Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Router won't let me connect to internet 1

Status
Not open for further replies.

ostrich69

Technical User
Apr 8, 2004
49
Ok, I've been having this problem for a few weeks now, and I have no idea how to fix this problem.

Basically what happened is that I usually leave my computer on overnight, and one morning, for no apparent reason, when I tried to use the internet, I was offline. I did not change any settings, did not upgrade any hardware, everything had remained the same.

I live in Toronto, Canada, and my ISP is Rogers, I have a 5 mb cable modem. I have a PC running Windows XP Pro, and a laptop running Windows Home Edition.

I am able to connect to the internet now because I am bypassing the router, I have a straight connection from cable modem > PC. If I try to go from cable modem > router > PC, I am unable to connect to the internet.

When I am connected to the router:
[ul]
[li]ping localhost works. [/li]
[li]pinging the router works. [/li]
[li]pinging externally, to the internet does not work.[/li]
[li]192.168.100.1 is supposed to be the address for my cable modem, and i cannot connect to it like I can connect to my router by using 192.168.0.1[/li]
[li]ipconfig says that my IP is 192.168.0.100 however when im in the router settings, under the Status/WAN tab, it says "DHCP Client Disconnected" and IP address/Subnet Mask/Default Gateway/DNS are all 0's. [/li]
[li]I can release my IP, I cannot renew it, doing so gives me a timeout error[/li]
[li]I have version 2.50 firmware[/li]
[li]I have tried using other cables, this did not resolve my problem[/li]
[li]I have tried going to default settings, this did not work[/li]
[li]DMZ is enabled[/li]
[/ul]
Here are the results for ipconfig /all while being connected to the router:

Windows IP Configuration

Host Name . . . . . . . . . . . . : [removed]

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter

Physical Address. . . . . . . . . : [removed]

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::20c:6eff:fe6b:d430%4

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : May 9, 2005 4:59:51 PM

Lease Expires . . . . . . . . . . : May 16, 2005 4:59:51 PM

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

Here are the settings for ipconfig /all when I am not going through the router:

Windows IP Configuration

Host Name . . . . . . . . . . . . : [removed]

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mtwd.phub.net.cable.rogers.com

Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter

Physical Address. . . . . . . . . : [removed]

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 69.197.62.199

Subnet Mask . . . . . . . . . . . : 255.255.255.128

IP Address. . . . . . . . . . . . : fe80::20c:6eff:fe6b:d430%4

Default Gateway . . . . . . . . . : 69.197.62.129

DHCP Server . . . . . . . . . . . : 24.153.23.11

DNS Servers . . . . . . . . . . . : 24.153.23.66

24.153.22.67

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : May 9, 2005 4:30:24 PM

Lease Expires . . . . . . . . . . : May 16, 2005 4:30:24 PM

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : [removed]

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : mtwd.phub.net.cable.rogers.com

Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : [removed]

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 2002:45c5:3ec7::45c5:3ec7

Default Gateway . . . . . . . . . : 2002:836b:213c:1:e0:8f08:f020:8

2002:c058:6301::c058:6301

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : mtwd.phub.net.cable.rogers.com

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : [removed]

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:69.197.62.199%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

Can anyone help with this problem?
 
1) Some cable modems store the MAC address of the last device they're connected to. Did you unplug the modem for a minute or so before re-connecting the router so as to flush the MAC address?

2) Have you tried a hard reset on the router?

You may have had a power surge that toasted the router.
 
It's definately a router issue, and absolutely nothing to do with the OS.. so it's not a WinXP issue..

I would do as bygeek says and hard reset the router, as you are receiving DHCP from the cable modem, but not from the router, you have ruled out both the cable modem and computer from being the piece that is broken.

Computer/Network Technician
CCNA
 
He IPCONFIG results show a perfectly good DHCP session with the router.

"bygeeks" suggestion is the reason that broadband routers have a MAC cloning feature. Use the feature in the router to clone the MAC address of the PC in the router setup.

Your IPCONFIG will return the MAC address as "Physical Address"

 
For what it's worth, the exact same thing happened to me a couple of weeks ago. I have Adelphia as my cable/broadband
ISP, and they had "disabled" my connection because they claimed that their software had detected a MUCH HIGHER than normal amount of data going to and from my address.

To Adelphia this meant that I must be running a Web server or some other kind of server inviolation of the terms of
my contract with them.

It took three, hour long phone calls over a span of 4 days
to convince them that I do not have a Server running in my home, and that the reason they were seeing a different MAC address than before is that my cable modem had been zapped
by lightening and I had replaced it with a spare I keep on hand.

Papa4
 
Bcaster is right clone the MAC to the PC that works when hock up directly. It also helps to power down all equip. then turn on the cable modem first wait for it to sink up then power up the router, then the PC. Some cable modems has reset buttons then when pushed will have then reset the MAC that are looking for. holding in the reset while powering up the modem dose a more thorough hard reset on some models.
 
I was referring to bygeek's #2 suggestion, regardless of the DHCP session, he successfully connects when removing the router from the equation.

So if you had your router working before, I would probobaly assume the router is bad.

Computer/Network Technician
CCNA
 
If the cable ISP suddenly began enforcing MAC authentication, it would explain the bahvior seen.

Clone the PC workstation MAC to the router.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top