Wireless issue

[Steve Drake]

All,

I had an odd issue with my wireless network, the fix was to remove IPV6
protocols and the tunneling bits.

Not sure why, but it did fix my issue, if you are having a issues with
wireless this maybe the fix for you.

I tried 1 hours worth of random things before this. it was odd, ipconfig was
showing the wrong NIC, eg it was showing my Wired NIC has having an auto
config IP and my Wireless as being disconnected.


The symptoms were, sticking at acquiring ip address, even though the wep key
was correct, then it would default auto config.

Steve

 

[Zack Whittaker \(R2 Mentor\)]

It seems a lot of people have been struggling with this ( Check the DNS
settings, make sure they are right - make sure you have a static IP as this
can help. Also, try and make sure that you are using IPv4 for the time
being - it's safe still ;o)

--
Zack Whittaker
Microsoft Beta (Windows Server R2 Beta Mentor)
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: http://msblog.resdev.net
» ZackNET Forum: www.zacknet.co.uk/forum
» VistaBase: www.zacknet.co.uk/vistabase
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, mother or cat. Let's be clear on that one!


--- Original message follows ---

 

[Steve Drake]

I think it was an IPv6 issue, I remember back in the PDC build, this was
VERY VERY VERY (is that enough verys) buggy.

It was a Wireless connection in the hotel bar, so I could really go for a
static IP as I didn't know the subnet, the funny thing was, from the hotel
bar could see 3 other access points the had NO security setup when I fixed
my issues I could connect to them all.

rant...
On one of them, they had the default password set for there ZOOM ADSL
router, so if I was a bad boy I could have really messed things up, can you
imagine if MS did this, I can see the headlines now ...... sorry for the
rant

Steve