Some Wireless networks appears as local only

[Guest]

I have been using wireless network fine until i tried to connect to a public
hotspot and it appears as local only, no internet connection. I tried it with
my mobile pc and WindowsXP and it works fine. I have checked this wireless
hotspot is 801b which is a legacy, could it be that vista wireless connection
software has a problem with legacy hotspots.

 

[Jeff]

Akram,

If you change your battery setting to performance, instead of balanced, it
may correct that.
Some older AP's have issues with the wireless in Vista
chk this KB out:
http://support.microsoft.com/kb/928152

Jeff

 

[Guest]

I am also having the same issues on Vista Enterprise. Although I have
succesfully connected to a WEP wireless network with a Dlink DWL 650+ network
card in my laptop in the past, when attempting to access a WiFi hotspot with
open authentication it fails to get a DHCP address. (169. etc is what i get)

This tells me that the card and the drivers work, although there still seems
to be a problem with Vista somewhere.

I've tried different cards (linksys wireless G), three different types of
software (Dlink, AT&T, Linksys) and several other ideas that people were kind
enough to suggest. (power management, firewall, event viewer etc). I've tried
three ways from sunday to get this machine connected to a hotspot to no
avail. It simply should NOT be that difficult with a new OS.

Anyone else have any suggestions before i remove another Microsoft Windows
Millenium?

 

[Guest]

I am also having the same issues on Vista Enterprise. Although I have
succesfully connected to a WEP wireless network with a Dlink DWL 650+ network
card in my laptop in the past, when attempting to access a WiFi hotspot with
open authentication it fails to get a DHCP address. (169. etc is what i get)

This tells me that the card and the drivers work, although there still seems
to be a problem with Vista somewhere.

I've tried different cards (linksys wireless G), three different types of
software (Dlink, AT&T, Linksys) and several other ideas that people were kind
enough to suggest. (power management, firewall, event viewer etc). I've tried
three ways from sunday to get this machine connected to a hotspot to no
avail. It simply should NOT be that difficult with a new OS.

Anyone else have any suggestions before i remove another Microsoft Windows
Millenium?

You have the latest Wi-Fi card drivers, specially designed
for Vista (and not legacy WinXP drivers) - correct?
You've used the Vista buil-in diagnostics to troubleshoot the connection issue
( netsh wlan ... ) - correct?

--PA

 

[Guest]

Vista drivers are not available - and i doubt that they will be for a legacy
802.11b card, however, the XP drivers worked just fine when i had it
connected to a WEP network. (I'm betting it would connect to anything that
was encrypted). Not sure what this is all about - It's like it stops you from
connecting to an unsecured network or something.

Ahh the Vista built in diagnostics - those are about as good as the ones on
XP, not very. As far as I'm concerned it's a glorified ipconfig /release and
/renew command built into an idiot button. Suffice to say that did not work.

I did start working on the netsh wlan, but after no initial success, i gave
up quickly.
To be honest at this point i was 2 plus hours into attempting to figure out
why i couldnt get the latest and greatest from Micorsoft connected to an open
network....

Thanks for ideas. Any others?

Robert

 

[Guest]

I had the same problem, and as an old Networking hack, finally managed to get
it to work.

There are incompatabilities with Vista and some of the built-in DHCP servers
in routers. As a result, kiss off automatic assignment of network settings
for these routers (wireless or otherwise).

You will have to MANUALLY set your IP info, just like in the old days.
Unfortunately, that also means that you will have to CAN those adapter IP
setting when using true DHCP enabled routers that actually work.

Here is one solution that may work for SOME routers (but it does NOT work
for all of them!)

http://support.microsoft.com/kb/928233/en-us

The reality is that as long as you can connect to the router (i.e. local
only connection) then the manual assignment of the IP info should get you
there.

~~~~~~~~~~~~~~~~~~~~~~

 

[gg]

I had the same problem, and as an old Networking hack, finally managed to get
it to work.

There are incompatabilities with Vista and some of the built-in DHCP servers
in routers. As a result, kiss off automatic assignment of network settings
for these routers (wireless or otherwise).

You will have to MANUALLY set your IP info, just like in the old days.
Unfortunately, that also means that you will have to CAN those adapter IP
setting when using true DHCP enabled routers that actually work.

Here is one solution that may work for SOME routers (but it does NOT work
for all of them!)

http://support.microsoft.com/kb/928233/en-us

The reality is that as long as you can connect to the router (i.e. local
only connection) then the manual assignment of the IP info should get you
there.

~~~~~~~~~~~~~~~~~~~~~~

http://groups.google.co.uk/group/mi...5e28e033f09/fc03f284489f27c2#fc03f284489f27c2

 

[Michael A. Bishop \(MSFT\)]

We've tested quite a number of IGDs for compatibility, but obviously it's
not possible to check every single one. Which IGDs have you found to be
incompatible, other than the ones with the BROADCAST issue?

 

[Guest]

OK...Similar Problem here...

I work for a 25,000 student State University that has open access wireless,
that requires authentication at the university's firewall. This normally
appears as a window that requests user name and password as soon as you open
a browser.

Vista simply won't do this. There is no way to assign manual IPs to a
student, and the software is not allowing anything past a local level only.

What do I do?

 

[Papa]

I wish I could help you. However, your best bet is to read the posts in this
forum and elsewhere. Perhaps you will find a solution in one of them. Google
can quickly narrow the search time for the other forums.

If that doesn't help, then you have two choices. In the short run, either go
back to Windows XP or forget wireless and have everyone use Ethernet cables.
In the long run, wait for Vista SP1 to come out, whenever that will be - in
the hope that a solution will become available.

Frankly, I am a little surprised that a university would switch to Vista
shortly after it was released. Not very prudent.

 

[Guest]

The University hasn't....the students buy their own laptops... and since the
new wave of computers only come loaded with vista, and for obvious reasons,
they are pissed that their recent investment won't work at the place that
they bought it to use.

 

[Papa]

The University hasn't....the students buy their own laptops... and since
the
new wave of computers only come loaded with vista, and for obvious
reasons,
they are pissed that their recent investment won't work at the place that
they bought it to use.

Very understandable. I would be too.

 

[Guest]

Hey Rob,
Have you had any luck with this? We deployed a 3com Managed Wireless last
summer in out campus and now students are bringing Vista Laptops and
requesting access to the network and internet as well. They can get
connected to the wireless, ping around the world, just can't access anything.
I called 3com to see if there was a solution and they just escalated to the
level 3 engineers. Just wondering if you have gone through this phase yet
and what the results were.
Thanks,
Jeremey

 

[Guest]

I tried for the first time to use the wireless feature to connect to a public
network. My prior XP laptop did not have a wireless card, so I was quite
looking forward to being able to take advantage of wireless connectivity.
Except Vista did not see the public network in the Connect To A Network
dialogue box, although if I kept drilling down through Menus and Properties
there it was, at full strength, but there was no-way to access it. How
frustrating is that! My client had his Mac, click, click and he was on -
felt like I was in one of those Mac commercials.

Yet ANOTHER frustration and disappointment with Vista - I've had many, and
nowI just accept the slow speed, the intermittent crashes, the failure to
show photos in thumbnails/icons, etc. etc.), as part of my punishment for
choosing to purchase a computer with Vista.

 

[Guest]

Hi paulp,
Not sure if this will help you or not, we fixed our issue by loading the XP
wireless Driver over the Vista Driver. This at least worked for our 3Com
wireless campus when using the intel 3945ABG card.
Hope that leads you down at least a possible good road.

Jeremey

 

[Guest]

Hi Jeremy,

Thanks for your sincere reply.

I may try that (if XP has a driver for this new 802.11n card) but I'm not
that sophisticated a user so I'm a bit nervous about it.

The point is that I have paid the price (in time, money, and aggravation) to
be a Microsoft beta tester. Microsoft promised faster, more stable, more
secure, easier connectivity, blah, blah, blah, and what I have experienced is
pretty much the exact opposite. Vista is not close to being market ready and
my next computer (which will unfortunately be 3 years from now) will
definitely be a Mac because I resent having been duped by Microsoft (and that
PC magazine I read which reviewed Vista and said how much better it was than
XP) and having to suffer for it.

As an aside, earlier in the day I was at a car dealership and my laptop saw
an unsecured wireless network and allowed me to connect, but the connection
was designated as a "local connection" only (as noted in some of the other
comments). My computer was plugged in at the time, so it wasn't the battery
thing some are saying will resolve this issue. After that experience I met
with a client at this restaraunt where half the patrons are using their
laptops to connect to the public wrireless network as per my initial comment.

Anyway, as I indicated at the outset, I do appreciate your sincere attempt
to assist. Thanks again.

 

[Guest]

Disable ipv6 on wireless and notebook adapterand you will be fine. If you
just do the wireless it still won't work. I am still looking for why it does
not work with IPv6. I'll post if I find the answer. But for now just uncheck
it and reboot.

 

[Guest]

Hi paulp,
Not sure if this will help you or not, we fixed our issue by loading the XP
wireless Driver over the Vista Driver. This at least worked for our 3Com
wireless campus when using the intel 3945ABG card.
Hope that leads you down at least a possible good road.

Jeremey

 

[Guest]

The issue is caused by a lack of a correct association on the SonicWALL
between the computer running Windows Vista and its assigned IP address.
Follow these steps to work around the issue by editing the System Registry:

Click the Start button.
Select All Programs > Accessories.
Right click (Command Prompt) then click (Run as administrator).
Type regedit.exe and press enter.
Go to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Right click this entry and click (New) then click (Dword).
Rename the new entry ArpRetryCount (leave it set to 0 by default).
Restart the computer.
Retry connecting to network. You should notice a successful connection.

 

[Robert L [MVP - Networking]]

Thank you for sharing your experience with us.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
The issue is caused by a lack of a correct association on the SonicWALL
between the computer running Windows Vista and its assigned IP address.
Follow these steps to work around the issue by editing the System Registry:

Click the Start button.
Select All Programs > Accessories.
Right click (Command Prompt) then click (Run as administrator).
Type regedit.exe and press enter.
Go to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Right click this entry and click (New) then click (Dword).
Rename the new entry ArpRetryCount (leave it set to 0 by default).
Restart the computer.
Retry connecting to network. You should notice a successful connection.