Network card not recieving any packets

Network card not recieving any packets

Author
Discussion

Fatboy

Original Poster:

8,187 posts

284 months

Monday 20th October 2003
quotequote all
I've just tried to reinstall my brother's old computer with win2k, which was (ages ago) connected to an ethernet network.

The install went fine, but I cannot seen to connect to the network, and the 'Local Area Connection Status' box shows plenty of packets sent, but none recieved.

I've tried different PCI slots, checked for conflicts but nothing, and I'm totally stumped. All the othe comps on the network are accessing it fine?

Any ideas what it could be?

ew_topcat

1,938 posts

261 months

Monday 20th October 2003
quotequote all
you could do a 'ping' to see where the packets are going.
In dos command get the C: prompt then type, ping 127.0.0.1, this will do a loop off the card to check all is well. good luck.

smeagol

1,947 posts

296 months

Monday 20th October 2003
quotequote all
Things to try:

Command prompt, type ipconfig /all
This will list the settings for your card. Check its on the right subnet mask and ip address.

Try pinging the other computers: ping ipaddress (eg ping 168.192.1.2 ) You should get 3 replies.

Try pinging the W2k machine from a computer taht is working on the network.

Look at the workgroup settings. Ensure that it is on the same workgroup.

You haven't said if its a standard hub or gateway, or what the other computers are running. If they are on XP turn off their firewalls and see if you can then see them.

Something for you to try, hope that has helped a bit.

Fatboy

Original Poster:

8,187 posts

284 months

Monday 20th October 2003
quotequote all
I've tried pinging out, but not been able to - I just get the request timed out error.

Te network I'm trying to join has a gateway - I've got all the IP address etc right, all the settings are as for tje other computers in the lab but different (valid) IP address.

I can't join the domain, as the computer says it can't find it, and although it's sending the data out (lights on the local hub are flashing, it says there are packets being sent), I'm seeing no return of data, and only one of the little monitor symbols on the toolbar flashes. (I also get the 0 packes recieved message on the status thing)

Cheers for the help guys.

smeagol

1,947 posts

296 months

Monday 20th October 2003
quotequote all
Have you got any AV sofwtare installed? I've heard that tis has caused this kind of problem before. Try disabling it setting up the network and then reinstalling network.

Also there is a slammer worm which causes the flooding affect making it unable to see networks:

www.microsoft.com/sql/techinfo/administration/2000/security/slammer.asp

Have a look at these possibilities.

Out if interest I had a similar problem with my XP laptop it was dual boot but in XP mode wouldn't see the network. Unfortunately my cure isn't that helpful. I repartitioned the disk to pure XP and reinstalled with the network plugged in and it then was fine. (not much help I know)

pdV6

16,442 posts

273 months

Tuesday 21st October 2003
quotequote all
Check the simple things first:

. Swap the cable for one that you know works.
. Have you plugged it into an uplink port on the hub?

Fatboy

Original Poster:

8,187 posts

284 months

Tuesday 21st October 2003
quotequote all
pdV6 said:
Check the simple things first:

. Swap the cable for one that you know works.
. Have you plugged it into an uplink port on the hub?

Tried both of those - I also plugged my laptop into the the hub using the same port and cable and it could se the network fine - If it's a hardware problem it must be with the PC I think.

Fatboy

Original Poster:

8,187 posts

284 months

Tuesday 21st October 2003
quotequote all
smeagol said:
Have you got any AV sofwtare installed? I've heard that tis has caused this kind of problem before. Try disabling it setting up the network and then reinstalling network.


The graphics card is an ATI all-in-wonder-pro, but I've not installed any software yet - literally just win2k. (I'd formatted and Fdisked the hard drive, then win2k reformatted it during set up).

smeagol said:
Also there is a slammer worm which causes the flooding affect making it unable to see networks:

www.microsoft.com/sql/techinfo/administration/2000/security/slammer.asp

Have a look at these possibilities.

Out if interest I had a similar problem with my XP laptop it was dual boot but in XP mode wouldn't see the network. Unfortunately my cure isn't that helpful. I repartitioned the disk to pure XP and reinstalled with the network plugged in and it then was fine. (not much help I know)


Cheers for the help - I'll try pulling some other cards and see if works then (which is odd as it previously worked fine over the network running dual boot linux and win98)

loaf

850 posts

273 months

Tuesday 21st October 2003
quotequote all
Fatboy,

Have you got the vendor-supplied drivers for the network card, or are you using the MS embedded ones?

If you can't ping the loopback (127.0.0.1) it sounds as though the TCP/IP stack either hasn't initialised properly, or it hasn't bound to the card.

What OS and adapter are you using? Might be able to offer more help with a bit more info...

Fatboy

Original Poster:

8,187 posts

284 months

Tuesday 21st October 2003
quotequote all
loaf said:
Fatboy,

Have you got the vendor-supplied drivers for the network card, or are you using the MS embedded ones?

If you can't ping the loopback (127.0.0.1) it sounds as though the TCP/IP stack either hasn't initialised properly, or it hasn't bound to the card.

What OS and adapter are you using? Might be able to offer more help with a bit more info...



I'm using the microsoft embedded ones - didn't think to try pinging the loopback address, I'll try that (tommorrow though, as I'm out of the lab today).

The card is a realtech combined rj45/BNC job - I'll track down the actual model (came bundled with the comp so I'm not sure if I've got the actual drivers, comp came from Roldec who bollocksed up a lot of the order. Bout it in 1998 just before they went under....)

Edited to add: Just called my mate in the lab, got him to try it - it can ping 127.0.0.1 fine.

The network card is:

Realtek RTL8029{AS} PCI (according to the device manager)

>> Edited by Fatboy on Tuesday 21st October 11:19

zumbruk

7,848 posts

272 months

Tuesday 21st October 2003
quotequote all
BTW, pinging the loopback address doesn't necessarily tell you a lot. Many IP stacks deal with loopback pings at a very high level.

loaf

850 posts

273 months

Tuesday 21st October 2003
quotequote all


That is one prehistoric NIC. You can still get the drivers here: www.realtek.com.tw/downloads/downloads1-3.aspx?software=True&refdesign=True&spec=True&other=True&series=14
for all the major OS's - I'd start with those and see how you go.

Fatboy

Original Poster:

8,187 posts

284 months

Tuesday 21st October 2003
quotequote all
loaf said:


That is one prehistoric NIC. You can still get the drivers here: www.realtek.com.tw/downloads/downloads1-3.aspx?software=True&refdesign=True&spec=True&other=True&series=14
for all the major OS's - I'd start with those and see how you go.


Cheers for that - I bought it in 1998, and it had to be capable of either RJ45 or BNC connections (uni network officer told me I might need either for a connection in my room) and that was the card roldec supplied (I didn't specify an exact card).

liszt

4,330 posts

282 months

Tuesday 21st October 2003
quotequote all
You haven't got a firewall such as Zonealarm running have you?

Had this problem once, spent days trying to solve this problem. Mentioned it to friend at work and that was the first thing he said , which was the problem. Was a bit red faced

squirrelz

1,186 posts

283 months

Tuesday 21st October 2003
quotequote all
Can you watch theon the NIC when you ping out?

Data should flash in time to the pings.

Also try pinging it from another PC and see if it flashes then too.

Other things....

From command prompt, type arp -a
should see something like

Interface: 10.1.1.100 on Interface 0x1000003
Internet Address Physical Address Type
10.1.1.1 00-a0-0c-02-a1-0c dynamic
10.1.1.5 00-10-02-a4-b1-04 dynamic

and do it from another PC on the network after pinging for the problem PC, see if it can associate the IP address with a physical address.

>> Edited by squirrelz on Tuesday 21st October 13:44

Fatboy

Original Poster:

8,187 posts

284 months

Wednesday 22nd October 2003
quotequote all
loaf said:


That is one prehistoric NIC. You can still get the drivers here: www.realtek.com.tw/downloads/downloads1-3.aspx?software=True&refdesign=True&spec=True&other=True&series=14
for all the major OS's - I'd start with those and see how you go.


Tried that, and I can now recieve packets, ping out and get a reply, and am currently joining the domain

Cheers mate, owe you a pint

loaf

850 posts

273 months

Wednesday 22nd October 2003
quotequote all
Fatboy said:

loaf said:


That is one prehistoric NIC. You can still get the drivers here: <a href="http://www.realtek.com.tw/downloads/downloads1-3.aspx?software=True&refdesign=True&spec=True&other=True&series=14">www.realtek.com.tw/downloads/downloads1-3.aspx?software=True&refdesign=True&spec=True&other=True&series=14</a>
for all the major OS's - I'd start with those and see how you go.



Tried that, and I can now recieve packets, ping out and get a reply, and am currently joining the domain

Cheers mate, owe you a pint


Glad to be of service - invoice is in the post