internet on a secure site

[Keef]

If it works OK connected "wired" to the same network, then that narrows down the problem a bit.

Does the wireless device on your computer "see" the network you're trying to connect to? Can you then "Connect" to it? Is it WEP, or WPA, or what security, and is it asking you for the code?

If you aren't getting as far as connecting to the wireless bit,then you will get that "Windows default" 169.xxx.xxx.xxx IP address - which will do nothing for you.

If your wireless connection reports that you are connected to the server, what else does it tell you? The "Properties" ought to tell you something - even if not an IP address.

What information do you get at that stage?

I'd say step 1 is to be sure you are connected to the network. Once that's done, the rest should be easy. From my experience, getting the wireless bits to "see" and accept each other is the tricky bit.

[foxmoth]

If you read my earlier posts you will see that I can connect to the network OK but it just says "local only" and I cannot get onto the internet. There is another computer on the network that accesses wirelessly and that works OK on the net albeit a bit slowly (but I think that is another issue).

[Keef]

If it's "local only", and is connecting but isn't getting an IP address from the DHCP server, it sounds as if the server is running some kind of security protocol - maybe MAC address checking, maybe "fixed IP addresses only" for all wireless connections. I do that with my home network: if you know the WEP code, you still can't connect to the Internet through it. I tell it your MAC code, and the IP to give you.

This thread may be some help.

[Keef]

Is it a Vista, or an XP machine?

I've never used Vista (other than to remove it for several non-PC-literate friends), but it seems there are additional hurdles to be jumped (or disabled) to make WiFi work.

[Keef]

Clutching at straws now...

Try opening a "cmd" window, then type:

ipconfig /release

ipconfig /renew

[Keef]

Last suggestion:

• Go to Start > Connect to.
When the Connect to a network dialog window is displayed, click Open Network and Sharing Center.
When that window opens, click on Manage network connections.
You may see multiple adapters available in this window.
Right-click the adapter named Wireless Network Connection (or something similar) and click Properties.
Wireless Network Connection Properties will display.
Highlight Internet Protocol Version 4 (TCP/IPv4) and click Properties.
Internet Protocol Version 4 (TCP/IPv4) Properties will appear.
Under the General tab, make sure that both
Obtain an IP address automatically and
Obtain DNS server address automatically are selected.
Reconnect to the wireless network.

[foxmoth]

Followed Keefs link in post #23 and was doing fine until

Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\P arameters\Interfaces\{GUID}
In this registry path, click the (GUID) subkey that corresponds to the network adapter that is connected to the network.

How do I tell which to go for? I have:-
{3a539854-6a70-11db-887c-806e6f6e6963}
{50400352-FDC1-4DF1-8CBB-48264FCD8CFC}
{8595E907-0C99-4DD2-9B9D-36D150B7433B}
{BBFE635B-99B1-4D30-AA28-9218EE60274C}


No idea how to tell which one is connected to the network

[foxmoth]

Sorted!

Looking at the subkeys I found the one with the same IP address and then followed the guide, did not think it had worked at first but did a restart and Bingo - all OK.
Thanks Keef and everyone else that tried to help.

[Saab Dastard]

That's a very useful link to a very revealing article!

An outdated network router may not function correctly when you use it together with new networking features in Windows Vista

Typical MS insisting that it's the rest of the world that's doing it wrong. Just looking at the number of hits in google for "DHCP BROADCAST flag" suggests that "outdated" to MS = "mainstream" for everyone else.

Such breathtaking arrogance never ceases to amaze.

SD