Net access problem

This could be a DNS issue - can you access the sites with a browser using the IP address rather thatn the FQDN?
http://64.156.132.140
should take you to www.experts-exchange.com

if the IP address gets you there then check out what gateway and DNS you have setup on your client.

Have you checked the Internet Browser settings? Tried installing a new browser like mozilla.

If your pinging sites should be something to do with your browser.

What OS is running on the gateway and the client?
Is the gateway machine set up to route?
Have you tried tracert <name>  to see where the routing falls down?

hi,

To sunray_2003,

   If I connect the DSL modem directly to my client PC, everything runs fine, I mean I can access any site without any problems. Regarding winsock.exe, shud it be executed on my win2k gateway m/c ?

To  juliancrawford,

Nope, Cannot access any of the sites (including google!!) either via domain name or via IP.
To danhalen,

To danhalen,

AM running IE6 and there are no problems with it whatsoever. Have NETSCAPE 7 too and with the same problem .

To wyliecoyoteuk,

On the Gateway computer, WINDOWS 2000  and on the client WIN XP. Am not sure what you mean by setting the Gateway m/c to route. If its performing a tracert from my client PC, then yes, I can do a tracert to any IP/ domain name from my client PC.

for a temp workaround you could use the host or lmhost files to direct the traffic - but something is wrong, have you checked the event viewer for errors?

check out this link for more details on host and lmhost ..
http://www.realcomputerguy.com/lmhosts.htm

Hi guys,

Figure I have narrowed down the problem.  Have something new & weird.

I hooked my client pc (winXP) to the ethernet HUB using a network cable and at the same time removed the Wireless PCMCIA card and Voila, everythings normal as it should be.. I can access any site now from the client mc..

This means there is something wrong in the wireless access. Am using a Airway Transport Wireless Access Point which includes a gateway and on the first access, I had to configure the IPs which I set to DHCP server and nothing to do with accessing websites..

What could be wrong and how do i correct it?

thnx,
sg

check for things in the way of the signal reaching your Access point sometimes walls, and lighting could have an effect on the wireless signal.  Try repositioning them both.  What about the distance, too far...

Am sitting right next to the Access Point! am totally perplexed.. hv mailed the company support but dont expect a fast reply..:(

Must be something in the gateway or AP`s settings.
Is it set to:
a) be a gateway
b) be a proxy

If b, that could be a problem.

You may need to enable or forward port 80 on either the gateway and/or the AP.
Is the firewall set up to allow access to the internet from the wireless card?

on the client machine, run ipconfig /all
and post the result.

the result of the tracert could be useful too.

Hi,

No, am not using any proxy and even with the firewall down, the problem exists.

Fwg is the output from the win XP client machine. AFraid its in portuguese. hv translated some stuff....

C:\>ipconfig /all

Configuration IP do Windows

        Host Name. . . . .: ANI
        Sufixo DNS principal. . . . . . . :
        Node Type. . . . . . . . . . . . : Mixed
        IP Routing enabled. . . . . . . . . : Sim
        WINS Proxy activado . . . . . . . : Não

Adaptador ethernet Ligação de rede sem fios 2:
Ethernet adapter Wireless Network connection 2:

        Sufixo DNS específico da ligação. :
        Descrição . . . . . . . . . . . . : 802.11b WLAN CardBus
        Endereço físico . . . . . . . . . : 00-08-A1-4B-37-66
        DHCP activado . . . . . . . . . . : Sim
        Autoconfiguração activada . . . . : Sim
        Endereço IP . . . . . . . . . . . : 192.168.0.2
        Máscara de sub-rede . . . . . . . : 255.255.255.0
        Gateway predefinido . . . . . . . : 192.168.0.1
        Servidor DHCP . . . . . . . . . . : 192.168.0.1
        Servidores DNS. . . . . . . . . . : 192.168.0.1
        Concessão obtida. . . . . . . . . : sábado, 27 de Dezembro de 2003 11:24
:25
        Concessão obtida válida até . . . : sábado, 3 de Janeiro de 2004 11:24:2
5

Adaptador ethernet Ligação de área local:

        Estado do suporte . . . . . . . . : Suporte desligado
        Descrição . . . . . . . . . . . . : Realtek RTL8139/810X Family PCI Fast
 Ethernet NIC
        Endereço físico . . . . . . . . . : 00-E0-18-9A-68-5F

And the TRACERT

C:\>tracert www.experts-exchange.com

A rastrear a rota para experts-exchange.com [64.156.132.140]
até um máximo de 30 saltos:

  1     3 ms     3 ms     4 ms  192.168.0.1
  2    32 ms    65 ms    30 ms  lgsr1.telepac.net [213.13.135.13]
  3    29 ms    43 ms    26 ms  dial-b1-170-46.telepac.pt [194.65.170.46]
  4    27 ms    24 ms    28 ms  lcatrt1.telepac.net [213.13.135.185]
  5    31 ms    28 ms    30 ms  lisbon1-br1-p61.cprm.net [195.8.10.133]
  6    60 ms    58 ms    59 ms  london1-cr1-p20.cprm.net [195.8.0.94]
  7    62 ms    61 ms    60 ms  sl-gw20-lon-7-0.sprintlink.net [213.206.159.169]

  8    61 ms    59 ms    58 ms  sl-bb21-lon-9-0.sprintlink.net [213.206.128.98]

  9    59 ms    66 ms    60 ms  213.206.131.22
 10    59 ms    61 ms    78 ms  ae-0-51.mp1.London1.Level3.net [212.187.131.1]
 11    61 ms    61 ms    60 ms  so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

 12   132 ms   132 ms   132 ms  so-1-0-0.bbr1.Washington1.Level3.net [212.187.12
8.138]
 13   181 ms   182 ms   180 ms  so-0-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.1
57]
 14   182 ms   183 ms   183 ms  ge-8-1.hsa1.LosAngeles1.Level3.net [64.159.1.201
]
 15   190 ms   186 ms   188 ms  EXPERTS-EXCH.hsa1.Level3.net [209.245.88.50]
 16   187 ms   185 ms   185 ms  www-level3.experts-exchange.com [64.156.132.140]


Trace Completed


Hope this was helpful..

sg

Hi guys,

Solved the problem thnx to  stevenlewis. It was after all a MTU issue (though i had never heard of it before) !!

Thnx to everyone specially  stevenlewis!

cheers and hv a great new year,

sg