Problem connecting to only one WiFi network

[ilprincipe]

Hello,

I am experience a strange problem. My laptop can connect to any public Wi-Fi, expect one.

What happens is as follow: the message says 'connected', but cannot access the Internet. The IP address I see when looking at Status/Support is of the form 192.168.1.x and the Default Gateway is 192.168.1.y. I believe the problem lies here, but have no idea how to resolve.

I have tried to Repair the connection, ipconfig /release /renew command, and from Windows Services, I have stopped and restarted both the DHCP Client and the DNs client...still nothing..every time I reconnect, the connection gives me the same 'Connected' message with no problem, but the same IP 'unresolved' issue, hence to possibility to access the Internet

The network I have problem with is a free public network (TP-Link) which requires no password (in fact it connects with no problem). I even stopped my firewalls to see if anything improves, nothing..
I have scanned for Virus, using Karsperky, still nothing..

It is a little frustrating, because I need to gain access to this TP-Link as it is the free network provided to all resident in my apartment block.

One last thing..it used to work before with no problem. Later on when I experienced similar problems, all I need to do was to connect to a different network, browse the web, and then back on TP-LINk the connection would work. Now, not matter what, it still doesn't work

thanks for the help

[johnwill]

Actually, IP addresses 192.168.1.x are very common for wireless networks.

Try removing any stored wireless network profiles from the machine, then searching for new networks and connecting.

[ilprincipe]

hello,
thanks for your reply.. I have tried as you suggest to delete the profile and reconnect, but the problem remains.

I have notices when trying to Repair the connection, i get an error message "cannot clear DNS cache'. I have tried to do this manually via command prompt and ipconfig command, but still nothing.

[johnwill]

TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.




Try these simple tests.

Hold the Windows key and press R, then type CMD (COMMAND for W98/WME) to open a command prompt:

In the command prompt window that opens, type type the following commands one at a time, followed by the Enter key:

NOTE: For the items below in red surrounded with < >, see comments below for the actual information content, they are value substitutions from the previous IPCONFIG command output!

IPCONFIG /ALL

PING <computer_IP_address>

PING <default_gateway_address>

PING <dns_servers>

PING 206.190.60.37

PING yahoo.com

Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.

<computer_IP_address> - The IP Address of your computer, obtained from the IPCONFIG command above.

<default_gateway_address> - The IP address of the Default Gateway, obtained from the IPCONFIG command above.

<dns_servers> - The IP address of the first (or only) address for DNS Servers, obtained from the IPCONFIG command above.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.

[ilprincipe]

thanks for your detailed instructions
I did as you suggest, the cmd commands all gave positive results, but when trying to 'repair' the connection, I still get the same error message 'unable to clear DNS cache'.

HOWEVER, the connection now works...so your input has helped me (even if I don't understand why I get the same error message).

thanks again, much appreciated

[johnwill]

Check the event log and see if there are any clues why that error still appears.