Limited or no connectivity! (Please help!)

  josh.archer 18:04 26 Apr 2009
Locked

Hello, i know that there are several posts all over the web and including on this forum that deal with this issue but no matter what i try i cannot seem to fix my problem. It started a couple days ago when our house router died and was replaced. There are only two computers linked on this router and one of them works however my laptop does not.

I have tried the ipconfig /release and /renew

I have tried uninstalling and reinstalling the network driver

I have used a USB adapter

I have tried using a fixed ip adress

I have tried all kinds of settings and configurations to no avail.

Please help :(

I'm on my last legs here and am hoping that someone far more educated then me in these matters can come to my rescue.

Here is the information on my ipconfig /all if it is any help.


Windows IP Configuration

Host Name . . . . . . . . . . . . : vicariou-e28rby
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 8:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-C0-9F-AF-E5-BC

Ethernet adapter Local Area Connection 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys EtherFast 10/100 Compact USB
Network Adapter
Physical Address. . . . . . . . . : 00-10-60-E7-DE-B3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.181.15
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


Thankyou

  mgmcc 21:50 26 Apr 2009

I see that you have two "wired" ethernet adapters installed in the PC. What happens if you connect to the router with the other adapter?

  MAJ 22:04 26 Apr 2009

Try going to a command prompt (on the laptop) again and typing in:

netsh int ip reset resetlog.txt

press Return and see if it helps.

  josh.archer 00:37 27 Apr 2009

Nothing happens the other ethernet adapter is a ethernet to USB adapter that didn't work either.

Tried the netsh int ip... and it did not resolve the problem :(

  brundle 02:16 27 Apr 2009

Your problem isn't TCP/IP, your adapter isn't picking up a DHCP address from your router as it should. Try another cable, plug into the Realtek adapter rather than adding another potential point of failure with the USB/ethernet converter.

  mgmcc 08:43 27 Apr 2009

I'm not even sure it is a DHCP issue because, if it were, you should still be able to connect with fixed IP addressing which appears not to be the case.

Having repaired the TCP/IP stack with...

netsh int ip reset resetlog.txt

try also repairing the Winsock with the command...

netsh winsock reset catalog

I assume that, when trying fixed IP addressing, you did use an address in the correct subnet (IP address range) for the router, i.e. the third octet (number) of the IP address matched that of the router's IP address? Having replaced the original router, the new one might operate in a different subnet.

  Marskeman 10:18 27 Apr 2009

I've had this problem, justed sorted another with mine. When i had this problem when i made a static ip address on my computer it solved the problem. It was the router no allocating ip addresses. But you say you tried this. The ip address does not look right and there is no default gateway ip.
Your ip address should be 192.168.1.2 but the 2 can be any number within your client range. And your default gateway should be 192.168.1.1. Your ip address looks like windows allocating you on.
I would turn off all encryption and to static again making sure you fill in your DNS as well.

Marskeman

  mgmcc 12:50 27 Apr 2009

>>> Your ip address should be 192.168.1.2 but the 2
>>> can be any number within your client range. And
>>> your default gateway should be 192.168.1.1

Not necessarily. Netgear DG834 and D-Link routers use the 192.168.0.0 subnet; Belkin use the 192.168.2.0 subnet; Buffalo use the 192.168.11.0 subnet, so the third octet of the IP address may not be "1", which is why I suggested the new router might be operating in a different subnet from the previous one.

This thread is now locked and can not be replied to.

Elsewhere on IDG sites

OnePlus 5 review

Alice Saey's mesmerising animation for Dutch singer Mark Lotterman

iPad Pro 10.5in (2017) review

Comment booster votre iPhone ?