//flex table opened by JP
PDA

Click to See Complete Forum and Search --> : ICS screwed up my NICS...beware

SocialChaos
03-08-2006, 07:41 PM
Ok...here's the machine:

Asus A7N8X-E Deluxe (comes with 10/100 nic and 10/100/1000 nic onboard)
US Robotics Performance Pro V.92 modem (moved out the the sticks and I'm on dialup again)

I have 2 machines networked via a LinkSys switch, with the Asus machine having the internet access with the US Robotics dial-up modem. I needed to hit the net with the other machine on the network, so I enabled ICS on my machine and picked from the drop-down menu the 10/100/1000 gigabit NIC on the Asus board as the one I wanted to use. Well, ICS changed my ip to 192.168.0.1 on that nic (normal) and the other machine had internet access through my comp like I needed.

After I was done on the other machine, I disabled ICS and switched my gigabit NIC back to dhcp (Obtain an ip address automatically) well...afterwards my NIC just sits there saying "Aquiring network address" for 5 minutes then gives me a pop up saying "Limited or no connectivity". I tried to hit repair, but it just hangs on "Renewing your IP address". If I assign a static IP the NIC is fine. I check the NIC details and it says the IP address is 169.254.96.110 with a subnet mask of 255.255.0.0

I tried ICS again and picked my 10/100 NIC this time, then disabled it afterwards and now both my NICS are screwed, and can't obtain an IP address automatically. If anyone tries this I'm pretty sure they can replicate the problem on their own machine....but beware, I have tried the winsockfix and tons of other things and still haven't been able to get my NICS back to normal. If anyone gets brave, try this out and see if you can figure out what the fix is for your NIC after you disable ICS.

I'm out of ideas.... :mad:
Midknyte
03-08-2006, 07:54 PM
you're using dialup, not broadband, right? if there is no dhcp server connected to your nic, then 169.254.x.x is the correct APIPA IP.

ICS sets a static IP, but it will go back to DHCP when you disable ICS. if there is no router or ISP for your NICS to get an IP from, then it will default to the 169.254.x.x.
SocialChaos
03-08-2006, 07:59 PM
you're using dialup, not broadband, right? if there is no dhcp server connected to your nic, then 169.254.x.x is the correct APIPA IP.

ICS sets a static IP, but it will go back to DHCP when you disable ICS. if there is no router or ISP for your NICS to get an IP from, then it will default to the 169.254.x.x.

Yes, I'm using dialup. That's what I noticed...the IP seems correct, but I have the "Limited or no connectivity" warnings down at the bottom of my taskbar for both NICS now after disabling ICS. The only way to get rid of it is to assign a static IP to both nics. If I switch both nics to "Obtain ip address automatically" it just searches for an IP for like 5 minutes then gives me the error on the taskbar. It's so annoying... :mad:
Midknyte
03-08-2006, 08:13 PM
that is a normal message because windows is expecting to find a dhcp server. you could just disable the hardware in device manager also. then just enable it when you need to.
cat5e
03-08-2006, 08:20 PM
ICS is a combo NAT/DHCP Server, so it woud assign IP to the second computer.

When you do not use ICS. there is No DHCP server available, and you need to assign Static IP.

:cool:
SocialChaos
03-08-2006, 08:20 PM
that is a normal message because windows is expecting to find a dhcp server. you could just disable the hardware in device manager also. then just enable it when you need to.

Yeah...with static IP's the NICS work like they're supposed to so I guess it's not too bad...but I never had the problem until I used ICS for the first time then disabled it. Weird... :confused:
Midknyte
03-08-2006, 08:30 PM
it's not an ICS issue; that's just how winxp is.

i think it's easier just to disable it in the device manager you're not using it rather than typing in a static IP. just my opinion, 'cause I'm lazy. :)
harmon12
03-12-2006, 02:40 PM
I have close to the same problem every couple of months, I use xp for my dial up connection. To fix the problem I set the ip on xp nic to 192.168.0.1 subnet 255.255.255.0 then I use the home network wizard and share my dial up connection turn on file and print sharing and I dont bother making the network disk I then go to the 98/me machine and make sure it is set to obtain an ip address automatic restart the 98/me machine when I get back to the desktop I run winipcfg and make sure I have an ip that starts with 192.168.0.xxx I have no problem surfing the net, printing or sharing files. I have never been able to have a shared connection or even to see my own pc in network places if the ip is 169.xxx.xxx.xxx