PCA Forums

I've noticed something odd with my cable modem connection, at least since ATTBI took over. If I disconnect the patch cable and reconnect it I no longer have connectivity to the web. Can't ping, nada. I had a static address with @Home, so perhaps its DHCP?? ( I assign static to all client networks as they are all small, they can continue to work if the DHCP server gets hosed, etc thus know dick about DHCP other than how to set it up- a little )

I'm running W2KAS here at home, having to use DHCP now. When I pull the cable then reconnect it the IP settings have not changed. And I can't release and renew it, as I can on the networks I usually deal with. The only way to get up again is to reboot the %#@@!$ system.

Is this a 'feature' of DHCP?

the %#@ @!$ system.

huh? Looks like I'll have to learn new ways to almost curse :lol

Most cable networks are DHCP. If you're using IPCONFIG to release and renew that IS DHCP.

If it is DHCP, then when you reboot and run IPCONFIG you should see a lease date for the NIC listed in the details information.

If it is using DHCP I can't see any reason why it would require you to reboot as opposed to using IPCONFIG to release and renew.

I can renew to my hearts content, no worries. As soon as I release the lease I'm locked out, and am assigned a class B ?? ( 169.254.121.241 ) address from somewhere. ( There was a third IP range reserved for private networks: is this part of it? ) Currently this is the only system on this segment so.....

After releasing the lease, when I try to renew i am told :

"The following error occured when renewing the adapter Local Area Connection: no connection could be made because the target machine actively refused it"

After rebooting I am back to my normal 12.233.x.x address, and all is well.

I'm unaware of a DHCP server on my network at home. And this looks like it might be intentional ( these are the guys who refused to talk to me when they thought I had W2KAS running )... Either there is a simple answer, or perhaps they track the lease info with respect to my NIC's MAC address, then give it an invalid IP when I release and try to renew... ?
What is different between the boot strap process and renewing a lease?

Not a burning issue of course :chug but would be nice to know why. Might help rule possible causes when at a site banging my head on a desktop..

I assume you're using two NICs and a software NAT router?

Well it can't be another DHCP server because that would be on the internal LAN and wouldn't be detected on the NIC conencted to the router.

I'm guessing, but yeah I'd say it's something they're doing.

If it bugs you, you could always use a Dsl/Cable router box and not worry about disconnecting your rig.

no, only one NIC in this system. Was working on learning enough Linux to set up a router, but instead have installed an old 8 port hub after the cable modem.

Y'know, I hate being dis stupid early in the day )* . I just did a quick Google search on private IP ranges... the first link was

http://www.win2000mag.com/Articles/Inde ... cleID=7464


which covers the IP I come up with after releasing....It doesn't explain the 'target machine actively refused' comment.. further searching w/Google seem to say it's 'something' with respect to the server side of the connection. The service is not available.
So, in some way ATTBI is able to kill the service for my spceific MAC... think I'll see what happens if I assigne the IP info I had before releasing manually

Thanks for your thoughts!