Help Does Froyo fix the DHCP Netmask WiFi problem?

[Mechromancer]

Does Froyo Fix the DHCP Netmask issue on the Galaxy S? Does it actually take the DHCP info from DNS and populate netmask as 255.255.255.0 instead of 255.0.0.0 on some networks? THIS IS ALL I WANT OUT OF FROYO! I want to finally be able to connect to my workplace's damn Wi-Fi. I take a lot of crap from my Motorola Droid and iPhone coworkers because of this enormous issue with the Galaxy S.

More info on this here:
http://androidforums.com/captivate-support-troubleshooting/142397-odd-netmask-issues-wifi.html

And here:
Samsung Captivate WiFi DHCP netmask issue - AT&T Community

 

[blonkster]

Does Froyo Fix the DHCP Netmask issue on the Galaxy S? Does it actually take the DHCP info from DNS and populate netmask as 255.255.255.0 instead of 255.0.0.0 on some networks? THIS IS ALL I WANT OUT OF FROYO! I want to finally be able to connect to my workplace's damn Wi-Fi. I take a lot of crap from my Motorola Droid and iPhone coworkers because of this enormous issue with the Galaxy S.

More info on this here:
http://androidforums.com/captivate-support-troubleshooting/142397-odd-netmask-issues-wifi.html

And here:
Samsung Captivate WiFi DHCP netmask issue - AT&T Community

Yes, its fine for me - but don't know if it was wrong before.

 

[Mechromancer]

Yes, its fine for me - but don't know if it was wrong before.

Tell me about your usage scenario. Were you connecting it to a home wifi network with a standard 192.168.X.X or 10.0.X.X network, or a workplace Domain network with multiple segments and a non-standard IP? People have also had trouble with complex home networks as described in the AT&T forum link I have posted above.

If Froyo fixes this problem, I will be the happiest Captivate user on Earth.

 

[blonkster]

Tell me about your usage scenario. Were you connecting it to a home wifi network with a standard 192.168.X.X or 10.0.X.X network, or a workplace Domain network with multiple segments and a non-standard IP? People have also had trouble with complex home networks as described in the AT&T forum link I have posted above.

If Froyo fixes this problem, I will be the happiest Captivate user on Earth.

Sorry, I'm on a simple home LAN, 192.168.x.x. so I probably would not have had your problem.

I can only connect to the public WLAN at work, but will try that if I can next week.