LAN Reconfiguration help please

Started by dlorde, Mar 10, 2008, 00:07:32

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

dlorde

I'm running a wireless LAN at home using a Belkin modem/router. At present, my WinXP PC is Ethernet wired directly into the router. Other devices are wirelessly connected. I need to reconfigure the LAN so that the PC is wirelessly connected to the router.

I've got a Belkin USB wireless LAN adapter which I installed on the PC, and it picks up the router network signal fine. However, when I disable the PC Ethernet adapter, and tell WinXP that I want to use the wireless network, it sees the wireless adapter, and lets me select the wireless network to connect to, but fails to establish the connection, saying that it can't get a valid network address. It also says the network key isn't correct (I'm using WPA security), but it is the same key as the other devices use, and they're fine.

I don't know enough about how these things work together to fix the problem.

The IP configuration disagnostics are below. Any suggestions?

IP Configuration Diagnostic
Invalid IP address

info AutoNet address detected: 169.254.194.150
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
error Error renewing the IP address: The semaphore timeout period has expired. 
info AutoNet address detected: 169.254.194.150
action Automated repair: Reset network connection
action Disabling the network adapter
action Enabling the network adapter
info Network adapter successfully enabled
info Zero (0.0.0.0) IP address detected
action Manual repair: Reboot modem
info AutoNet address detected: 169.254.194.150
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
error Error renewing the IP address: The semaphore timeout period has expired. 
info AutoNet address detected: 169.254.194.150
action Manual repair: Verify wireless network key
info AutoNet address detected: 169.254.194.150



Wireless Diagnostic
Wireless - Service disabled

Wireless - User SSID

action User input required: Specify network name or SSID
Wireless - First time setup

info The Wireless Network name (SSID) to which the user would like to connect = DLorde Wireless.
Wireless - Radio off

info AutoNet address detected: 169.254.194.150
Wireless - Out of range

Wireless - Hardware issue

Wireless - Novice user

Wireless - Ad-hoc network

Wireless - Less preferred

Wireless - 802.1x enabled

Wireless - Configuration mismatch

Wireless - Low SNR




WinSock Diagnostic
WinSock status

info All base service provider entries are present in the Winsock catalog.
info The Winsock Service provider chains are valid.
info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback communication test.
info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback communication test.
info Provider entry RSVP UDP Service Provider passed the loopback communication test.
info Provider entry RSVP TCP Service Provider passed the loopback communication test.
info Connectivity is valid for all Winsock service providers.



Network Adapter Diagnostic
Network location detection

info Using home Internet connection
Network adapter identification

info Network connection: Name=Local Area Connection, Device=Broadcom NetXtreme 57xx Gigabit Controller, MediaType=LAN, SubMediaType=LAN
info Network connection: Name=Wireless Network Connection, Device=Belkin 54g Wireless USB Network Adapter, MediaType=LAN, SubMediaType=WIRELESS
info Network connection: Name=1394 Connection, Device=1394 Net Adapter #2, MediaType=LAN, SubMediaType=1394
info Network connection: Name=1394 Connection 2, Device=1394 Net Adapter, MediaType=LAN, SubMediaType=1394
info Both Ethernet and Wireless connections available, prompting user for selection
action User input required: Select network connection
info Wireless connection selected
Network adapter status

info Network connection status: Connected



HTTP, HTTPS, FTP Diagnostic
HTTP, HTTPS, FTP connectivity

warn HTTP: Error 12007 connecting to www.microsoft.com: The server name or address could not be resolved 
warn HTTPS: Error 12007 connecting to www.microsoft.com: The server name or address could not be resolved 
warn FTP (Passive): Error 12007 connecting to ftp.microsoft.com: The server name or address could not be resolved 
warn HTTP: Error 12007 connecting to www.hotmail.com: The server name or address could not be resolved 
warn HTTPS: Error 12007 connecting to www.passport.net: The server name or address could not be resolved 
warn FTP (Active): Error 12007 connecting to ftp.microsoft.com: The server name or address could not be resolved 
error Could not make an HTTP connection.
error Could not make an HTTPS connection.
error Could not make an FTP connection.


Rik

My first thought would be that the wireless adaptor doesn't support WPA. Try disabling the wireless security temporarily and see if you can then connect. AAMOI, why do you want to go wireless for the PC, a wired connection is faster, more secure and more relaible.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

dlorde

Quote from: Rik on Mar 10, 2008, 00:15:19
My first thought would be that the wireless adaptor doesn't support WPA. Try disabling the wireless security temporarily and see if you can then connect
It does support WPA according to the manual, but I'll follow your suggestion and see what happens...

QuoteAAMOI, why do you want to go wireless for the PC, a wired connection is faster, more secure and more relaible.
I have to move the PC to another room, which doesn't have a phone socket nearby... If the result is too slow and unreliable, I guess I'll have to rethink.

Thanks for the suggestions.

Rik

Ethernet cables can be up to 100m per segment, so if you can run a cable easily, length shouldn't be an issue.

If you can't connect without security, come back and we'll have another think.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JB

Quote from: dlorde on Mar 10, 2008, 00:58:48
It does support WPA according to the manual, but I'll follow your suggestion and see what happens...
I have to move the PC to another room, which doesn't have a phone socket nearby... If the result is too slow and unreliable, I guess I'll have to rethink.

Thanks for the suggestions.

Not sure if your move is permanent or temporary and therefore how much you want to spend.

Just to say that I use a pair of these powerline ethernet adapters. They work really well and in my case are much more reliable than wireless and extremely secure.

http://www.amazon.co.uk/Max-Value-Mbps-Home-Double/dp/B000TV7FJ4/ref=pd_sbs_ce?ie=UTF8&qid=1205171266&sr=8-9

JB.
JB

'Keyboard not detected ~ Press F1 to continue'

dlorde

Quote from: 6jb on Mar 10, 2008, 17:53:49Just to say that I use a pair of these powerline ethernet adapters.
Now that's a great idea - I've seen them before, but it just didn't occur to me they might be useful now  :blush:

Thanks for the tip :thumb:

Incidentally, I've just activated my connection with IDNet (PIPEX escapee), and I'm immediately getting the fastest speeds I've had with the same line stats as before. One happy bunny  ;D

Lance

Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.