General Questions

I've been using version 1.22 with a DLink AP for a wireless hotspot for a little over a year, without any issues. No authentication, a few rules, and dhcp.  Vista OS clients are begining to show up and are trying to connect, but can't. Is anyone else experiencing this issue or advice on resolving this?

Thanks!

Using it with captive portal you mean?  I haven't seen any issues with Vista, but haven't used it w/CP.

At first I was using the Captive Portal. When it was discovered Vista clients were having issues I disabled that feature.
I am using the DHCP feature. But it seems the Vista clients aren't accepting the IP. This is where I get involved  by checking their network settings. I've had the Vista clients disable their IPv6 and reboot. While reviewing the logs they still won't accept an IP. I have to assign them an IP (v4) and they get access to the Internet.

Thanks!

At first I was using the Captive Portal. When it was discovered Vista clients were having issues I disabled that feature.
I am using the DHCP feature. But it seems the Vista clients aren't accepting the IP. This is where I get involved  by checking their network settings. I've had the Vista clients disable their IPv6 and reboot. While reviewing the logs they still won't accept an IP. I have to assign them an IP (v4) and they get access to the Internet.

Thanks!

     I am plagued with this problem, I will try to give them a static IP and they still are unable to connect to the internet, I have tried the IPv6 trick with no hope.
Here is the Microsoft article explaining how to fix this on the PC end but I am not about to go through the registry with anyone.

http://support.microsoft.com/kb/928233

     Here is a copy and past of a DHCP Log on one of the many M0n0wall servers I have out in the field.

Aug 22 15:36:59   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:00   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:02   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:02   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:10   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:10   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:26   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:26   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:53   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:37:53   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:38:04   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:38:04   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:38:18   dhcpd: DHCPDISCOVER from 00:21:00:ab:7a:c9 (Soundwerx) via vr0
Aug 22 15:38:18   dhcpd: DHCPOFFER on 172.20.1.250 to 00:21:00:ab:7a:c9 (Soundwerx) via vr0

     I saw a glimpse of a fix in the mailing list but no instruction on what or how to do it. I know other routers had the same problem but with a firmware upgrade the problem is gone. I am wondering if Monowall will ever fix this.

I have been seeing this a few places as well.  The funny part of the Microsoft article is that they make it sound like we don't see them.  If you look in the logs, you will see the DHCP request with the system name, and out DHCP offer...  But they never see it.

I have not seen it one machines with the latest service pack, however, so that may be a fix.  How they get it with no net, is another issue.

I discover the same issue but anyway, the Vista machine got a correct address via DHCP.
Ping Gateway is ok. DNS is ok too.
My suspicion is, Vista makes a test like ping Microsoft.com , then stores the status as "no connection to the Internet" (because of CP) .
Vista not use the gateway now when i start Firefox or IE.
Disconnect the WLAN connection , switch of the CP and connect again to WLAN helps.
After this procedure i can switch on the CP.
Vista does not have the problem re

Windows 7 has the same issue .
anyone?

I had a problem with one customer using Vista and he is connected behind his access point (ubiquiti nanostation2).  He was not able to see the captive portal homepage... well it was working one time out of 10-15 refresh.

I added this morning these address in the allowed networks:
131.107.255.255/32  dns.msftncsi.com   
64.4.18.90/32  www.msftncsi.com   

This let the Network Connectivity Status in Vista and 7 to display the "Earth", and I'm guessing that it's making the redirection working normally.  So far, it's working with Vista and 7.
[ http://technet.microsoft.com/en-us/library/cc766017(WS.10).aspx ]

Thanks to frank for posting his experience.

I discover the same issue but anyway, the Vista machine got a correct address via DHCP.
Ping Gateway is ok. DNS is ok too.
My suspicion is, Vista makes a test like ping Microsoft.com , then stores the status as "no connection to the Internet" (because of CP) .
Vista not use the gateway now when i start Firefox or IE.
Disconnect the WLAN connection , switch of the CP and connect again to WLAN helps.
After this procedure i can switch on the CP.
Vista does not have the problem re

Windows 7 has the same issue .
anyone?