Discussion Locked

No Pinging

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Dell Optiplex running Windows 95 on a mac served network. It used to just run the internet, now I have reinstalled all protocalls and the card itself and just have the LAN available. I have assigned an IP address that I know works and have manually entered all wins and gateway info. I cannot ping myself from this system.

11 replies

by toadysd

I pinged the IP address it is assigned to and got back all packets. Also, earlier I had another system assigned to the same address and both came back with IP in use errors that went away when I reconfigured the other system to its proper address.

by simon sedgwick

Ok, so you can now ping yourself but now you can't travel the network ?? Is this correct??

Are you using a DNS server on your network?
Are you able to resolve names across the network?
Can you ping other machines by IP but not by name ?

I know this isn't an answer, but these are some of the questions that will help identify your problem. post a comment wiht wom of these answers ...

=)

by 3dad

It's hard to determine where the problem may be with such minimal info, so here are a couple of other resources,

This is the first I would try:

1)"Use TechRepublic's TCP/IP checklist to troubleshoot your network"
https://www.techrepublic.com/download_item.jhtml?src=search&id=dr00220000120eje01.htm

2) Do a search on all of TechRepublic using different keywords-you'll be surprised at how much you'll find. Try "troubleshooting", or "TCP/IP" - or where ever you may think the problem may lie.

3) www.searchnetworking.com - "ask the experts" feature not up yet, but will be soon, haven't spent much time at that site to know wether or not they have much to offer, heard about it in a TechRepublic TechMail.

Hope it helps.

by toadysd

In response to Simon's Q's:
I don't know much about the district server and their dns setup. We do have internet access here, but DNS is disabled in all of our TCP/IP settings on all systems.

The ping on the address was not possible from the problem system. I did that from the system in my office. The one I'm having trouble with can only use the LAN right now. It won't even ping 127.0.0.1!

I'm not sure what you mean by resolving names accross the network. If you are referring to other systems on the LAN, there is no problem. If the internet, then no names are being resolved at all.

In response to Pytor:
I have used #1 and #2 to a point. Will try more with 2 and 3. Thanks.

by toadysd

And yet more test info.

WINIPCFG does not work due to an error "Unable to read IP configuration".

PING does not work for any IP address. Same error every time: "PING: transmit failed, error code 10091."

PING from my system to problem works. TRACERT from my system to problem system's IP gives the correct system name.

As for Pytor: #2 has been helpful so far... #3 was useless. Got a bunch of corp. buy this junk. Will mark acceptable when im ready to close question.

by cdobbin

You said that you can not even PING the internal IP address, and when you run winipcfg you get an error saying can't read IP config. I would delete all protocols and remove the NIC from device manager and reboot.(let win detect the card)
Start by adding netbuei and setting up a windows share with another PC and make sure it works fine, then add TCP/IP and configure it and see what happens. If that fails you may want to try another NIC, last resort would be to reinstall the OS and see if that helps.

This discussion is closed to new replies.