13 replies
by dennisbv
Poster rated this answer.
by voldar
by dennisbv
by sgt_shultz
by dennisbv
Poster rated this answer.
by the clam
It sounds to me as though there is something on the machine flooding the connection. I think we can eliminate jabber since you've tried more NICs on it.
I'd be very tempted to install a packet sniffer and have a look at what it thinks is going in / out of the interface. Personally I use Ethereal, mainly because it's open source (free) and I'm more of a Linux kind of guy.
It might show up a mistake in the configuration, or perhaps that a firewall is blocking any useful communication. I know Zone Alarm plays hell with my network at home, even when it's set to OFF!
by dennisbv
Poster rated this answer.
I did run a packet capture and it seems that when I cannot ping this machine or any of our network machines from it. I think the packet info shows that the computer thinks it is a Server so it logs into it's self. I have a program called big info running on it and it displays the the logon server is the same as the computer. I ran the packet capture for about fifteen minutes and it only capture three packets from this machine. Under Netbios it show a source name service4<20> (server service) "service4 is the workstation name". and under Microsoft Windows Browser Protocol it has server type 0x00001003 and it appears that it thinks it is a server?
by the clam
OK then:
a) do you get an IP address?
b) what is the output of ipconfig /all
It seems to me a bit like your PC isn't picking up an IP address. Make sure the DHCP client service is running and on auto start in your services list.
The NetBIOS stuff you describe sounds fairly normal to me - the workstations I have here advertise service numbers 00, 03, 20 and 1E. If I didn't log them onto the domain, they would refer to themselves as servers according to your software I would guess.
Still, only receiving 3 packets in 15 minutes suggests it's *not* talking to the network or hearing it at all. Windows machines tend to send out the odd broadcast packet even when they're idle, so you should be seeing more than that assuming other machines on the network are powered up. It sounds like either you have a firewall (do you? you didn't answer) which is blocking everything or your NIC isn't installed properly. I've seen cases like this with an IRQ set wrongly on a card, also seen cases where the NIC has crashed and needed to be removed and re-added.
My gut feeling though is firewall seeing as how you're not getting any traffic at all and you've tried another NIC.
by dennisbv
Poster rated this answer.
Some times if I totally shut down and restart the machine it will log in to the network and run my log in script but it will not stay on the network. The firewall is between the internet and the local network and this machine is on the local network.
by the clam
To be honest I don't know why I'm bothering to post again given your previous replies, but anyway...
Perhaps it is the result of an IRQ or I/O conflict. It's possible that the two NICs you have tried (which I assume are known good as tested in other machines, but you haven't said) may possibly have a similar chipset on them, or may be getting assigned the same IRQ / memory ranges / ports by the PnP BIOS. You could, if your BIOS supports it, try sepcifying which IRQ / whatever to give to the slot your NIC is in. I've had to do this in the past when my BIOS has tried to make a NIC share IRQ with another device (actually, several other devices while leaving 3 IRQs free).
If no joy, could you verify that both NICs you've tried work fine in other machines? Do other machines work OK in that switch port?
Have you tried forcing the media & duplex settings for the NIC?
by dennisbv
Poster rated this answer.
I set the Bois to Not Automaticly control resources. There was a conflict between the card and another component.
by dennisbv
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending