Fix that first.
Remember that this is why you hired that IT staff.
Bob
Hi I am new to this forum.
![]() | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
Hi I am new to this forum.
Discussion is locked
Fix that first.
Remember that this is why you hired that IT staff.
Bob
Trying to make sense of your post.
Do you have any USEFUL information, or not really?
1. Work the ping issue.
2. It's a business. If your IT staff is lacking, call in some consultant.
Hope this clears it up.
Bob
Be sure your IT staffer checks the HOSTS file. The LAN cables are rarely the issue when you can ping other machines.
Bob
Did you at least find the HOSTS.SAM file?
In a stock setup it's over at http://support.microsoft.com/kb/972034
Having no HOSTS file is odd. I'd use Microsoft's stock content at least to remove that oddity.
Also, I can't guess how you are PINGING. By IP is best since we can't guess the name resolution system your IT setup.
-> And do the other TRACEROUTE to that to see if any odd things show up. For XP, here's how -> http://support.microsoft.com/kb/314868/
Bob
I'd compare the working and non-working machines results from the following command.
IPCONFIG /ALL
It looks like a netmask or gateway is off. Or if there is VPN involved an issue with the VPN client.
Bob
Loopback1.ken10.Sydney.telstra.net [165.228.2.1]
Maybe the route at 172.17.144.40 is broke?
Bob
I don't know what the netmask, default gateway is. But you found the issue at least. You have to know what these IPs are.
Bob
Hi Bob
how would I go about finding the peice of hardware which the connection is stopping at? A few pointers would be good. Will be good to know what to do if this ever happens again, or in a differtent scenario.
Thanks Bob
I see someone has given instructions on how to share the needed details. All I can see is that it leap off the path. It's your network and I can't guess why it went there given only these details.
What happened to your IT staff?
Bob
I'd like to help. Keep telling more and maybe some clue will show up.
I have had such issues when the subnet mask was incorrect on the server. Verified the subnet mask is correct on the server?.. Is the subnet mask supposed to be the same on all machines? Or are they different subnets? Checked that as well?
Since you mentioned "issues" on the server, you might need to uninstall/reinstall TCP/IP on the server.. Tried that yet?
Checked "Event Viewer" on the XP machines to see if there are any clues as to the problem.. Maybe TCP/IP or DHCP errors..
Have you tried uninstalling, then reinstalling the server's network adapter/card? Maybe an updated driver or new ethernet card is needed?
Hope this helps.
Grif