General discussion

Locked

Net card

By larry ·
I have an NT server and the workstation Iam having trouble with has win 98.
I can ping the server from the workstation and ping itself and other workstations but cannot ping the workstation from the server or anywhere else. Iam thinking the eathernet card is bad and only sending out and not recieving. Am I thinking in the right direction?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Net card

by eBob In reply to Net card

It is probably something in the TCP/IP configuration such as "default gateway". When PING is returning funny results, always do a follow-up TRACEROUTE (TRACERT in Windoze). This way you can see if TCP/IP is sending the packets out a secondary interface somewhere along the line.

Collapse -

Net card

by eBob In reply to Net card

Oooops, forgot one thing: No you likely do not have a bad NIC that is only sending and not receiving (or the other way around). You know that because you can ping from WKSTN to SRVR which means your WKSTN NIC sent a packet, SRVR received it, SRVR then sent an acknowledgement, and WKSTN received that.

Collapse -

Net card

by larry In reply to Net card

The question was auto-closed by TechRepublic

Collapse -

Net card

by McKayTech In reply to Net card

I agree with the first answer that the most likely explanation is a TCP/IP configuration issue. However, you didn't tell us whether you are pinging by IP address or name and if you're pinging by machine name, it could be a WINS issue (stale WINS record or WINS configuration error).

If you're pinging by IP, I would say the most likely TCP/IP setting to look at would be the subnet mask. You can do an IPCONFIG /ALL from the command prompt and see all the TCP/IP settings so you can compare them with those on a machine that is working properly. In a single server LAN environment, only the IP address should be different from machine to machine - the default gateway, WINS, etc should all match.
The most common error would be a subnet mask of 255.255.255.0 on one machine and 255.255.0.0 on the rest of the network.

That having been said, I would think that the remaining possibilities are that the NIC driver is goofy or the NIC itself has some bizarre disease. Either of those would be rare, but not unheard of.

paul

Collapse -

Net card

by larry In reply to Net card

The question was auto-closed by TechRepublic

Collapse -

Net card

by larry In reply to Net card

This question was auto closed due to inactivity

Back to Networks Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums