unable to connect in XP

jmwombat · 30-Apr-2009, 04:42 PM #1

I recently set up wireless internet access using a TP-Link Tl-Wr541g router & a Tl-WN321G adaptor.

Although I was originally able to connect from XP, I am now unable, as the connection stalls at the at the 'aquiring network address' stage. I set up static IP, which then connected, but was unable to resolve DNS. The strange thing is, under jaunty (ubuntu 9.04) I have no problems, and the connection takes about 2 seconds.

I recently tried to set up an ad-hoc network, but failed. Could this be affecting it?

Any help appreciated.

P.S. Could I reset this with ipconfig? I'm used to Linux, and not scared of the command line.

Jason08 · 30-Apr-2009, 05:06 PM #2

Hi and welcome to TSG.
Go to start>run. Type cmd, then in the command prompt ipconfig/all. If you see a DNS listed, enter that in the static IP box for the DNS preferred, and the alternate DNS can be left blank if there is only 1 DNS listed.

**TerryNet** · 30-Apr-2009, 06:20 PM #3

Setting up an ad-hoc wireless with the same SSID as your Access Point would certainly lead to problems. Otherwise there should be no issue.

Disable encryption on the router and use dynamic addressing on your wireless adapter and try to connect. If successful you can probably re-enable encryption and reconnect. If unsuccessful please show ...

Start, Run, CMD, OK to open a command prompt:
(For Vista type CMD in the Search box after Start)

Type the following command:

IPCONFIG /ALL

[Note that there is no space between the slash and ALL.]

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

If necessary use a text file and removable media to copy the results to a computer with internet access.

jmwombat · 02-May-2009, 10:36 AM #4

I have just been able to connect with no security. However, XP still throws in the towel, even at WEP. Jaunty still connecting fine..

IPCONFIG shows no dns servers, so static IP isn't working. However, there is no dns error on an open network.

Help! I really don't want to use an unsecured network!

jmwombat · 02-May-2009, 10:38 AM #5

Just got WEP working -used 128 bit key not 152. Rebooting & trying WPA...

JohnWill · 02-May-2009, 11:18 AM #6

There is no such thing as 152 bit WEP.

jmwombat · 02-May-2009, 11:20 AM #7

WEP connected on reboot, but not to the internet, so I took the ipconfig/all settings & tried static IP & WPA, but had trhe same problem. I then tried using the wrong network key, which also worked?!

JohnWill · 02-May-2009, 11:22 AM #8

I have no idea what is going on, or what you're actually doing.

jmwombat · 02-May-2009, 11:34 AM #9

Sorry. My router lists something called "152 bit WEP" (I tried to put a picture here but failed).

I rebooted after managing to connect using insecured and 128-bit WEP, and after logging in loaded internet explorer, which worked.
However, when I went (to ie) to change to WPA, it was no longer working. I then took the ipconfig values I'd obtained and changed to static IP in the TCP/IP section.

This claimed it had 'connected to TP...' but could not access the internet.

I tried a different (and wrong) message and got the same 'connected to..' .

I assume something is wrong - but is it bad enough for a re-install ( and the usual headache of configuring grub, installing software etc...)?

jmwombat · 02-May-2009, 11:49 AM **#10**

changed back to dynamic IP from static I.P. Now I can connect over an unsecured network.

**TerryNet** · 02-May-2009, 02:35 PM **#11**

Now make sure you have the latest driver for the wireless adapter and then try WPA again.

Anytime you switch from one type of encryption to another, or change the encryption key, if you have a problem it's best to disable encryption, connect, and then go forward with the new encryption/key. Usually not necessary, but just keeps things cleaner when you encounter problems.

jmwombat · 02-May-2009, 02:44 PM **#12**

Quote:

Originally Posted by TerryNet

Now make sure you have the latest driver for the wireless adapter and then try WPA again.

Thanks. I'm running the driver on the cd, which is identical to the latest revision on the TP-Link website.

I've just been reading some threads and apparently Kb 8933567 (the hotfix for WPA2 can cause this problem - several people are reporting the same thing. I shall disable & try WPA

jmwombat · 04-May-2009, 07:21 AM **#13**

Didn't work. I shall re-install...

jmwombat · 04-May-2009, 01:57 PM **#14**

Re-installed XP (twice) but still no connection using encryption. Ethernet is working fine.
Wireless works on unsecured network.

**TerryNet** · 04-May-2009, 04:26 PM **#15**

What service pack level are you at now?

You've tried both WEP (with a HEX key) and WPA since the reinstall?

Tag Cloud
access acer asus bios bsod computer crash desktop dns driver drivers error ethernet excel freeze gaming graphics hard drive hardware hdmi internet laptop malware memory monitor motherboard network printer problem ram registry repair router slow software sound trojan ubuntu 11.10 uninstall usb video virus vista wifi windows windows 7 windows 7 32 bit windows 7 64 bit windows xp wireless

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Find the solution to yourcomputer problem!

Find the solution to your
computer problem!