Problem with cable modem and Win XP moving from comcast to new ISP

Problem with cable modem and Win XP moving from comcast to new ISP
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.modems.cable  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Problem with cable modem and Win XP moving from comcast to new ISP Benrand 09-15-2006
Posted by Benrand on September 15, 2006, 9:13 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Have a strange problem that seems to reside with the users XP config.

User machines: will pull DHCP IP on wired ethernet (Cisco sw, Foundry
rtr), will NOT pull DHCP IP on MTL Surfboard cable modem when running
WinXP, but will when FreeBSD is patrially installed from CD.

Looked at packet traces and the DHCP packets look fine, but her
machine doesn't seem to be recognized by the cable modem. The DHCP
transaction starts with her machine, but there is no response. Her
driver reports no pakcets recieved. Even placed a linksys rtr in
between and still see the same problem. Other laptops seem fine, work
with no problems.

Anyone hear of a user having issues moving from CM ISPs and
interoperability issues from some piece of software installed?

Someone mentioned this to me, but having trouble finding right result
from google.

Posted by Bit Twister on September 15, 2006, 11:21 am
On Fri, 15 Sep 2006 09:13:54 -0400, Benrand wrote:
> Have a strange problem that seems to reside with the users XP config.
>
> User machines: will pull DHCP IP on wired ethernet (Cisco sw, Foundry
> rtr), will NOT pull DHCP IP on MTL Surfboard cable modem when running
> WinXP, but will when FreeBSD is patrially installed from CD.

You description sounds different but the
usual problem is cable modem will not talk to anyone else execpt the
mac seen on powerup. If it were me,
I would
o verify doze box is set to get dhcp,
o power all equipment down, including cable modem
o wait for one minute by your watch,
o power up cable modem and wait for leds to settle down to about normal
o power up the equipment on the wire from the cable modem
o then power up any remaining equipment.

Posted by Benrand on September 18, 2006, 10:53 am
On Fri, 15 Sep 2006 10:21:25 -0500, Bit Twister

>On Fri, 15 Sep 2006 09:13:54 -0400, Benrand wrote:
>> Have a strange problem that seems to reside with the users XP config.
>>
>> User machines: will pull DHCP IP on wired ethernet (Cisco sw, Foundry
>> rtr), will NOT pull DHCP IP on MTL Surfboard cable modem when running
>> WinXP, but will when FreeBSD is patrially installed from CD.
>
>You description sounds different but the
>usual problem is cable modem will not talk to anyone else execpt the
>mac seen on powerup. If it were me,
>I would
>o verify doze box is set to get dhcp,
>o power all equipment down, including cable modem
>o wait for one minute by your watch,
>o power up cable modem and wait for leds to settle down to about normal
>o power up the equipment on the wire from the cable modem
>o then power up any remaining equipment.


Thanks for the reply, been through it more than a few times.



Posted by Benrand on September 18, 2006, 12:28 pm
On Fri, 15 Sep 2006 10:21:25 -0500, Bit Twister

>On Fri, 15 Sep 2006 09:13:54 -0400, Benrand wrote:
>> Have a strange problem that seems to reside with the users XP config.
>>
>> User machines: will pull DHCP IP on wired ethernet (Cisco sw, Foundry
>> rtr), will NOT pull DHCP IP on MTL Surfboard cable modem when running
>> WinXP, but will when FreeBSD is patrially installed from CD.
>
>You description sounds different but the
>usual problem is cable modem will not talk to anyone else execpt the
>mac seen on powerup. If it were me,
>I would
>o verify doze box is set to get dhcp,
>o power all equipment down, including cable modem
>o wait for one minute by your watch,
>o power up cable modem and wait for leds to settle down to about normal
>o power up the equipment on the wire from the cable modem
>o then power up any remaining equipment.


Well, I just found it. There was a QoS protocol enabled on her driver,
802.1p, that, I guess, the regular wired ethernet network didn't care
about but our cmts did.

Was a head scratcher.

Similar ThreadsPosted
Comcast cable modem problem April 18, 2005, 12:00 pm
Moving, new cable Co, offers Earthlink OR RoadRunner broadband October 9, 2005, 11:09 am
Cable modem problem? July 30, 2006, 10:51 pm
Problem with Cox cable modem January 2, 2008, 10:09 pm
cable modem speed problem December 23, 2005, 8:46 pm
Comcast DHCP renewal problem? March 5, 2006, 5:04 pm
Moving Internet to new room April 23, 2006, 4:23 pm
Modem problem? January 22, 2006, 2:13 pm
New here... with a problem of course. August 4, 2005, 8:06 pm
DNS problem September 29, 2005, 10:36 am

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map