WG v6.01 build 995 Server BSOD on second SSL connection

[ChadRA]

I am using the latest build of wingate but have been having the same problem since the first released build of 6.01, it is when I am using the WGIC and connect to secure web sites (internet banking, etc.) from a "client" machine where the first connection will be fine but additional connections will cause the WG server to stop with a BSOD for IRQL_NOT_LESS_OR_EQUAL and points to module Afd.sys.

Since reading a while ago about the pain that realtek NIC cards can cause I had switched to 3COM, so my WG server configuration is:
Win2K Pro w/ SP4 and current with updates
3COM 3C509b-TCO card connected to high speed modem (5Mb download)
3COM 3CSOHO100B-TX card connected to LAN

I am able to connect to secure sites if I toggle the WGIC and just use NAT, so that is what I have been doing. It seems strange that NAT works but using the WGIC from a separate machine could cause a BSOD on the WG server, but I am also open to suggestions for configuration changes not directly related to Wingate, but the toggling of the client almost seem to suggest otherwise.

I am also still using my v5 license with this WG version if that could make any difference.

And BTW, I have been getting much more sleep since I started using v6 with the fixed VPN tunneling, thanks.

Regards,
Chad.

[genie]

When you said second connection, did you mean the connection made in the context of the same session in the browser?

[ChadRA]

It doesn't even need to be from the same WGIC, it has been from a completely separate machine.
Since this is a reproducable and serious problem I would have though that someone else would have reported this before, so that is why I am thinking that it may be something specific to my configuration but I don't have any more ideas on what to try.

[genie]

Aye, we haven't had any reports of such stranges - can you send your config to my email? Routing table, ipconfig output, installed drivers - things like that?

[ChadRA]

Will do, I'll gather that stuff up and send it to you tomorrow since it's getting late here.

Thanks,
Chad.

[ChadRA]

Since there were no other reports I did a bunch more testing and found that the problem was related to using Netscape 7.1. If Internet Explorer 6 was used the BSOD did not happen. I have since installed Netscape 7.2 and it doesn't seem to cause any problems. NS 7.1 must have been doing something really nasty to cause such problems with the WGIC.

Thanks,
Chad

[adrien]

OK, thanks for letting us know.

Normally it shouldn't be possible for a sockets application, or WinGate's Winsock Redirection Service to cause a bluescreen, but I guess if there is a problem in afd.sys that Netscape was able to find then you never know.

Adrien