Remote client blue screen on connection

[dparry]

Hi,

I have been trying to get a trial of WinGate VPN up and running, I have managed to get the WinGate VPN server (Windows 98 with Cable Modem) running, however, when even I attempt to connect the WinGate VPN Remote Client (Windows XP with USB ADSL Modem) upon connection, the client machine crashes with a blue screen of death.

Does anyone have any ideas ?

Thanks,

David

[adrien]

Which version is this?

Adrien

[dparry]

Adrein,

I believe the version I am using is 1.0.6, downloaded from Deerfield software.

[adrien]

OK, we're up to 1.0.10 now on www.wingate.com

Suggest you try that one.

You will need to move the server to the same version as well though. It's a free upgrade.

Adrien

[dparry]

Adrien,

I upgraded the remote clients to 1.0.10 and the server to 5.0.10.

After upgrade, I am still having the same problem with remote clients blue screening on connection when connected via USB Broadband connection.

I was able to connect these remote clients via a dialup internet connection, so I am pretty convinced that the problem is related to the USB broadband connection.

I don't have the specific details of the USB broadband modem with me, but I will get them later today.

Thanks,

David

[dparry]

Adrien,

The USB modem being used is..

Motorola Surfboard 4200 USB Cable Modem

and it blue screens with the following message...

DRIVER_IRQL_NOTLESS_OR_EQUAL

[Westie]

I too am getting this problem.
Any help would be great.

[adrien]

ok, thanks for that - we have seen some problems with USB devices...

Will check

Adrien

[Westie]

I think the problem maybe SP1 for winxp.
I tested the VPN on a laptop without SP1 installed and worked fine.
This maybe worth a shot for people having the same problem.

[karlb]

I also have a similar problem...

Our wireless access point is connected to the DMZ side of our firewall and we use the Wingate VPN client to access internal resources from wireless laptops around the office.

This works well with all our client machines accept for one which has a LinkSys USB 802.11b Wirlesss Network adapter, this reliably blue screens when the VPN connection is made...

Any ideas...

[dparry]

Adrien,

Is there any outlook for a new release to fix this problem ??

Even if it's a beta version ??


Thanks,

David

[adrien]

we fixed a couple of potential blue screen issues with the latest drivers in WinGate VPN 1.2 / WinGate 5.2 which is now available.

Let me know if you still see these problems.

Adrien

[dparry]

Adrien,

I upgraded the Wingate Server to 5.2 and the remote clients to Wingate VPN 1.2. However, the same problem still exists upon connection the remote clients blue screen.

Sorry,

David

[dparry]

Adrien,

My client is starting to get a bit frustrated, and is asking to look at other options for a VPN. Since they currently use Wingate for their proxy server/firewall, my preference is obviously to get the Wingate VPN working.

Any assistance that you could provide in getting this problem resolved as quick as possible would be greatly appreciated.

Thanks,

David

[genie]

Hi, David

Could you make sure that the network card drivers installed are the latest ones?
Also, it would be handy if you send us the crash dumps - we will be able to identify the location of the problem then.

Regards,

Gene

[jono659]

This is the same problem as mentioned in

http://forums.qbik.com/viewtopic.php?t=1497

once again I think to do with WAN ip, one of our offices used one and the way the usb modem is set up is to subnet the public ip, when connecting the server BSOD's with a STOP: 7f error debug says this

Probably caused by : Unknown_Image ( qbikhkXP!stricmp+24c60 )

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_d

TRAP_FRAME: f7c7656c -- (.trap f7c7656c)
ErrCode = 00000000
eax=000005ea ebx=867cb340 ecx=8676b958 edx=fffffffe esi=00000008 edi=f7c76c34
eip=f765ca01 esp=f7c765e0 ebp=f7c765fc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
qbikhkXP!stricmp+0x31631:
f765ca01 c70200000000 mov dword ptr [edx],0x0 ds:0023:fffffffe=????????
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from f76579ac to f765ca01

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7c765fc f76579ac f7c76c98 00000616 000001ff qbikhkXP!stricmp+0x31631
f7c76614 f764e0ba f7c76c98 00000616 851b4a58 qbikhkXP!stricmp+0x2c5dc
f7c76c70 f764df50 f7661cc0 85e48b74 857fd1e0 qbikhkXP!stricmp+0x22cea
f7c76ca8 f764dea0 f7661cc0 85c82a58 857fd1e0 qbikhkXP!stricmp+0x22b80
f7c76d34 f7649a62 f7661cc0 85e48b66 85e48b74 qbikhkXP!stricmp+0x22ad0
f7c76d68 f7657d8a 851b4a50 851b4a50 851b4a50 qbikhkXP!stricmp+0x1e692
f7c76d7c 80528545 851b4a50 00000000 867cb340 qbikhkXP!stricmp+0x2c9ba
f7c76dac 805b05c6 851b4a50 00000000 00000000 nt!ExpWorkerThread+0xed
f7c76ddc 80534de6 80528458 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
qbikhkXP!stricmp+31631
f765ca01 c70200000000 mov dword ptr [edx],0x0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: qbikhkXP!stricmp+31631

MODULE_NAME: qbikhkXP

IMAGE_NAME: qbikhkXP.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 40313899

STACK_COMMAND: .trap f7c7656c ; kb

BUCKET_ID: 0x7f_d_qbikhkXP!stricmp+31631

Followup: MachineOwner



Why would the software on a normal install though issue a public ip, not up enough on networking for that one anyone got clues?

[adrien]

Hi Jono

Justr tracked this down. We fixed this bug on 25 Feb this year... unfortunately 1 day after we released 5.2.3, so this fix will be in the next release or we can send you a driver to try if you like.

This also implies however that your system ran out of buffers, since this is related to a buffer allocation failure. We are looking into possible causes for this.

Adrien

[jono659]

Hi Jono

Justr tracked this down. We fixed this bug on 25 Feb this year... unfortunately 1 day after we released 5.2.3, so this fix will be in the next release or we can send you a driver to try if you like.

This also implies however that your system ran out of buffers, since this is related to a buffer allocation failure. We are looking into possible causes for this.

Adrien

Hi there,

Thanks for the repy, will allocate larger buffers today, could you also give me a clue as to why:

a: a normal setup (eg cable or dsl) would broadcast its WAN ip in this way

b: why this specifically would cause the buffer/driver problem

Also would LOVE the new driver ;)

Many thanks

JonO

[jono659]

Any more news on this one ?

JonO

[jono659]

Spose it's back to paid support again.

[MattP]

I've sent you the latest driver. We have been moving offices so things have been a little hectic here.

[jono659]

Many thanks

JonO