Discussion Locked

I can't Ping out.

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a server running as an ftp and print server. TCP/IP setting's mimic a similar server (just a print server) and they both are on the same subnet. When I ping my ftp/print server it replies w/no problem. When I go to that particular server and ping out to my other print server (w/ the same subnet) I get a request timed out. I can ping my loopback, its own IP, but I can't ping its gateway, or WINS Server. The server functions properly with FTP, but doesn't function as a print server. When I double-click network neighborhood I see all the net-bios names properly and I can do a net send to a remote computer but I can't ping it. When I ping, I do get the IP and hostname resolved but right after I get Request timed out messages.

16 replies

by slora

Your FPT/print server is able to resolve the IP addresses of other computers on the network, and the FTP server is working, so TCP/IP is working. Your net send commands work because your FTP/print server is able to resolve the addresses of the other computers. Your ping times out because the other computers cannot properly resolve the name of your FTP/print server. Your ping request reaches the other computers, but their replies cannot return.

The first place you should look is in your WINSand DHCP databases. There is probably a name resolution conflict for your print server.

If you have recently changed network cards in the server, or if the server has the same name as an old server it may have replaced, you can easily get an address conflict in WINS or DHCP that can cause intermittent and unpredictable (or persistent and predictable) name resolution problems.

Look at the WINS database sorted by name, then by IP address. Tombstone obsolete or improper conflicting inactiveentries.

by zaldy

Thanks for the input. I should have been a little bit more descriptive. This ftp/print server is also a BDC. LMHOST name and IP is set statically just like our other print server.

by mckaytech

Wow! That's an interesting situation and I don't know quite what to make of it.

I think the first thing I would do is make there are no other protocols running on the network (e.g. NetBeui). Then at the server where you're having the problem, go to a command prompt and type "ipconfig /all" and see if it thinks the settings are the same that you think they are. Also check the Event Log to see if there is any evidence of duplicate IP addresses or anything of that sort. It sounds a little bit like a situation I once saw where the NIC was configured with an incorrect subnet mask but the machine also had NetBeui running so some connections still succeeded.

Hope this gives you a start.... good luck!

paul

by zaldy

Thanks for the reply; although, I checked for those instances already. I think I'll try looking at the NIC to see if it is preventing ICMP tools to run.

by terminator

Go to wins manager and delete all entries related to your server and then go to your server and restart it, that you reregister it on Wins properly this time

Good luck

by zaldy

Thanks for the input. I should have been a little bit more descriptive. This ftp/print server is also a BDC. LMHOST name and IP is set statically just like our other print server.

by terminator

Ping workstation, if it does work then got to wins database and have a look if everything seems ok, you can delete all the entries related to that workstation and restart that workstation to force it to reregister its name. If this doesn't do the trick then you should check your server if he is a wins client.

If ping doesn't work then connectivity problem, check your tcp/ip configuration

good luck

by zaldy

Thanks for the input. I should have been a little bit more descriptive. This ftp/print server is also a BDC. LMHOST name and IP is set statically just like our other print server. I think I am going to try seeing if the NIC has a problem w/ICMP tools.

by billy

When you use the ping command it has absolutely nothing to do with name resolution or your wins server/database. Your tcp config must be incorrect such as subnet mask.(ie 225 instead of 255).

by zaldy

Thanks, but the subnet mask are the same as my print server. They both are on the same subnet as well. NetBeui and ftp works fine so it appears as if the connection and route is reachable. I am going to see if the NIC has a problem w/ICMP tools.

by zaldy

I appreciate your help but we are planning on that as our last case scenario because ftp is still being used heavily on this production server. I am still gathering data for off-peak hours to "play" w/the network card bindings.

by zaldy

Thanks for the input. I should have been a little bit more descriptive. This ftp/print server is also a BDC. LMHOST name and IP is set statically just like our other print server. The ftp side of the server works fine; therefore, there can't be any IP conflicts currently.

by shs_bulldog

Try to ping with a higher TTL rate. Thats a variable you can set after ping. That should give it more time for the server to respond. If that doesnt work, try tracert and see exactly where the promblem is.

by zaldy

Thanks but I have already tried that. I also tried tracert. The funny thing is that ftp works fine, no problem. The NetBeui utilities also works fine.

This discussion is closed to new replies.