Curious. Have u tried to disable the IPv6 stack in Vista ?
We are using monowall on wired networks with Vista, once the IPv6 stack is disabled, have not seen any issues with DHCP. Regards Faisal Imtiaz -----Original Message----- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Joe Miller Sent: Sunday, May 17, 2009 11:17 PM To: WISPA General List Subject: Re: [WISPA] Monowall and Microsoft Vista machines Yes I do, they are RV Parks. They are great money makers, but this Vista issue is getting out of hand. ----- Original Message ---- From: RickG <rgunder...@gmail.com> To: WISPA General List <wireless@wispa.org> Sent: Sunday, May 17, 2009 9:27:44 PM Subject: Re: [WISPA] Monowall and Microsoft Vista machines Joe, I've seen Vista have issues connecting with all kinds of access points. I usually have the customer get a different router and it works. Which takes me to a question: Why do you have customers connecting laptops directly to you? Do you run a hotspot? -RickG On Sun, May 17, 2009 at 10:09 PM, Joe Miller <joe.mil...@dslbyair.com> wrote: > > > I'm having a hell of a time with Vista machines connecting to my Monowall router. I found this regarding Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers, and gives the fix for the computer. HOW MANY PEOPLE are knowledgable enough with Vista to fix there own machine? >support.microsoft.com/default.as...33/en-us and Monowall's latest version: > > >m0n0.ch/wall/ "04/11/2009 - m0n0wall 1.3b16 released This beta > release improves IPv6 support (by providing more control over RAs, adding DHCPv6, allowing IPv6 DNS servers, enabling IPv6 webGUI access, etc.), adds initial basic support for secondary IP addresses, patches a kernel security issue and adds support for Broadcom BCM5722 NICs." > > Has anyone dealt with this before? Does anyone know how to make Vista work on their Monowall routers without having to assign a static address on the Vista machine? This is starting to become a pain in the a$$. The customer will complain that they cannot connect to the captive portal and will say it worked in the last place they were at. It kind of makes me wonder why Microsoft pulled such a rotten joke on end-users. > > > > > > ---------------------------------------------------------------------- > ---------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > ---------------------------------------------------------------------- > ---------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > ---------------------------------------------------------------------------- ---- WISPA Wants You! Join today! http://signup.wispa.org/ ---------------------------------------------------------------------------- ---- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ ---------------------------------------------------------------------------- ---- WISPA Wants You! Join today! http://signup.wispa.org/ ---------------------------------------------------------------------------- ---- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
