Cable and Winipcfg

[michlin]

Hi all,

My cousin has cable through AT&T (in southern NH). He tells me he has to all too often, use Release All and Renew All in Winipcfg to keep a connection. I can't truthfully tell him this sounds strange or not, (although I think it is) because I'm using DSL and have no experience with broadband cable.

Is this normal? In what situations should Release All and then Renew All be normally used? :confused:

Thanks people! :)

[xbit]

thats not normal, if he get connected and then disconnect over and over he could have a weak signal or a bad cable modem. It could also be that the isp is having problems or is he using usb. If he is tell him to get an ethernet card and hook up his cable modem that way. If you need to know more just come backs ask

[xbit]

And also have the isp test his lines and check for packet loss:)

[MosDef112]

Yep, unfortunately Windows doesn't automatically renew a lease even after it expires, so you will have to continue renewing. Doing it too much would signify a line that continues to reconnect, so you could be experiencing signal loss, or a busy network. Have them take a look.

[Indy]

He may also want to check to see if someone else is using his ip. I've seen a few instances where this was caused by another person using the wrong ip...

[michlin]

Thank you for your responses. I will send this thread to him. :)

[MosDef112]

*** In response to IndyOST ***

You're right, I didn't think about that. At my job we also have a DHCP server that also sometimes delays in refreshing it's address pool database to MAC addresses, but at least we get a conflict error. I don't suppose that AT&T broadband does that.

[Murman]

ya, AT&T Broadband does do that .. if there is a IP conflict, you'll see the windows error with the conflicting device and IP.

Originally posted by MosDef112
*** In response to IndyOST ***

You're right, I didn't think about that. At my job we also have a DHCP server that also sometimes delays in refreshing it's address pool database to MAC addresses, but at least we get a conflict error. I don't suppose that AT&T broadband does that.

[Indy]

Originally posted by Murman
ya, AT&T Broadband does do that .. if there is a IP conflict, you'll see the windows error with the conflicting device and IP.



Unless the ATT system is significantly different from the system I'm in, you won't necessarily get the error message...most of the time that I have gone into customers houses that have had this problem have had no indication other than the fact that they have to continually release and renew their ip address. The easiest way to verify is to shut down the computer that's having the problem, then have someone ping your ip address...if you get replies back, then someone else is using that ip....

[MosDef112]

*** In response to IndyOST ***

You don't even need to do all that. If you have that good old analog modem, you can pop it in, disconnect your broadband connection from your PC, dial out, and try to ping your address. In most cases, if someone else is using your IP, you'll just get no connection. The network will assume you're trying to access an IP that does not correspond to your MAC address, and the interface will be disabled on your node from the CMTS end until you renew your lease.

[Murman]

It is diffrent .. you do see the IP conflict error message when and if someone hard codes your IP or a IP or when DHCP is acting up and double assinging IP's (very rare), but has happened.

Note: this is only in the NewEngland and LA area. Atlanta is prob the same but I'm not 100% sure and these are the Mediaone systems acquired by AT&T



Originally posted by IndyOST


Unless the ATT system is significantly different from the system I'm in, you won't necessarily get the error message...most of the time that I have gone into customers houses that have had this problem have had no indication other than the fact that they have to continually release and renew their ip address. The easiest way to verify is to shut down the computer that's having the problem, then have someone ping your ip address...if you get replies back, then someone else is using that ip....