Grrrr.....ICS!!

Erasmus-X

Platinum Member
Oct 11, 1999
2,076
0
0
I just purchased a 3Com HomeConnect phoneline networking kit. Since I'm too lazy to run ethernet under the carpets in my new apartment, I thought I would give this one a try. The included network adapters are USB. Since I'm running Win2k, I can't use the included Microsoft HomeClick (this part is more of a blessing, actually).

Here's where I keep running into problems though:

I trying to set up ICS so that I can share my dialup connection with the computer in my brother's bedroom. I was able to do this with no problems using my ethernet card back when I had the two machines connected hardwire. The only thing is that ICS will only use the IP 192.138.0.1. That IP was originally bound to my 3Com Etherlink XL 10/100. To change this, I set the ethernet NIC to automatically obtain an IP address (lengthy reboot!). After that was finished, I configured the USB phoneline adapter on my machine to share the internet conneciton. But Windows won't LET me do that, because it still insists that the ethernet adapter was already using IP 192.138.0.1! I just went through a reboot to prevent this from happening and apparently the problem is still there. I even tried disabling the ethernet NIC in the device manager with no luck. I've tried just about everything and Windows refuses to let go of that IP binding on the ethernet card. Very aggravating to say the least. I really don't want to yank out my ethernet card because I do make quite a bit of use out of it, with or without the phoneline networking kit.

Any insight would be appreciated. Thanks.
 

RustyNale

Platinum Member
Apr 14, 2001
2,220
0
0
Go into network neighborhood and remove tcp/ip. reboot. add tcp/ip but don't configure it.reboot. Run ics, it should now to assign your nic ip 192.168.0.1, subnet 255.255.255.0 reboot.

Yes, windows needs to reboot that many times.
 

Yzzim

Lifer
Feb 13, 2000
11,990
1
76


<< Yes, windows needs to reboot that many times. >>


Man, you could say that again. I did those same steps and thought I was gonna blow the PS rebooting so many times ;)
 

Scarpozzi

Lifer
Jun 13, 2000
26,392
1,780
126
Yeah...the main reason it must reboot is just to finish the whole &quot;remove&quot; action. I used to completely reinstall all my protocols and clients when I had that problem. But, then again...running winipcfg from the command prompt should allow you to release your ip info. When you click renew and obtain a new one, it will recache that address the next time you boot.
 

Scarpozzi

Lifer
Jun 13, 2000
26,392
1,780
126
oops...noticed you said you're using Win2k. Go to a command prompt and type ipconfig /release then type ipconfig /renew

:)