Return of the "Limited or No Connectivity" Thread

Boyd

New Member
Reaction score
0
I know some people have had this issue in the past and I was wondering if anyone had come up with a quantifiable response to the issue?

My Scenario: Custom built a PC for my neighbor after the backlight on their 5 year old notebook went out. I built the unit in my office, installed XP Pro, updated, connected to my network, transferred files and settings, took the unit next door for installation. Hooked it all up, turned it on... "Limited or No Connectivity."

Grrr...

So I started with "the usual suspects".
-jiggled the cables
-power cycled the cable modem (reset)
-swapped ethernet cable
-released and renewed with ipconfig
-reset winsock catalog
-tried setting up a new network with the network wizard
-tried manually setting the IP address, after calling the ISP and getting "everything looks good on this end... your IP is..."
-I even went next door, got my laptop, hooked it up to the cable modem..

Limited or No Connectivity... on my Vista laptop. ugh. Two systems, one XP Pro, one Vista... and bot have limited or no connectivity when connected directly to the cable modem. (the VOIP-telephony on the cable modem works fine, btw)

Am I correct in assuming the issue lies with the ISP at this point?

Should I try to hook up a router? Would that help? If so, why?

:confused::confused::confused:
 
Last edited:
For vista open the command prompt(admin mode) and issue the following commands, hit return after each line to apply it. See if that works.

ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset all
netsh int ip reset
netsh winsock reset
 
I've run into this problem with Vista systems on networks with routers running outdated firmware. You can blame Vista or blame the router manufacturer, but every time, flashing to the newest firmware on the router fixes the problem, so I blame the router manufacturers.
 
I've run into this problem with Vista systems on networks with routers running outdated firmware. You can blame Vista or blame the router manufacturer, but every time, flashing to the newest firmware on the router fixes the problem, so I blame the router manufacturers.

Thanks for the heads up. However, there's no router involved yet.

Also, the issue is present in both computers (XP Pro and Vista).
 
To rule out the NIC, I installed a different NIC on-site. [modem brand is Arris, model: TM602G]

Still having the "limited or no connectivity" issue.

I also tried the previously mentioned steps.

I changed the speed setting to 100 half duplex, 10 half duplex, etc... no change.

After an hour of fiddling, I decided to bring the system back to my shop (next door) and continue fiddling, as it is nearly dinner time.. and I could tell that my neighbor was getting agitated. (apparently the elderly are ALL about a rigidly structued routine) :)

Plugged it in to my Residential Gateway... bam, connected, DHCP working flawlessly, etc. *shrug*

How do I get the ISP to admit that it might be an issue with their equipment, even though they see a "valid" IP?
 
It occurs to me that I have no idea what MAC address to spoof the NIC to. Meaning, I have no idea what MAC address the cable modem is expecting to see.

*shrug*

Gonna have to call the ISP again, I suppose.
 
I BELIEVE that you need to pull the battery on these cable/phone combinations to get a full reset. Always a scary time waiting for everyting to sync up.

This may solve the problem.
 
The cable modem was switched out while I was building the PC offsite. The client was having difficulty with thier voip phone service, so the ISP changed the modem out. When I arrived with the new PC, is when we started having the "limited or no connectivity" issue.

The ISP is Cox Communications, not Comcast.

Overall, it's just an annoying situation. I set up an appointment for the ISP to send a technician this Saturday. My client has asked that I be present for that appointment. I'm frustrated because I worry that this scenario makes me appear ignorant or lax.

I even tried a Linux Boot disk, which on my systems at my house, connects just fine. Also tried UBCD4win, which also works fine on my network.

Here's hoping that the issue *IS* with the ISP's equipment, otherwise I'll have to pay my client for their service call. Not to mention, still be without a resolution to the issue.

:eek:
 
These are tough. I'm 99% convinced you have a MAC issue that won't be cured until you get a full reset.

Spend a little time at dslreports.com (I know it's not DSL) and enter Cox + MAC.

I'll bet - I know - you'll find help.

Good luck.
 
Back
Top