Re: Network Error: "Limited or no Connectivity"

Tech-Archive recommends: Speed Up your PC by fixing your registry

In article <1140992320.534804.185780@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Verdagon" <Verdagon@xxxxxxxxx> wrote:
That's strange... it doesn't work even when its connected through a
cable. Maybe I should have checked that beforehand...

So now that I know it's not a problem with the physical connection;
this "limited or no connectivity" error happens regardless of how I
connect my laptop to the router. So what's going on now?

Here's an ipconfig for when I was connected via cable:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ion
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : LAN-Express AS IEEE 802.11g
miniPCI
Adapter
Physical Address. . . . . . . . . : 00-0E-9B-6E-B6-8E

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-01-4A-0A-15-02
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.173.9
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Thanks

- E

Connect the computer's Ethernet port to a regular LAN port on the
router. Don't connect it to the uplink port or to the WAN port.

If you haven't done so already, unplug the router from the AC power,
wait a few seconds, and plug it back in. That might get everything to
work.

It's possible that the router's DHCP server isn't working. To see,
configure the computer's wired network connection with a manual IP
address of 192.168.1.2/255.255.255.0 and try to connect to the
router's web interface, which I'm assuming is at http://192.168.1.1.
For Internet access, set the computer's Default Gateway and DNS Server
addresses to 192.168.1.1, too.

It's possible that the router has become defective.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
.

Relevant Pages

  • Re: Using Remote Desktop From an SBS Domain
    ... when you tried to RDP while attached directly to a port on your router? ... So if 3389 needs forwarded on the client end too then that is what the ... Hopefully next week I can attempt a connection while my ISP watches the ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting up Home Network w/ 2 Routers
    ... successfully got my 2Wire, Netgear, and Linksys playing nicely. ... Connected the LAN port #1 of 2Wire to the WAN port of the Netgear. ... connection type and all for me. ... If you add another router to the mix, just make sure to disable the ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networking Question - VLANs on SBS 2003 Premium SP1
    ... port on the old router so I now have a segregated WLAN. ... be sure you do not enable any DHCP server in internal network. ... On the Connection Type page, click Broadband, and then click Next. ... On the Network Connection, You must enable and configure the network ...
    (microsoft.public.windows.server.sbs)
  • How did they get behind my NAT?
    ... this point I panicked and shutdown the VNC service ASAP. ... My question is how the attacker got to my VNC port! ... the internet through the router. ... client connection using local port number 5900 (which was also being ...
    (alt.computer.security)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)