[RESOLVED] Can't connect to Network

[Ozrock]

HI.

OS:XPRO

I have a Netgear WGT624 which is connected to a wired hub and everyone has access to the network and each other -- wired.

Now I introduce a Compex WLA11A USB to my laptop and set the wireless network name and WEP numbers on the Netgear and the laptop.

The laptop can see the network name but cannot connect no matter what I try. I have even taken off the WEP and still can see, but not connect.

I decided to also attach my other wireless router (Compex NetPassage16) to the wired hub to see if the WLU11A (which actually came with the NetPassage) would see the network this way.

The wireless laptop did see the NetPassage but had difficulty acquiring an IP address. In the end it said it would connect with Limited or No Access.

It does show as connected in 'Network Connections' but without a Network IP number.

Summary
It seems that the Laptop WLU11A USB will only work with its NetPassage 'mother' and not the Netgear, which is fine with me, as long as I can get to the network.

The problem is how do I get the laptop a Network IP number it will recognize so it will give me full access to my network.

Hope it all makes sense.

Thanks in anticipation..

oz :?

[Greenstead]

The windows status is a bit misleading. Limited or No Access really means no access at all. It means the WLU11A USB has found the wireless network and asscociated with it but an IP address is refused by the DHCP server in the WGT624 router. Normally this is caused by using an incorrect WEP passcode, but you seem to have checked this by disabling WEP.

It would be helpful to connect the laptop wired to check you can get an IP that way.

[Ozrock]

HI,

Yes that is certainly correct - access at all. I'll give this info which may help..

The overview is WGT624 plugged into Internet cable and into a couple of XPs and to the wired hub. Everything that gets attached gets it own IP 192.168.0.blah and has access to MShome LAN and web.

The WGT624 LAN setup is

LAN TCP/IP
IP Address 192.168.0.1
IP Subnet Mask 255.255.255.0
Use Router as DHCP Server enabled
Start IP 192.168.0.2
End 192.168.0.254



With the Laptop WLA11A and the NP16 plugged into the wired hub I see the network named 'starnet' and using 'Status' I get a IP on the laptop of 169.254.168.113 - 255.255.0.0.

The NP16 auto setup is..

IP Address 192.168.168.1
Network Mask 255.255.255.0
DHCP Start 192.168.168.100
DHCP End 192.168.168.254
DHCP Gateway IP Address 0.0.0.0
DHCP Server Enabled

Yes I have the latest firmware.

If I plug the Laptop into the wired hub I get a good IP of 192.168.0.6 or whatever is available when I plug it in. That wired LAN is called MShome with default setup and all boxes are 192.168.0.blah.

I need the wireless connection as I don't have any cable to where I need to work with the laptop.

Thanks for the help.

oz

[Ozrock]

AH HAAAAAAAAA. I went into the NP16 Setup and re assigned the WEP then chnaegd it to reflect that on the Laptop and whammo.. There it was!

All the IP's on both hubs are still the same as in the previous post.

Nothing else was touched except the WEP reassignment.

I now have another problem which is not wireless related so will post it in the correct place if I can find it.

An over view is..

All boxes can connect and have access to each other except one box which can access out but won't allow access in, even though they can see the dir structure. The message is something like..

The so and so dir is not accessable. You may not have permission etc. The enough server storage is available for this command.

It is the same message on all boxes who try access this one. I will re post now.

Thanks for your help.

oz

[Ozrock]

Looks like i spoke to quickly. Whilst the Laptop does now connect to the NP16 and get an IP of 192.168.0.8, when I try to connect to the MShome network boxes it says .. Path not found.


Thanks

oz

[Ozrock]

Okay fixed now. At last..!

Thanks for your time. It is appreciated.

oz