Re: No internet access

"ptreves" <ptreves@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:22889F48-55D8-4878-B40A-E3B3F2DDCCB5@xxxxxxxxxxxxxxxx
> Hello Martin,
>
> Here are a few commands and there corresponding outputs:
>
> 1) telnet www.yahoo.com 80
> Connectin to www.yahoo.com....Could not open a connection to host on port
> 80....Connect Failed

Presuming the above also fails with the IP address
then you have proven that either routing in general
is failing (check with tracert if ICMP is allowed)
OR that you are explicitly blocking outbound requests
for destination port 80 or the expected responses.

> 2) ipconfig
> Windows 2000 IP Configuration

Is that all?

IPConfig should give at least your IP address.

IPConfig /all should give a page (or more) of stuff.

If you are seeing those - -check your hardware and
drivers in Device Manager to get the NIC working.

> 3) tracert -h 100
> Tracing route to 0.0.0.100 over a maximum of 100 hops
> 1 destination host unreacheable
> Trace complete

First, you almost never need any tracert options or switches
other than the DESTINCTION, so just try:

tracert www.yahoo.com

Or perhaps better (to eliminate name resolution issues):

tracert 68.142.197.76


> ---
> Under the Device Manager, for my Network Adapters I have the following:
>
> Realtek RTL8139/810x Family Fast Ethenet NIC
>
> With a device status saying that 'This device is working properly'. Under
> the Control Panel under the "Internet Protocol TCP/IP" for the Realtek
> adapter, when I press the Properties button, I get the following message:
>
> In order to configure TCP/IP, you must install and enable a network
adapter
> card.
>
> 1) I don't understand this message, my Realtek adapter is enabled. Why am
I
> getting this message ?

My first guess would be "Link Detect" (as I indicated previously).

Check the NIC, "Network and Dialup connections"->properties->
Configure (button) and check for "connector type" or something
similar that offers link detect, 100 Mbps etc.

Chose the proper network speed/connector and try to avoid a
"link detect" setting.

OR make sure this NIC is plugged into a working hub.

You might have to swap out the NIC if this doesn't help

Broken NICs are uncommon (today) but they do happen.


.

Loading