ADSL networking - no Internet access

[Kern]

I am currently working on a system with a built in Ethernet controller
hooked to a Westell 7500 ADSL Modem Router. 2 other computers have no
problem connecting through this so I have ruled out the router as the
problem. However the 3rd keeps coming up with the network 'name' as
the routers wireless SSID even though the connection is wired. I have
uninstalled and reinstalled the Ethernet controller drivers, done
Netsh to both the TCP/IP and Winsock, confirmed DHCP is enable
and automatic IP address assignment is enabled. Checked all the
networking services that I have been able to find out about to make
sure that they are in their proper states, and checked the Winsock
integrity through MSINFO32. I have also been able to access the
router settings through one of the other working computers
and see that the router does in fact see the computer with the
problem and has assigned it an IP address. I am able to ping
the router with success but still the problem computer is not
getting Internet access.

Additionally, and I think this has something to do with the
problem, the problem computer does not show any network devices/
computers at all when that is opened. Not even itself.
(Network entry on right side of Start Menu).

I've even tried static IP address assignment without success.

At this point I'm without a clue as to what to do since I,
unfortunately do not have a complete knowledge and understanding
of the workings of Windows network components.

Help? Please?

 

[GlowingBlueMist]

I am currently working on a system with a built in Ethernet controller
hooked to a Westell 7500 ADSL Modem Router. 2 other computers have no
problem connecting through this so I have ruled out the router as the
problem. However the 3rd keeps coming up with the network 'name' as
the routers wireless SSID even though the connection is wired. I have
uninstalled and reinstalled the Ethernet controller drivers, done
Netsh to both the TCP/IP and Winsock, confirmed DHCP is enable
and automatic IP address assignment is enabled. Checked all the
networking services that I have been able to find out about to make
sure that they are in their proper states, and checked the Winsock
integrity through MSINFO32. I have also been able to access the
router settings through one of the other working computers
and see that the router does in fact see the computer with the
problem and has assigned it an IP address. I am able to ping
the router with success but still the problem computer is not
getting Internet access.

Additionally, and I think this has something to do with the
problem, the problem computer does not show any network devices/
computers at all when that is opened. Not even itself.
(Network entry on right side of Start Menu).

I've even tried static IP address assignment without success.

At this point I'm without a clue as to what to do since I,
unfortunately do not have a complete knowledge and understanding
of the workings of Windows network components.

Help? Please?

Does the problem PC actually have a wireless adapter installed, even if
you don't think it being used? If this is a laptop, many have a switch
to disable the wireless entirely.

Have your tried a different cable between the router and the problem PC?

Have you physically swapped the ports on the back of the router between
a good PC and the problem PC?

With the PC set to get it's IP address from the router, not static, open
a command prompt window. This can usually be found in Start | All
Programs | Accessories | Command Prompt.
Once the black Command Prompt window is open enter in the following
sequence of commands and wait a minute or so for them to function if
they do not respond immediately.

ipconfig /release

clr

ipconfig /renew


The above clr followed by the carriage return or enter key is used to
blank the data that appeared on the screen from the /release entry.
Removing that data will make sure the info you read after the /renew is
the actual "current" data as far as the computer is concerned.

After the ipconfig /renew has finished scrolling on the screen you can
scroll the window up/down until you see a line that reads
"Ethernet adapter Local Area Connection:" A few lines below that there
will be an entry that starts with "IPv4 Address". If that address
starts with a 169 then the computer is not seeing the router's response
when it asks for an IP address. What you should see is the actual IP
address that the router has assigned to the PC during the /renew
command. Routers do not assign any address values that start with 169
to PC's.

I keep a long Ethernet cable around just for testing problems when I
want to bypass cables buried inside a wall or ceiling panels.

Purchasing one of those two-part Ethernet testers at your local home
center will go a long way to eliminating future cable problems as well.
Even store bought 4 foot cables go bad or be wired incorrectly. A
quick scan with the tester and you "know" the cable is not the problem.

Here is a eBay link to a tester similar to what you can purchase at many
"home centers". A few of them have even been known to give you one of
these testers when you purchase a box of Ethernet cable. >
http://cgi.ebay.com/Network-RJ45-RJ...emZ120483275951QQcategoryZ58300QQcmdZViewItem

I don't endorse the vendor nor have I purchased anything from them. I
merely provide it as an example of what is available with out having to
spend much.

 

[Char Jackson]

Does the problem PC actually have a wireless adapter installed, even if
you don't think it being used? If this is a laptop, many have a switch
to disable the wireless entirely.

Have your tried a different cable between the router and the problem PC?

Have you physically swapped the ports on the back of the router between
a good PC and the problem PC?

With the PC set to get it's IP address from the router, not static, open
a command prompt window. This can usually be found in Start | All
Programs | Accessories | Command Prompt.
Once the black Command Prompt window is open enter in the following
sequence of commands and wait a minute or so for them to function if
they do not respond immediately.

ipconfig /release

clr

ipconfig /renew

Minor correction, which I only noticed because I've been known to make
this exact same mistake. The command is "cls" rather than "clr",
presumably meaning 'clear screen'.

The above clr followed by the carriage return or enter key is used to
blank the data that appeared on the screen from the /release entry.
Removing that data will make sure the info you read after the /renew is
the actual "current" data as far as the computer is concerned.

After the ipconfig /renew has finished scrolling on the screen you can
scroll the window up/down until you see a line that reads
"Ethernet adapter Local Area Connection:" A few lines below that there
will be an entry that starts with "IPv4 Address". If that address
starts with a 169 then the computer is not seeing the router's response
when it asks for an IP address. What you should see is the actual IP
address that the router has assigned to the PC during the /renew
command. Routers do not assign any address values that start with 169
to PC's.

I keep a long Ethernet cable around just for testing problems when I
want to bypass cables buried inside a wall or ceiling panels.

Purchasing one of those two-part Ethernet testers at your local home
center will go a long way to eliminating future cable problems as well.
Even store bought 4 foot cables go bad or be wired incorrectly. A
quick scan with the tester and you "know" the cable is not the problem.

Here is a eBay link to a tester similar to what you can purchase at many
"home centers". A few of them have even been known to give you one of
these testers when you purchase a box of Ethernet cable. >
http://cgi.ebay.com/Network-RJ45-RJ...emZ120483275951QQcategoryZ58300QQcmdZViewItem

I don't endorse the vendor nor have I purchased anything from them. I
merely provide it as an example of what is available with out having to
spend much.

I have that exact tester and while it's nothing fancy, it works fine.
Mine came directly from China with a free leather carrying case and
cost me a whopping $4.99 with free shipping. I wonder how they made
any money on it at all.

 

[GlowingBlueMist]

On 2/21/2011 4:13 PM, Char Jackson wrote:

Minor correction, which I only noticed because I've been known to make
this exact same mistake. The command is "cls" rather than "clr",
presumably meaning 'clear screen'.

<snip>
Yep, Char, you caught me with my fingers doing the typing and not the
brain. Clearing the screen was the intended result as you surmised.

 

[russ]

I am currently working on a system with a built in Ethernet controller
hooked to a Westell 7500 ADSL Modem Router. 2 other computers have no
problem connecting through this so I have ruled out the router as the
problem. However the 3rd keeps coming up with the network 'name' as
the routers wireless SSID even though the connection is wired. I have
uninstalled and reinstalled the Ethernet controller drivers, done
Netsh to both the TCP/IP and Winsock, confirmed DHCP is enable
and automatic IP address assignment is enabled. Checked all the
networking services that I have been able to find out about to make
sure that they are in their proper states, and checked the Winsock
integrity through MSINFO32. I have also been able to access the
router settings through one of the other working computers
and see that the router does in fact see the computer with the
problem and has assigned it an IP address. I am able to ping
the router with success but still the problem computer is not
getting Internet access.

Additionally, and I think this has something to do with the
problem, the problem computer does not show any network devices/
computers at all when that is opened. Not even itself.
(Network entry on right side of Start Menu).

I've even tried static IP address assignment without success.

At this point I'm without a clue as to what to do since I,
unfortunately do not have a complete knowledge and understanding
of the workings of Windows network components.

Help? Please?


hi there,

i had a similar problem awhile ago, in the end it was the networking
portion on my m/b. i went and got a usb modem, plugged it in and all has
been good since. hope this helps.

russ