Networking Problem...

[wnied]

I am working on a Client machine whos tcp/ip config looks like this: IP: 200.200.200.13
SUB: 255.255.255.0
NO GATEWAY

The Server has TCP/IP Settings like this:
IP: 200.200.200.1
SUB: 255.255.0.0
NO GATEWAY

My problem is that the client has an applicatin that runs through tcp/ip, and its not communicating with the server.
Client cannot see anything on the network. I know the subnets are different, but there is a client machine with the same exact setup that CAN see the network. I have de-installed and re-installed Network neighborhood several times with no success...

Any Suggestions?
Thanks,
wnied

 

[dajo]

Well, I don't know much about IP addressing, but those numbers seem strange. If I were you I would:

1) use a subnet mask of 255.255.255.0 on all machines including the server
2) make sure that all machines are part of the same workgroup (right-click Network Neighborhood/Properties/Identification

Is this a peer-to-peer network, or do you have a server which actually authenticates (running NT)?

You must be logged on in order to see the network. Make sure that you are logging on when the computer boots. I'd use Client for Microsoft Networks on all machines, set it to be the Primary Network Logon, set the default protocol to TCP/IP (advanced settings on the TCP/IP protocol), and you must also have File/Printer Sharing Service installed on all machines and enabled (check box to share) in order to see shared resources. That alone may be your problem. If you do not have the File and Printer sharing Service installed you will not see anything.

Check all of these and see what you come up with.

Can you ping the IP address of the server or the other client machine? If not, then you are probably not logged on.

 

[outlamd]

Subnet mask is incorrect. Right now those two computers are not local to each other. Change the sub on the client to 255.255.0.0 and all should be good.

 

[warcleric]

I really dont think the subnet mask is going to effect it. It defines what other computers are considered to be on the same subnet. According to your setup, that workstation falls within the servers subnet and the server falls within the workstations subnet. So I would start looking elsewhere for your problem. Try setting the server 200.200.200.1 to the gateway on the workstation.

 

[spidey07]

Your mask is the problem.

Client thinks subnet broadcast address is 200.200.200.255 while the server thinks the subnet broadcast address is 200.200.255.255. Microsoft browsing relies heavily on the IP broadcast address to announce and locate services.

 

[NOC9006]

I agree with spidey07, the netmask seems to be a problem. When the PCs go through the "ANDING" process they each come up with a different IP broadcast address. Windows certain does rely heavily on IP broadcasts.

The other PC set up "exactly" the same makes me wonder.

Can you ping from the trouble PC to the server? what are the error messages if any?

Do you have the ability or software to do a trace and see what exaclty is on the wire?
(sniffer pro)

 

[spidey07]

pings should work with this kind of different mask. BUT, IP broadcasts will not work (browsing and other functions)

lets us know how it turns out.

cheers!
spidey

ps - the subnet mask must ALWAYS match on every single node of a particular network.