Problem with my NIC Card

[Dharamsi]

hello

I am having a strange problem with my nic cards.
My server box has 2 double port Intel NICs cards in it, one of the ports is used to go out to the internet router, and then one port has a crossover cable which is been hooked to my current main port. I have internet connection sharing. For some reason my file sharing between my two P4 boxes isn't working.

Please help meregarding this problem

Your views will be appreciated

[Zachary]

Try changing the workgroup on one PC to something different, saving, restarting then changing it back and restarting again, then try it on the other one.

It's also worth doing the same thing with file sharing.

Have you tried RDP to the server using the IP address?

[Big Fish]

Only other thing I might suggest is to see if the router has a reset button. Mine does. It is a pinhole button activated by use of a straightened paperclip. Good luck with it but it sure sounds like a failure.

[Shen]

You can try running this command from a command line:

ipconfig /all

If the numbers beside IP Address reads something like: 47.198.180.191
And the Subnet Mask reads something like: 255.255.255.128
And the Default Gateway reads something like: 47.198.180.128
And the DNS server reads something like: 64.71.255.198

Then you should be fine.

If however your IP Address reads something like: 69.xxx.xxx.xxx

then you may want to consider a new NIC.

But the fact that you're still able to download music when this occurs seems to say that it's not the NIC.

What about the lights on your modem? When you get the page cannot be found error do the light on it stay green?

Also, have you tried a different network cable?

I had an error like this once where out of the blue my connections became intermittent. Finally traced the problem to the network connection on the modem itself. My NIC was fine, my cable was fine, my modem's ability to connect to my provider was fine. It was just the point where the network cable plugged into my modem that had gone wonky on me.

[Steve123]

At least I think it's 69.xxx.xxx.xxx but it may have been 169.xxx.xxx.xxx, it's been a while since I've seen it. It's all about loopback addressing.


I don't remember the exact circumstances under which this happens but it's roughly along the lines of the NIC autoconfiguring itself. This was taken from a Microsoft TechCentre article:


Automatic Private IP Addressing


An interface on a computer running Windows Server 2003 and Windows XP that is configured to obtain an IPv4 address configuration automatically that does not successfully contact a Dynamic Host Configuration Protocol (DHCP) server uses its alternate configuration, as specified on the Alternate Configuration tab.


If the Automatic Private IP Address option is selected on the Alternate Configuration tab and a DHCP server cannot be found, Windows TCP/IP uses Automatic Private IP Addressing (APIPA). Windows TCP/IP randomly selects an IPv4 address from the 169.254.0.0/16 address prefix and assigns the subnet mask of 255.255.0.0. This address prefix has been reserved by the ICANN and is not reachable on the Internet. APIPA allows single-subnet Small Office/Home Office (SOHO) networks to use TCP/IP without static configuration or the administration of a DHCP server. APIPA does not configure a default gateway. Therefore, only local subnet traffic is possible.


If you can, try getting your hands on another NIC. Install it in your system and see if the problems occur then. If you do do this, just make sure you do an ipconfig /release before you hook your modem up to the borrowed NIC.