Hello all,
Just installed XPHome(bundled with SP2) on a computer. When I try to connect
to the cable modem it send up the "connection may have little or no
connection" message.
I tried the ipconfig /release then ipconfig /renew in the command prompt and
it gives me a "unable to connect to the dhcp server, request timed out"
message. The IP it assigns me is a 169.*.*.*. I've tried swapping out NICs,
changing cat5 cables, power cycling the equipment in different orders, etc
etc. I know it's not my cable connection since my other computer doesn't have
any problems connecting to the web using the exact same modem and cabling.

Also, this is a fresh install on a clean harddrive so there are no
peripherals getting in the way.

Any help would be appreciated,

Thanks,
Sam C

sam, read my post a few down from yours..... the exact same thing! does your
node type come up as unknown like mine? this is too wierd.

"Sam C" wrote:

> Hello all,
> Just installed XPHome(bundled with SP2) on a computer. When I try to connect
> to the cable modem it send up the "connection may have little or no
> connection" message.
> I tried the ipconfig /release then ipconfig /renew in the command prompt and
> it gives me a "unable to connect to the dhcp server, request timed out"
> message. The IP it assigns me is a 169.*.*.*. I've tried swapping out NICs,
> changing cat5 cables, power cycling the equipment in different orders, etc
> etc. I know it's not my cable connection since my other computer doesn't have
> any problems connecting to the web using the exact same modem and cabling.
>
> Also, this is a fresh install on a clean harddrive so there are no
> peripherals getting in the way.
>
> Any help would be appreciated,
>
> Thanks,
> Sam C

plus, i am kind of glad that this has happened to someone else. the more the
merrier (and the hope that this has happened many times before, and the fix
is as easy as a quick registry adjustment)

"tom" wrote:

> sam, read my post a few down from yours..... the exact same thing! does your
> node type come up as unknown like mine? this is too wierd.

Hmm, don't remember what the node said. I'll check it when I get home (work,
it's the curse of the computer geek)
I just hope we can find an answer *fast*, I need to get this computer back
to it's owner so I can get the money I've got sunk into it back.

Sam

"tom" wrote:

> plus, i am kind of glad that this has happened to someone else. the more the
> merrier (and the hope that this has happened many times before, and the fix
> is as easy as a quick registry adjustment)
>
> "tom" wrote:
>
> > sam, read my post a few down from yours..... the exact same thing! does your
> > node type come up as unknown like mine? this is too wierd.
>

Hmm, don't remember what the node said. I'll check it when I get home (work,
it's the curse of the computer geek)
I just hope we can find an answer *fast*, I need to get this computer back
to it's owner so I can get the money I've got sunk into it back.

Sam

"tom" wrote:

> plus, i am kind of glad that this has happened to someone else. the more the
> merrier (and the hope that this has happened many times before, and the fix
> is as easy as a quick registry adjustment)
>
> "tom" wrote:
>
> > sam, read my post a few down from yours..... the exact same thing! does your
> > node type come up as unknown like mine? this is too wierd.
>

Hmm, don't remember what the node said. I'll check it when I get home (work,
it's the curse of the computer geek)
I just hope we can find an answer *fast*, I need to get this computer back
to it's owner so I can get the money I've got sunk into it back.

Sam,and I agree, it's nice to know I'm not the only one pounding my head
against the wall

"tom" wrote:

> plus, i am kind of glad that this has happened to someone else. the more the
> merrier (and the hope that this has happened many times before, and the fix
> is as easy as a quick registry adjustment)
>
> "tom" wrote:
>
> > sam, read my post a few down from yours..... the exact same thing! does your
> > node type come up as unknown like mine? this is too wierd.
>

Hmm, don't remember what the node said. I'll check it when I get home (work,
it's the curse of the computer geek)
I just hope we can find an answer *fast*, I need to get this computer back
to it's owner so I can get the money I've got sunk into it back.

Sam,and I agree, it's nice to know I'm not the only one pounding my head
against the wall

Do these boards ever work correctly? I keep gettin an error message and
having to hit back to try to repost....eesh...is it Monday again?
"tom" wrote:

> plus, i am kind of glad that this has happened to someone else. the more the
> merrier (and the hope that this has happened many times before, and the fix
> is as easy as a quick registry adjustment)
>
> "tom" wrote:
>
> > sam, read my post a few down from yours..... the exact same thing! does your
> > node type come up as unknown like mine? this is too wierd.
>

LoL Just got off a chat session with the tech at Belkin. According to him I
have to register the MAC of the NIC with Charter to get this to work.

Make any sense to anyone else?

Sam, always thought a NIC is a NIC is a NIC

"Sam C." wrote:

> Hmm, don't remember what the node said. I'll check it when I get home (work,
> it's the curse of the computer geek)
> I just hope we can find an answer *fast*, I need to get this computer back
> to it's owner so I can get the money I've got sunk into it back.
>
> Sam,and I agree, it's nice to know I'm not the only one pounding my head
> against the wall
>
> Do these boards ever work correctly? I keep gettin an error message and
> having to hit back to try to repost....eesh...is it Monday again?
> "tom" wrote:
>
> > plus, i am kind of glad that this has happened to someone else. the more the
> > merrier (and the hope that this has happened many times before, and the fix
> > is as easy as a quick registry adjustment)
> >
> > "tom" wrote:
> >
> > > sam, read my post a few down from yours..... the exact same thing! does your
> > > node type come up as unknown like mine? this is too wierd.
> >

that's one that i have never heard.... keep me posted

Well, got off the phone with Charter. I was right, guy didn't know what he
was talking about.
On a good note, talked to Sanjeev at MS on the chat applet, and there's a
patch for this situation apparently. When I get his email I'll post the URL
so you can try it.

Sam C, I hope this works, I'm at my wits end.

"tom" wrote:

> that's one that i have never heard.... keep me posted

atta boy, keep up the good work!

heh well, I downloaded the patch...no such luck.
Altho I did manually input the IP and DNS of my working computer in and it
says it's connected...can't browse but it's connected. Time to figure out
how to mess with DHCP I guess.

The URL for the patch (who knows, may work for you!) is:


http://www.microsoft.com/downloads/details.aspx?FamilyID=17d997d2-5034...bb-b74d

Sam C, HTH

"tom" wrote:

> atta boy, keep up the good work!

Surrre, as soon as I post that this thread vanished, the link decides to work
again.
At any rate I got the issue resolved on the computer on my bench:

1. Install the patch (doesn't seem to do anything to the naked eye but it
must've done something)
2. Unplug the cable modem for about 5 minutes
3. Plug the cat5 cable back into the modem
4. Plug the modem back in
5. Check the settings in IE Internet tools to make sure it's still set to
autodetect settings
6. Disable the firewall
7. Click "repair" on the network connection
8. At this point I had my connection back
9. Re-enable the firewall
10. Reboot the computer to make sure the changes stay active.

Also, as an aside, before I did all of this the ipconfig /all displayed an
unknown node and I was able to manually enter a working IP from my other
computer that connected to the web on the modem and it stated it was
connected (couldn't browse the web tho)

So, I hope this helps you,

Sam C, feel free to send an email to strahan_lcaf(AT)hotmail(DOT)com

"Sam C." wrote:

> heh well, I downloaded the patch...no such luck.
> Altho I did manually input the IP and DNS of my working computer in and it
> says it's connected...can't browse but it's connected. Time to figure out
> how to mess with DHCP I guess.
>
> The URL for the patch (who knows, may work for you!) is:
>
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=17d997d2-5034...bb-b74d
>
> Sam C, HTH
>
> "tom" wrote:
>
> > atta boy, keep up the good work!

Surrre, as soon as I post that this thread vanished, the link decides to work
again.
At any rate I got the issue resolved on the computer on my bench:

1. Install the patch (doesn't seem to do anything to the naked eye but it
must've done something)
2. Unplug the cable modem for about 5 minutes
3. Plug the cat5 cable back into the modem
4. Plug the modem back in
5. Check the settings in IE Internet tools to make sure it's still set to
autodetect settings
6. Disable the firewall
7. Click "repair" on the network connection
8. At this point I had my connection back
9. Re-enable the firewall
10. Reboot the computer to make sure the changes stay active.

Also, as an aside, before I did all of this the ipconfig /all displayed an
unknown node and I was able to manually enter a working IP from my other
computer that connected to the web on the modem and it stated it was
connected (couldn't browse the web tho)

So, I hope this helps you,

Sam C, feel free to send an email to strahan_lcaf(AT)hotmail(DOT)com

"Sam C." wrote:

> heh well, I downloaded the patch...no such luck.
> Altho I did manually input the IP and DNS of my working computer in and it
> says it's connected...can't browse but it's connected. Time to figure out
> how to mess with DHCP I guess.
>
> The URL for the patch (who knows, may work for you!) is:
>
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=17d997d2-5034...bb-b74d
>
> Sam C, HTH
>
> "tom" wrote:
>
> > atta boy, keep up the good work!