Vista - Connecting to L2TP VPN on 64bit is crashing...

02-10-2009

I have 2 machined that are Vista 64bit (all the latest updates) that are
connecting to a L2TP VPN Connection.

When connected to the VPN and doing data transfers, the machine will
sometimes crash with the bugcheck info below...
We have several other machines that conenct the same way and they do not
have the issue.

Any Suggestions?

Thanks,
Scott<-

*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffffa60025878d0

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

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80001e71eae to fffff80001e72110

STACK_TEXT:
fffff800`0304ed28 fffff800`01e71eae : 00000000`0000007f 00000000`00000008
00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`0304ed30 fffff800`01e706f8 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffff800`0304ee70 fffffa60`025878d0 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
fffffa60`01fa2fe0 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : ndiswan!ProtoCoSendComplete+0x50

STACK_COMMAND: kb

FOLLOWUP_IP:
ndiswan!ProtoCoSendComplete+50
fffffa60`025878d0 ff15c2d90100 call qword ptr
[ndiswan!_imp_NdisAcquireReadWriteLock (fffffa60`025a5298)]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ndiswan!ProtoCoSendComplete+50

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndiswan

IMAGE_NAME: ndiswan.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919aad

FAILURE_BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50

BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50

Followup: MachineOwner

*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffffa60025878d0

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

Page 77189 not present in the dump file. Type ".hh dbgerr004" for details

PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for
details

PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for
details

BUGCHECK_STR: 0x7f_8

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80001e71eae to fffff80001e72110

STACK_TEXT:
fffff800`0304ed28 fffff800`01e71eae : 00000000`0000007f 00000000`00000008
00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`0304ed30 fffff800`01e706f8 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffff800`0304ee70 fffffa60`025878d0 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
fffffa60`01fa2fe0 fffffa60`00e11557 : fffffa80`08a19a00 00000000`00001630
fffffa80`066a9ba0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0x50
fffffa60`01fa3040 fffffa60`0255745c : fffffa80`078d8440 fffffa80`066a9ba0
fffffa80`0499bb98 00000000`00000000 :
ndis!ndisMCoSendCompleteToNdisPacket+0x127
fffffa60`01fa3090 fffffa60`02557009 : 00000000`00000003 fffffa80`04bd22a0
fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec
fffffa60`01fa30e0 fffffa60`0255708b : fffffa80`06125950 00000000`00000000
00000000`00000000 fffffa80`062aa9c0 : rasl2tp!L2tpSendComplete+0x89
fffffa60`01fa3110 fffff800`01e74485 : fffffa80`062aa9c0 00000000`00000000
00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b
fffffa60`01fa3150 fffffa60`04806f78 : 00000000`00000000 fffffa80`062aa902
fffffa80`06304800 00000000`00000000 : nt!IopfCompleteRequest+0x315
fffffa60`01fa3210 fffffa60`0481376c : fffffa80`063048a0 00000000`00000000
fffffa80`06304800 00000000`614b5357 : afd!WskProTLSendToComplete+0x48
fffffa60`01fa3240 fffff800`01e74485 : fffffa80`063048a0 fffff800`01f52e96
00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c
fffffa60`01fa3270 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000102
fffffa80`063048a0 00000000`42786454 : nt!IopfCompleteRequest+0x315
fffffa60`01fa3330 fffffa60`01064860 : 00000000`00000000 fffffa80`04e981e0
00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8
fffffa60`01fa3370 fffffa60`00cdca48 : fffffa80`04e98030 00000000`00000000
00000000`00000000 00000000`00000000 :
tcpip!UdpSendMessagesDatagramsComplete+0xf0
fffffa60`01fa33d0 fffffa60`048e25fa : 00000000`00000000 fffffa80`066d0310
00000000`00000000 00000000`00000000 :
NETIO!NetioDereferenceNetBufferList+0x78
fffffa60`01fa3400 fffffa60`00fab0b2 : fffffa80`066d0310 fffffa80`07a34a10
fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a
fffffa60`01fa3430 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000
fffffa80`079e4580 fffffa60`00e1ba29 :
ndis!ndisMSendCompleteNetBufferListsInternal+0xa2
fffffa60`01fa34a0 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000
00000000`00000000 00000000`00000000 :
pacer!PcFilterSendNetBufferListsComplete+0xf4
fffffa60`01fa3510 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000
fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195
fffffa60`01fa3560 fffffa60`0258795b : 00000000`00000000 fffffa80`08c5ab70
fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df
fffffa60`01fa35c0 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff
fffffa80`066a9ec0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb
fffffa60`01fa3620 fffffa60`0255745c : fffffa80`078d8440 fffffa80`066a9ec0
fffffa80`0499bb48 00000000`00000000 :
ndis!ndisMCoSendCompleteToNdisPacket+0x127
fffffa60`01fa3670 fffffa60`02557009 : 00000000`00000003 fffffa80`068f5cd0
fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec
fffffa60`01fa36c0 fffffa60`0255708b : fffffa80`066c1750 00000000`00000000
00000000`00000000 fffffa80`067a9560 : rasl2tp!L2tpSendComplete+0x89
fffffa60`01fa36f0 fffff800`01e74485 : fffffa80`067a9560 00000000`00000000
00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b
fffffa60`01fa3730 fffffa60`04806f78 : 00000000`00000000 fffffa80`067a9502
fffffa80`0675cb00 00000000`00000000 : nt!IopfCompleteRequest+0x315
fffffa60`01fa37f0 fffffa60`0481376c : fffffa80`0675cb80 00000000`00000000
fffffa80`0675cb00 00000000`614b5357 : afd!WskProTLSendToComplete+0x48
fffffa60`01fa3820 fffff800`01e74485 : fffffa80`0675cb80 fffff800`01f52e96
00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c
fffffa60`01fa3850 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000102
fffffa80`0675cb80 00000000`42786454 : nt!IopfCompleteRequest+0x315
fffffa60`01fa3910 fffffa60`01064860 : 00000000`00000000 fffffa80`0499d1e0
00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8
fffffa60`01fa3950 fffffa60`00cdca48 : fffffa80`0499d030 00000000`00000000
00000000`00000000 00000000`00000000 :
tcpip!UdpSendMessagesDatagramsComplete+0xf0
fffffa60`01fa39b0 fffffa60`048e25fa : 00000000`00000000 fffffa80`0720ae20
00000000`00000000 00000000`00000000 :
NETIO!NetioDereferenceNetBufferList+0x78
fffffa60`01fa39e0 fffffa60`00fab0b2 : fffffa80`0720ae20 fffffa80`07a34a10
fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a
fffffa60`01fa3a10 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000
fffffa80`079e4580 fffffa60`00e1ba29 :
ndis!ndisMSendCompleteNetBufferListsInternal+0xa2
fffffa60`01fa3a80 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000
00000000`00000000 00000000`00000000 :
pacer!PcFilterSendNetBufferListsComplete+0xf4
fffffa60`01fa3af0 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000
fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195
fffffa60`01fa3b40 fffffa60`0258795b : 00000000`00000000 fffffa80`06508010
fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df
fffffa60`01fa3ba0 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff
fffffa80`04a490b0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb
fffffa60`01fa3c00 fffffa60`0255745c : fffffa80`078d8440 fffffa80`04a490b0
fffffa80`0499baf8 00000000`00000000 :
ndis!ndisMCoSendCompleteToNdisPacket+0x127
fffffa60`01fa3c50 fffffa60`02557009 : 00000000`00000003 fffffa80`0677dcc0
fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec
fffffa60`01fa3ca0 fffffa60`0255708b : fffffa80`0677cb60 00000000`00000000
00000000`00000000 fffffa80`08ccb010 : rasl2tp!L2tpSendComplete+0x89
fffffa60`01fa3cd0 fffff800`01e74485 : fffffa80`08ccb010 00000000`00000000
00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b
fffffa60`01fa3d10 fffffa60`04806f78 : 00000000`00000000 fffffa80`08ccb002
fffffa80`061b2b00 00000000`00000000 : nt!IopfCompleteRequest+0x315
fffffa60`01fa3dd0 fffffa60`0481376c : fffffa80`061b2b80 00000000`00000000
fffffa80`061b2b00 00000000`614b5357 : afd!WskProTLSendToComplete+0x48
fffffa60`01fa3e00 fffff800`01e74485 : fffffa80`061b2b80 fffff800`01f52e96
00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c
fffffa60`01fa3e30 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000202
fffffa80`061b2b80 00000000`42786454 : nt!IopfCompleteRequest+0x315
fffffa60`01fa3ef0 fffffa60`01064860 : 00000000`00000000 fffffa80`054c7b60
00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8
fffffa60`01fa3f30 fffffa60`00cdca48 : fffffa80`054c79b0 00000000`00000000
00000000`00000000 00000000`00000000 :
tcpip!UdpSendMessagesDatagramsComplete+0xf0
fffffa60`01fa3f90 fffffa60`048e25fa : 00000000`00000000 fffffa80`0660e030
00000000`00000000 00000000`00000000 :
NETIO!NetioDereferenceNetBufferList+0x78
fffffa60`01fa3fc0 fffffa60`00fab0b2 : fffffa80`0660e030 fffffa80`07a34a10
fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a
fffffa60`01fa3ff0 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000
fffffa80`079e4580 fffffa60`00e1ba29 :
ndis!ndisMSendCompleteNetBufferListsInternal+0xa2
fffffa60`01fa4060 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000
00000000`00000000 00000000`00000000 :
pacer!PcFilterSendNetBufferListsComplete+0xf4
fffffa60`01fa40d0 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000
fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195
fffffa60`01fa4120 fffffa60`0258795b : 00000000`00000000 fffffa80`04f02010
fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df
fffffa60`01fa4180 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff
fffffa80`04a49240 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb
fffffa60`01fa41e0 fffffa60`0255745c : fffffa80`078d8440 fffffa80`04a49240
fffffa80`0499baa8 00000000`00000000 :
ndis!ndisMCoSendCompleteToNdisPacket+0x127
fffffa60`01fa4230 fffffa60`02557009 : 00000000`00000003 fffffa80`047d6df0
fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec
fffffa60`01fa4280 fffffa60`0255708b : fffffa80`04a4c160 00000000`00000000
00000000`00000000 fffffa80`0610a5d0 : rasl2tp!L2tpSendComplete+0x89
fffffa60`01fa42b0 fffff800`01e74485 : fffffa80`0610a5d0 00000000`00000000
00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b
fffffa60`01fa42f0 fffffa60`04806f78 : 00000000`00000000 fffffa80`0610a502
fffffa80`066e0200 00000000`00000000 : nt!IopfCompleteRequest+0x315
fffffa60`01fa43b0 fffffa60`0481376c : fffffa80`066e0260 00000000`00000000
fffffa80`066e0200 00000000`614b5357 : afd!WskProTLSendToComplete+0x48
fffffa60`01fa43e0 fffff800`01e74485 : fffffa80`066e0260 fffff800`01f52e96
00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c
fffffa60`01fa4410 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000202
fffffa80`066e0260 00000000`42786454 : nt!IopfCompleteRequest+0x315
fffffa60`01fa44d0 fffffa60`01064860 : 00000000`00000000 fffffa80`090b61e0
00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8
fffffa60`01fa4510 fffffa60`00cdca48 : fffffa80`090b6030 00000000`00000000
00000000`00000000 00000000`00000000 :
tcpip!UdpSendMessagesDatagramsComplete+0xf0
fffffa60`01fa4570 fffffa60`048e25fa : 00000000`00000000 fffffa80`0679d320
00000000`00000000 00000000`00000000 :
NETIO!NetioDereferenceNetBufferList+0x78
fffffa60`01fa45a0 fffffa60`00fab0b2 : fffffa80`0679d320 fffffa80`07a34a10
fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a
fffffa60`01fa45d0 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000
fffffa80`079e4580 fffffa60`00e1bae7 :
ndis!ndisMSendCompleteNetBufferListsInternal+0xa2
fffffa60`01fa4640 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000
00000000`00000000 00000000`00000000 :
pacer!PcFilterSendNetBufferListsComplete+0xf4
fffffa60`01fa46b0 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000
fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195
fffffa60`01fa4700 fffffa60`0258795b : 00000000`00000000 fffffa80`067fbb70
fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df
fffffa60`01fa4760 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff
fffffa80`04a493d0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb
fffffa60`01fa47c0 fffffa60`0255745c : fffffa80`078d8440 fffffa80`04a493d0
fffffa80`0499ba58 00000000`00000000 :
ndis!ndisMCoSendCompleteToNdisPacket+0x127
fffffa60`01fa4810 fffffa60`02557009 : 00000000`00000003 fffffa80`071eab80
fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec
fffffa60`01fa4860 fffffa60`0255708b : fffffa80`071ef8d0 00000000`00000000
00000000`00000000 fffffa80`06522a00 : rasl2tp!L2tpSendComplete+0x89

STACK_COMMAND: kb

FOLLOWUP_IP:
ndiswan!ProtoCoSendComplete+50
fffffa60`025878d0 ff15c2d90100 call qword ptr
[ndiswan!_imp_NdisAcquireReadWriteLock (fffffa60`025a5298)]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ndiswan!ProtoCoSendComplete+50

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndiswan

IMAGE_NAME: ndiswan.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919aad

FAILURE_BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50

BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50

Followup: MachineOwner
---------

---------

02-11-2009

Hi Scott,

Thank you for posting in newsgroup.

To locate the exact problem of the stop error, we need to analyze the crash
dump file. Unfortunately, we cannot help you analyze the dump file in
newsgroup. To trouble shoot this problem efficiently, I suggest that you
speak directly with a Microsoft Support Professional so that the crash dump
can be analyzed. Here are some articles that will help prepare you for this
call:

For a complete list of Microsoft Product Support Services phone numbers and
information about support costs, please go to the following address on the
World Wide Web:
http://support.microsoft.com/directory/overview.asp

Thank you for your understanding and cooperation.

Sincerely,
Joson Zhou
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

02-11-2009

Thanks, though now that I've been transferred to 3 different people I don't
think they now what I'm asking them...

Any way to get to someone who knows what L2TP is?

Scott<-
""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message
news:c04i2hCjJHA.5012@xxxxxx

Quote:

> Hi Scott,
>
> Thank you for posting in newsgroup.
>
> To locate the exact problem of the stop error, we need to analyze the
> crash
> dump file. Unfortunately, we cannot help you analyze the dump file in
> newsgroup. To trouble shoot this problem efficiently, I suggest that you
> speak directly with a Microsoft Support Professional so that the crash
> dump
> can be analyzed. Here are some articles that will help prepare you for
> this
> call:
>
> For a complete list of Microsoft Product Support Services phone numbers
> and
> information about support costs, please go to the following address on the
> World Wide Web:
> http://support.microsoft.com/directory/overview.asp
>
> Thank you for your understanding and cooperation.
>
> Sincerely,
> Joson Zhou
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

02-11-2009

Transferred Again...
"Scott Townsend" <scooter133@xxxxxx> wrote in message
news:O34bAPJjJHA.5124@xxxxxx

Quote:

> Thanks, though now that I've been transferred to 3 different people I
> don't think they now what I'm asking them...
>
> Any way to get to someone who knows what L2TP is?
>
> Scott<-
> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message
> news:c04i2hCjJHA.5012@xxxxxx

Quote:

>> Hi Scott,
>>
>> Thank you for posting in newsgroup.
>>
>> To locate the exact problem of the stop error, we need to analyze the
>> crash
>> dump file. Unfortunately, we cannot help you analyze the dump file in
>> newsgroup. To trouble shoot this problem efficiently, I suggest that you
>> speak directly with a Microsoft Support Professional so that the crash
>> dump
>> can be analyzed. Here are some articles that will help prepare you for
>> this
>> call:
>>
>> For a complete list of Microsoft Product Support Services phone numbers
>> and
>> information about support costs, please go to the following address on
>> the
>> World Wide Web:
>> http://support.microsoft.com/directory/overview.asp
>>
>> Thank you for your understanding and cooperation.
>>
>> Sincerely,
>> Joson Zhou
>> Microsoft Online Support
>> Microsoft Global Technical Support Center
>>
>> Get Secure! - www.microsoft.com/security
>> =====================================================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>

>

02-11-2009

Transferred again... I think I'm up to 6 people..

When I offered the Crash Debug info they said they didn't need it... They
didn't really care about the Stop Code...

"Scott Townsend" <scooter133@xxxxxx> wrote in message
news:O6T6qQJjJHA.3656@xxxxxx

Quote:

> Transferred Again...
> "Scott Townsend" <scooter133@xxxxxx> wrote in message
> news:O34bAPJjJHA.5124@xxxxxx

Quote:

>> Thanks, though now that I've been transferred to 3 different people I
>> don't think they now what I'm asking them...
>>
>> Any way to get to someone who knows what L2TP is?
>>
>> Scott<-
>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message
>> news:c04i2hCjJHA.5012@xxxxxx

Quote:

>>> Hi Scott,
>>>
>>> Thank you for posting in newsgroup.
>>>
>>> To locate the exact problem of the stop error, we need to analyze the
>>> crash
>>> dump file. Unfortunately, we cannot help you analyze the dump file in
>>> newsgroup. To trouble shoot this problem efficiently, I suggest that you
>>> speak directly with a Microsoft Support Professional so that the crash
>>> dump
>>> can be analyzed. Here are some articles that will help prepare you for
>>> this
>>> call:
>>>
>>> For a complete list of Microsoft Product Support Services phone numbers
>>> and
>>> information about support costs, please go to the following address on
>>> the
>>> World Wide Web:
>>> http://support.microsoft.com/directory/overview.asp
>>>
>>> Thank you for your understanding and cooperation.
>>>
>>> Sincerely,
>>> Joson Zhou
>>> Microsoft Online Support
>>> Microsoft Global Technical Support Center
>>>
>>> Get Secure! - www.microsoft.com/security
>>> =====================================================
>>> When responding to posts, please "Reply to Group" via your newsreader so
>>> that others may learn and benefit from your issue.
>>> =====================================================
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>

>>

>

02-11-2009

7th Transfer... Going on over 30 minutes with not talking to anyone who
knows what L2TP is...

"Scott Townsend" <scooter133@xxxxxx> wrote in message
news:%23xMJgZJjJHA.4644@xxxxxx

Quote:

> Transferred again... I think I'm up to 6 people..
>
> When I offered the Crash Debug info they said they didn't need it... They
> didn't really care about the Stop Code...
>
> "Scott Townsend" <scooter133@xxxxxx> wrote in message
> news:O6T6qQJjJHA.3656@xxxxxx

Quote:

>> Transferred Again...
>> "Scott Townsend" <scooter133@xxxxxx> wrote in message
>> news:O34bAPJjJHA.5124@xxxxxx

Quote:

>>> Thanks, though now that I've been transferred to 3 different people I
>>> don't think they now what I'm asking them...
>>>
>>> Any way to get to someone who knows what L2TP is?
>>>
>>> Scott<-
>>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message
>>> news:c04i2hCjJHA.5012@xxxxxx
>>>> Hi Scott,
>>>>
>>>> Thank you for posting in newsgroup.
>>>>
>>>> To locate the exact problem of the stop error, we need to analyze the
>>>> crash
>>>> dump file. Unfortunately, we cannot help you analyze the dump file in
>>>> newsgroup. To trouble shoot this problem efficiently, I suggest that
>>>> you
>>>> speak directly with a Microsoft Support Professional so that the crash
>>>> dump
>>>> can be analyzed. Here are some articles that will help prepare you for
>>>> this
>>>> call:
>>>>
>>>> For a complete list of Microsoft Product Support Services phone numbers
>>>> and
>>>> information about support costs, please go to the following address on
>>>> the
>>>> World Wide Web:
>>>> http://support.microsoft.com/directory/overview.asp
>>>>
>>>> Thank you for your understanding and cooperation.
>>>>
>>>> Sincerely,
>>>> Joson Zhou
>>>> Microsoft Online Support
>>>> Microsoft Global Technical Support Center
>>>>
>>>> Get Secure! - www.microsoft.com/security
>>>> =====================================================
>>>> When responding to posts, please "Reply to Group" via your newsreader
>>>> so
>>>> that others may learn and benefit from your issue.
>>>> =====================================================
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>

>>

>

02-11-2009

#8!! Apparently the Vista Networking Team does not do VPN...

"Scott Townsend" <scooter133@xxxxxx> wrote in message
news:Oj0L$eJjJHA.4976@xxxxxx

Quote:

> 7th Transfer... Going on over 30 minutes with not talking to anyone who
> knows what L2TP is...
>
>
> "Scott Townsend" <scooter133@xxxxxx> wrote in message
> news:%23xMJgZJjJHA.4644@xxxxxx

Quote:

>> Transferred again... I think I'm up to 6 people..
>>
>> When I offered the Crash Debug info they said they didn't need it... They
>> didn't really care about the Stop Code...
>>
>> "Scott Townsend" <scooter133@xxxxxx> wrote in message
>> news:O6T6qQJjJHA.3656@xxxxxx

Quote:

>>> Transferred Again...
>>> "Scott Townsend" <scooter133@xxxxxx> wrote in message
>>> news:O34bAPJjJHA.5124@xxxxxx
>>>> Thanks, though now that I've been transferred to 3 different people I
>>>> don't think they now what I'm asking them...
>>>>
>>>> Any way to get to someone who knows what L2TP is?
>>>>
>>>> Scott<-
>>>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message
>>>> news:c04i2hCjJHA.5012@xxxxxx
>>>>> Hi Scott,
>>>>>
>>>>> Thank you for posting in newsgroup.
>>>>>
>>>>> To locate the exact problem of the stop error, we need to analyze the
>>>>> crash
>>>>> dump file. Unfortunately, we cannot help you analyze the dump file in
>>>>> newsgroup. To trouble shoot this problem efficiently, I suggest that
>>>>> you
>>>>> speak directly with a Microsoft Support Professional so that the crash
>>>>> dump
>>>>> can be analyzed. Here are some articles that will help prepare you for
>>>>> this
>>>>> call:
>>>>>
>>>>> For a complete list of Microsoft Product Support Services phone
>>>>> numbers and
>>>>> information about support costs, please go to the following address on
>>>>> the
>>>>> World Wide Web:
>>>>> http://support.microsoft.com/directory/overview.asp
>>>>>
>>>>> Thank you for your understanding and cooperation.
>>>>>
>>>>> Sincerely,
>>>>> Joson Zhou
>>>>> Microsoft Online Support
>>>>> Microsoft Global Technical Support Center
>>>>>
>>>>> Get Secure! - www.microsoft.com/security
>>>>> =====================================================
>>>>> When responding to posts, please "Reply to Group" via your newsreader
>>>>> so
>>>>> that others may learn and benefit from your issue.
>>>>> =====================================================
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>>
>>>>
>>>

>>

>

02-11-2009

OMG!!!
" Cisco? What Microsoft product is installed on that?"

"VPN, that is a Virtual Desktop right?"

"Scott Townsend" <scooter133@xxxxxx> wrote in message
news:OX2QflJjJHA.3716@xxxxxx

Quote:

> #8!! Apparently the Vista Networking Team does not do VPN...
>
> "Scott Townsend" <scooter133@xxxxxx> wrote in message
> news:Oj0L$eJjJHA.4976@xxxxxx

Quote:

>> 7th Transfer... Going on over 30 minutes with not talking to anyone who
>> knows what L2TP is...
>>
>>
>> "Scott Townsend" <scooter133@xxxxxx> wrote in message
>> news:%23xMJgZJjJHA.4644@xxxxxx

Quote:

>>> Transferred again... I think I'm up to 6 people..
>>>
>>> When I offered the Crash Debug info they said they didn't need it...
>>> They didn't really care about the Stop Code...
>>>
>>> "Scott Townsend" <scooter133@xxxxxx> wrote in message
>>> news:O6T6qQJjJHA.3656@xxxxxx
>>>> Transferred Again...
>>>> "Scott Townsend" <scooter133@xxxxxx> wrote in message
>>>> news:O34bAPJjJHA.5124@xxxxxx
>>>>> Thanks, though now that I've been transferred to 3 different people I
>>>>> don't think they now what I'm asking them...
>>>>>
>>>>> Any way to get to someone who knows what L2TP is?
>>>>>
>>>>> Scott<-
>>>>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message
>>>>> news:c04i2hCjJHA.5012@xxxxxx
>>>>>> Hi Scott,
>>>>>>
>>>>>> Thank you for posting in newsgroup.
>>>>>>
>>>>>> To locate the exact problem of the stop error, we need to analyze the
>>>>>> crash
>>>>>> dump file. Unfortunately, we cannot help you analyze the dump file in
>>>>>> newsgroup. To trouble shoot this problem efficiently, I suggest that
>>>>>> you
>>>>>> speak directly with a Microsoft Support Professional so that the
>>>>>> crash dump
>>>>>> can be analyzed. Here are some articles that will help prepare you
>>>>>> for this
>>>>>> call:
>>>>>>
>>>>>> For a complete list of Microsoft Product Support Services phone
>>>>>> numbers and
>>>>>> information about support costs, please go to the following address
>>>>>> on the
>>>>>> World Wide Web:
>>>>>> http://support.microsoft.com/directory/overview.asp
>>>>>>
>>>>>> Thank you for your understanding and cooperation.
>>>>>>
>>>>>> Sincerely,
>>>>>> Joson Zhou
>>>>>> Microsoft Online Support
>>>>>> Microsoft Global Technical Support Center
>>>>>>
>>>>>> Get Secure! - www.microsoft.com/security
>>>>>> =====================================================
>>>>>> When responding to posts, please "Reply to Group" via your newsreader
>>>>>> so
>>>>>> that others may learn and benefit from your issue.
>>>>>> =====================================================
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>>
>>>>>
>>>>
>>>

>>

>

02-12-2009

Scott - you're not using the Cisco VPN client at all? I see no sign of it in
your stack trace, so I'm assuming this is a pure MS L2TP session. In which case
it looks like a bug - no doubt something in the packets from the Cisco VPN
termination device it doesn't like (you did mention Cisco)

All you can do is hang on until you get to someone that is interested in the
blue screen dump as that's what they'll need to resolve it, and maybe a
netmon/wireshark/sniffer trace as well.

Not something that anyone without Windows source code access is going to be able
to debug, so you need what MS PSS term an "escalation engineer"

Quote:

> I have 2 machined that are Vista 64bit (all the latest updates) that are
> connecting to a L2TP VPN Connection.
>
> When connected to the VPN and doing data transfers, the machine will
> sometimes crash with the bugcheck info below...
> We have several other machines that conenct the same way and they do not
> have the issue.

Neil Pike. Protech Computing Ltd
http://www.linkedin.com/in/neilpike

02-12-2009

Hi Scott,

I am sorry to hear that.

Generally, the networking guys in the PLATFORMS SERVER team should be able
to help you analyze the issue. Do you get the case ID for this issue? I can
help you check the current status of the case if I know the case ID.

Thank you for your patience.

Sincerely,
Joson Zhou
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

02-10-2009	#1 (permalink)
Scott Townsend n/a posts	Connecting to L2TP VPN on 64bit is crashing... I have 2 machined that are Vista 64bit (all the latest updates) that are connecting to a L2TP VPN Connection. When connected to the VPN and doing data transfers, the machine will sometimes crash with the bugcheck info below... We have several other machines that conenct the same way and they do not have the issue. Any Suggestions? Thanks, Scott<- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a portion of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffffa60025878d0 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80001e71eae to fffff80001e72110 STACK_TEXT: fffff800`0304ed28 fffff800`01e71eae : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff800`0304ed30 fffff800`01e706f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e fffff800`0304ee70 fffffa60`025878d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8 fffffa60`01fa2fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndiswan!ProtoCoSendComplete+0x50 STACK_COMMAND: kb FOLLOWUP_IP: ndiswan!ProtoCoSendComplete+50 fffffa60`025878d0 ff15c2d90100 call qword ptr [ndiswan!_imp_NdisAcquireReadWriteLock (fffffa60`025a5298)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: ndiswan!ProtoCoSendComplete+50 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndiswan IMAGE_NAME: ndiswan.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47919aad FAILURE_BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50 BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50 Followup: MachineOwner ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a portion of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffffa60025878d0 Debugging Details: ------------------ Page 77189 not present in the dump file. Type ".hh dbgerr004" for details PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80001e71eae to fffff80001e72110 STACK_TEXT: fffff800`0304ed28 fffff800`01e71eae : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff800`0304ed30 fffff800`01e706f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e fffff800`0304ee70 fffffa60`025878d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8 fffffa60`01fa2fe0 fffffa60`00e11557 : fffffa80`08a19a00 00000000`00001630 fffffa80`066a9ba0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0x50 fffffa60`01fa3040 fffffa60`0255745c : fffffa80`078d8440 fffffa80`066a9ba0 fffffa80`0499bb98 00000000`00000000 : ndis!ndisMCoSendCompleteToNdisPacket+0x127 fffffa60`01fa3090 fffffa60`02557009 : 00000000`00000003 fffffa80`04bd22a0 fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec fffffa60`01fa30e0 fffffa60`0255708b : fffffa80`06125950 00000000`00000000 00000000`00000000 fffffa80`062aa9c0 : rasl2tp!L2tpSendComplete+0x89 fffffa60`01fa3110 fffff800`01e74485 : fffffa80`062aa9c0 00000000`00000000 00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b fffffa60`01fa3150 fffffa60`04806f78 : 00000000`00000000 fffffa80`062aa902 fffffa80`06304800 00000000`00000000 : nt!IopfCompleteRequest+0x315 fffffa60`01fa3210 fffffa60`0481376c : fffffa80`063048a0 00000000`00000000 fffffa80`06304800 00000000`614b5357 : afd!WskProTLSendToComplete+0x48 fffffa60`01fa3240 fffff800`01e74485 : fffffa80`063048a0 fffff800`01f52e96 00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c fffffa60`01fa3270 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000102 fffffa80`063048a0 00000000`42786454 : nt!IopfCompleteRequest+0x315 fffffa60`01fa3330 fffffa60`01064860 : 00000000`00000000 fffffa80`04e981e0 00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8 fffffa60`01fa3370 fffffa60`00cdca48 : fffffa80`04e98030 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpSendMessagesDatagramsComplete+0xf0 fffffa60`01fa33d0 fffffa60`048e25fa : 00000000`00000000 fffffa80`066d0310 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferList+0x78 fffffa60`01fa3400 fffffa60`00fab0b2 : fffffa80`066d0310 fffffa80`07a34a10 fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a fffffa60`01fa3430 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000 fffffa80`079e4580 fffffa60`00e1ba29 : ndis!ndisMSendCompleteNetBufferListsInternal+0xa2 fffffa60`01fa34a0 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000 00000000`00000000 00000000`00000000 : pacer!PcFilterSendNetBufferListsComplete+0xf4 fffffa60`01fa3510 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000 fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195 fffffa60`01fa3560 fffffa60`0258795b : 00000000`00000000 fffffa80`08c5ab70 fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df fffffa60`01fa35c0 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff fffffa80`066a9ec0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb fffffa60`01fa3620 fffffa60`0255745c : fffffa80`078d8440 fffffa80`066a9ec0 fffffa80`0499bb48 00000000`00000000 : ndis!ndisMCoSendCompleteToNdisPacket+0x127 fffffa60`01fa3670 fffffa60`02557009 : 00000000`00000003 fffffa80`068f5cd0 fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec fffffa60`01fa36c0 fffffa60`0255708b : fffffa80`066c1750 00000000`00000000 00000000`00000000 fffffa80`067a9560 : rasl2tp!L2tpSendComplete+0x89 fffffa60`01fa36f0 fffff800`01e74485 : fffffa80`067a9560 00000000`00000000 00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b fffffa60`01fa3730 fffffa60`04806f78 : 00000000`00000000 fffffa80`067a9502 fffffa80`0675cb00 00000000`00000000 : nt!IopfCompleteRequest+0x315 fffffa60`01fa37f0 fffffa60`0481376c : fffffa80`0675cb80 00000000`00000000 fffffa80`0675cb00 00000000`614b5357 : afd!WskProTLSendToComplete+0x48 fffffa60`01fa3820 fffff800`01e74485 : fffffa80`0675cb80 fffff800`01f52e96 00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c fffffa60`01fa3850 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000102 fffffa80`0675cb80 00000000`42786454 : nt!IopfCompleteRequest+0x315 fffffa60`01fa3910 fffffa60`01064860 : 00000000`00000000 fffffa80`0499d1e0 00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8 fffffa60`01fa3950 fffffa60`00cdca48 : fffffa80`0499d030 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpSendMessagesDatagramsComplete+0xf0 fffffa60`01fa39b0 fffffa60`048e25fa : 00000000`00000000 fffffa80`0720ae20 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferList+0x78 fffffa60`01fa39e0 fffffa60`00fab0b2 : fffffa80`0720ae20 fffffa80`07a34a10 fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a fffffa60`01fa3a10 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000 fffffa80`079e4580 fffffa60`00e1ba29 : ndis!ndisMSendCompleteNetBufferListsInternal+0xa2 fffffa60`01fa3a80 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000 00000000`00000000 00000000`00000000 : pacer!PcFilterSendNetBufferListsComplete+0xf4 fffffa60`01fa3af0 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000 fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195 fffffa60`01fa3b40 fffffa60`0258795b : 00000000`00000000 fffffa80`06508010 fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df fffffa60`01fa3ba0 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff fffffa80`04a490b0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb fffffa60`01fa3c00 fffffa60`0255745c : fffffa80`078d8440 fffffa80`04a490b0 fffffa80`0499baf8 00000000`00000000 : ndis!ndisMCoSendCompleteToNdisPacket+0x127 fffffa60`01fa3c50 fffffa60`02557009 : 00000000`00000003 fffffa80`0677dcc0 fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec fffffa60`01fa3ca0 fffffa60`0255708b : fffffa80`0677cb60 00000000`00000000 00000000`00000000 fffffa80`08ccb010 : rasl2tp!L2tpSendComplete+0x89 fffffa60`01fa3cd0 fffff800`01e74485 : fffffa80`08ccb010 00000000`00000000 00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b fffffa60`01fa3d10 fffffa60`04806f78 : 00000000`00000000 fffffa80`08ccb002 fffffa80`061b2b00 00000000`00000000 : nt!IopfCompleteRequest+0x315 fffffa60`01fa3dd0 fffffa60`0481376c : fffffa80`061b2b80 00000000`00000000 fffffa80`061b2b00 00000000`614b5357 : afd!WskProTLSendToComplete+0x48 fffffa60`01fa3e00 fffff800`01e74485 : fffffa80`061b2b80 fffff800`01f52e96 00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c fffffa60`01fa3e30 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000202 fffffa80`061b2b80 00000000`42786454 : nt!IopfCompleteRequest+0x315 fffffa60`01fa3ef0 fffffa60`01064860 : 00000000`00000000 fffffa80`054c7b60 00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8 fffffa60`01fa3f30 fffffa60`00cdca48 : fffffa80`054c79b0 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpSendMessagesDatagramsComplete+0xf0 fffffa60`01fa3f90 fffffa60`048e25fa : 00000000`00000000 fffffa80`0660e030 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferList+0x78 fffffa60`01fa3fc0 fffffa60`00fab0b2 : fffffa80`0660e030 fffffa80`07a34a10 fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a fffffa60`01fa3ff0 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000 fffffa80`079e4580 fffffa60`00e1ba29 : ndis!ndisMSendCompleteNetBufferListsInternal+0xa2 fffffa60`01fa4060 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000 00000000`00000000 00000000`00000000 : pacer!PcFilterSendNetBufferListsComplete+0xf4 fffffa60`01fa40d0 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000 fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195 fffffa60`01fa4120 fffffa60`0258795b : 00000000`00000000 fffffa80`04f02010 fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df fffffa60`01fa4180 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff fffffa80`04a49240 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb fffffa60`01fa41e0 fffffa60`0255745c : fffffa80`078d8440 fffffa80`04a49240 fffffa80`0499baa8 00000000`00000000 : ndis!ndisMCoSendCompleteToNdisPacket+0x127 fffffa60`01fa4230 fffffa60`02557009 : 00000000`00000003 fffffa80`047d6df0 fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec fffffa60`01fa4280 fffffa60`0255708b : fffffa80`04a4c160 00000000`00000000 00000000`00000000 fffffa80`0610a5d0 : rasl2tp!L2tpSendComplete+0x89 fffffa60`01fa42b0 fffff800`01e74485 : fffffa80`0610a5d0 00000000`00000000 00000000`00000000 00000000`00000000 : rasl2tp!WskSendCompletion+0x4b fffffa60`01fa42f0 fffffa60`04806f78 : 00000000`00000000 fffffa80`0610a502 fffffa80`066e0200 00000000`00000000 : nt!IopfCompleteRequest+0x315 fffffa60`01fa43b0 fffffa60`0481376c : fffffa80`066e0260 00000000`00000000 fffffa80`066e0200 00000000`614b5357 : afd!WskProTLSendToComplete+0x48 fffffa60`01fa43e0 fffff800`01e74485 : fffffa80`066e0260 fffff800`01f52e96 00000000`00000000 00000000`00000000 : afd!WskTdiCOMPSendTo+0x4c fffffa60`01fa4410 fffffa60`00fe0698 : fffffa80`0796fa40 00000000`00000202 fffffa80`066e0260 00000000`42786454 : nt!IopfCompleteRequest+0x315 fffffa60`01fa44d0 fffffa60`01064860 : 00000000`00000000 fffffa80`090b61e0 00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0xa8 fffffa60`01fa4510 fffffa60`00cdca48 : fffffa80`090b6030 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpSendMessagesDatagramsComplete+0xf0 fffffa60`01fa4570 fffffa60`048e25fa : 00000000`00000000 fffffa80`0679d320 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferList+0x78 fffffa60`01fa45a0 fffffa60`00fab0b2 : fffffa80`0679d320 fffffa80`07a34a10 fffffa80`072f81a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x9a fffffa60`01fa45d0 fffffa60`048ba8ec : fffffa80`072f81a0 00000000`00000000 fffffa80`079e4580 fffffa60`00e1bae7 : ndis!ndisMSendCompleteNetBufferListsInternal+0xa2 fffffa60`01fa4640 fffffa60`00fabc25 : fffffa80`072f81a0 00000000`00000000 00000000`00000000 00000000`00000000 : pacer!PcFilterSendNetBufferListsComplete+0xf4 fffffa60`01fa46b0 fffffa60`025863ef : fffffa60`025aa600 00000000`00000000 fffffa80`0650e6c0 fffffa60`025aa110 : ndis!ndisMSendCompleteX+0x195 fffffa60`01fa4700 fffffa60`0258795b : 00000000`00000000 fffffa80`067fbb70 fffffa80`08a19a00 fffffa80`060ab010 : ndiswan!CompleteSendDesc+0x1df fffffa60`01fa4760 fffffa60`00e11557 : fffffa80`08a19a00 00000000`0002ffff fffffa80`04a493d0 00000000`00000000 : ndiswan!ProtoCoSendComplete+0xdb fffffa60`01fa47c0 fffffa60`0255745c : fffffa80`078d8440 fffffa80`04a493d0 fffffa80`0499ba58 00000000`00000000 : ndis!ndisMCoSendCompleteToNdisPacket+0x127 fffffa60`01fa4810 fffffa60`02557009 : 00000000`00000003 fffffa80`071eab80 fffffa80`078d84e8 00000000`00000000 : rasl2tp!SendPayloadUnseqComplete+0xec fffffa60`01fa4860 fffffa60`0255708b : fffffa80`071ef8d0 00000000`00000000 00000000`00000000 fffffa80`06522a00 : rasl2tp!L2tpSendComplete+0x89 STACK_COMMAND: kb FOLLOWUP_IP: ndiswan!ProtoCoSendComplete+50 fffffa60`025878d0 ff15c2d90100 call qword ptr [ndiswan!_imp_NdisAcquireReadWriteLock (fffffa60`025a5298)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: ndiswan!ProtoCoSendComplete+50 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndiswan IMAGE_NAME: ndiswan.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47919aad FAILURE_BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50 BUCKET_ID: X64_0x7f_8_ndiswan!ProtoCoSendComplete+50 Followup: MachineOwner --------- ---------
My System Specs

02-11-2009	#2 (permalink)
Joson Zhou n/a posts	RE: Connecting to L2TP VPN on 64bit is crashing... Hi Scott, Thank you for posting in newsgroup. To locate the exact problem of the stop error, we need to analyze the crash dump file. Unfortunately, we cannot help you analyze the dump file in newsgroup. To trouble shoot this problem efficiently, I suggest that you speak directly with a Microsoft Support Professional so that the crash dump can be analyzed. Here are some articles that will help prepare you for this call: For a complete list of Microsoft Product Support Services phone numbers and information about support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/directory/overview.asp Thank you for your understanding and cooperation. Sincerely, Joson Zhou Microsoft Online Support Microsoft Global Technical Support Center Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
My System Specs

02-11-2009	#3 (permalink)
Scott Townsend n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... Thanks, though now that I've been transferred to 3 different people I don't think they now what I'm asking them... Any way to get to someone who knows what L2TP is? Scott<- ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message news:c04i2hCjJHA.5012@xxxxxx Quote: > Hi Scott, > > Thank you for posting in newsgroup. > > To locate the exact problem of the stop error, we need to analyze the > crash > dump file. Unfortunately, we cannot help you analyze the dump file in > newsgroup. To trouble shoot this problem efficiently, I suggest that you > speak directly with a Microsoft Support Professional so that the crash > dump > can be analyzed. Here are some articles that will help prepare you for > this > call: > > For a complete list of Microsoft Product Support Services phone numbers > and > information about support costs, please go to the following address on the > World Wide Web: > http://support.microsoft.com/directory/overview.asp > > Thank you for your understanding and cooperation. > > Sincerely, > Joson Zhou > Microsoft Online Support > Microsoft Global Technical Support Center > > Get Secure! - www.microsoft.com/security > ===================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. >
My System Specs

02-11-2009	#4 (permalink)
Scott Townsend n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... Transferred Again... "Scott Townsend" <scooter133@xxxxxx> wrote in message news:O34bAPJjJHA.5124@xxxxxx Quote: > Thanks, though now that I've been transferred to 3 different people I > don't think they now what I'm asking them... > > Any way to get to someone who knows what L2TP is? > > Scott<- > ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message > news:c04i2hCjJHA.5012@xxxxxx Quote: >> Hi Scott, >> >> Thank you for posting in newsgroup. >> >> To locate the exact problem of the stop error, we need to analyze the >> crash >> dump file. Unfortunately, we cannot help you analyze the dump file in >> newsgroup. To trouble shoot this problem efficiently, I suggest that you >> speak directly with a Microsoft Support Professional so that the crash >> dump >> can be analyzed. Here are some articles that will help prepare you for >> this >> call: >> >> For a complete list of Microsoft Product Support Services phone numbers >> and >> information about support costs, please go to the following address on >> the >> World Wide Web: >> http://support.microsoft.com/directory/overview.asp >> >> Thank you for your understanding and cooperation. >> >> Sincerely, >> Joson Zhou >> Microsoft Online Support >> Microsoft Global Technical Support Center >> >> Get Secure! - www.microsoft.com/security >> ===================================================== >> When responding to posts, please "Reply to Group" via your newsreader so >> that others may learn and benefit from your issue. >> ===================================================== >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >
My System Specs

02-11-2009	#5 (permalink)
Scott Townsend n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... Transferred again... I think I'm up to 6 people.. When I offered the Crash Debug info they said they didn't need it... They didn't really care about the Stop Code... "Scott Townsend" <scooter133@xxxxxx> wrote in message news:O6T6qQJjJHA.3656@xxxxxx Quote: > Transferred Again... > "Scott Townsend" <scooter133@xxxxxx> wrote in message > news:O34bAPJjJHA.5124@xxxxxx Quote: >> Thanks, though now that I've been transferred to 3 different people I >> don't think they now what I'm asking them... >> >> Any way to get to someone who knows what L2TP is? >> >> Scott<- >> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message >> news:c04i2hCjJHA.5012@xxxxxx Quote: >>> Hi Scott, >>> >>> Thank you for posting in newsgroup. >>> >>> To locate the exact problem of the stop error, we need to analyze the >>> crash >>> dump file. Unfortunately, we cannot help you analyze the dump file in >>> newsgroup. To trouble shoot this problem efficiently, I suggest that you >>> speak directly with a Microsoft Support Professional so that the crash >>> dump >>> can be analyzed. Here are some articles that will help prepare you for >>> this >>> call: >>> >>> For a complete list of Microsoft Product Support Services phone numbers >>> and >>> information about support costs, please go to the following address on >>> the >>> World Wide Web: >>> http://support.microsoft.com/directory/overview.asp >>> >>> Thank you for your understanding and cooperation. >>> >>> Sincerely, >>> Joson Zhou >>> Microsoft Online Support >>> Microsoft Global Technical Support Center >>> >>> Get Secure! - www.microsoft.com/security >>> ===================================================== >>> When responding to posts, please "Reply to Group" via your newsreader so >>> that others may learn and benefit from your issue. >>> ===================================================== >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> >> >
My System Specs

02-11-2009	#6 (permalink)
Scott Townsend n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... 7th Transfer... Going on over 30 minutes with not talking to anyone who knows what L2TP is... "Scott Townsend" <scooter133@xxxxxx> wrote in message news:%23xMJgZJjJHA.4644@xxxxxx Quote: > Transferred again... I think I'm up to 6 people.. > > When I offered the Crash Debug info they said they didn't need it... They > didn't really care about the Stop Code... > > "Scott Townsend" <scooter133@xxxxxx> wrote in message > news:O6T6qQJjJHA.3656@xxxxxx Quote: >> Transferred Again... >> "Scott Townsend" <scooter133@xxxxxx> wrote in message >> news:O34bAPJjJHA.5124@xxxxxx Quote: >>> Thanks, though now that I've been transferred to 3 different people I >>> don't think they now what I'm asking them... >>> >>> Any way to get to someone who knows what L2TP is? >>> >>> Scott<- >>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message >>> news:c04i2hCjJHA.5012@xxxxxx >>>> Hi Scott, >>>> >>>> Thank you for posting in newsgroup. >>>> >>>> To locate the exact problem of the stop error, we need to analyze the >>>> crash >>>> dump file. Unfortunately, we cannot help you analyze the dump file in >>>> newsgroup. To trouble shoot this problem efficiently, I suggest that >>>> you >>>> speak directly with a Microsoft Support Professional so that the crash >>>> dump >>>> can be analyzed. Here are some articles that will help prepare you for >>>> this >>>> call: >>>> >>>> For a complete list of Microsoft Product Support Services phone numbers >>>> and >>>> information about support costs, please go to the following address on >>>> the >>>> World Wide Web: >>>> http://support.microsoft.com/directory/overview.asp >>>> >>>> Thank you for your understanding and cooperation. >>>> >>>> Sincerely, >>>> Joson Zhou >>>> Microsoft Online Support >>>> Microsoft Global Technical Support Center >>>> >>>> Get Secure! - www.microsoft.com/security >>>> ===================================================== >>>> When responding to posts, please "Reply to Group" via your newsreader >>>> so >>>> that others may learn and benefit from your issue. >>>> ===================================================== >>>> This posting is provided "AS IS" with no warranties, and confers no >>>> rights. >>>> >>> >> >
My System Specs

02-11-2009	#7 (permalink)
Scott Townsend n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... #8!! Apparently the Vista Networking Team does not do VPN... "Scott Townsend" <scooter133@xxxxxx> wrote in message news:Oj0L$eJjJHA.4976@xxxxxx Quote: > 7th Transfer... Going on over 30 minutes with not talking to anyone who > knows what L2TP is... > > > "Scott Townsend" <scooter133@xxxxxx> wrote in message > news:%23xMJgZJjJHA.4644@xxxxxx Quote: >> Transferred again... I think I'm up to 6 people.. >> >> When I offered the Crash Debug info they said they didn't need it... They >> didn't really care about the Stop Code... >> >> "Scott Townsend" <scooter133@xxxxxx> wrote in message >> news:O6T6qQJjJHA.3656@xxxxxx Quote: >>> Transferred Again... >>> "Scott Townsend" <scooter133@xxxxxx> wrote in message >>> news:O34bAPJjJHA.5124@xxxxxx >>>> Thanks, though now that I've been transferred to 3 different people I >>>> don't think they now what I'm asking them... >>>> >>>> Any way to get to someone who knows what L2TP is? >>>> >>>> Scott<- >>>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message >>>> news:c04i2hCjJHA.5012@xxxxxx >>>>> Hi Scott, >>>>> >>>>> Thank you for posting in newsgroup. >>>>> >>>>> To locate the exact problem of the stop error, we need to analyze the >>>>> crash >>>>> dump file. Unfortunately, we cannot help you analyze the dump file in >>>>> newsgroup. To trouble shoot this problem efficiently, I suggest that >>>>> you >>>>> speak directly with a Microsoft Support Professional so that the crash >>>>> dump >>>>> can be analyzed. Here are some articles that will help prepare you for >>>>> this >>>>> call: >>>>> >>>>> For a complete list of Microsoft Product Support Services phone >>>>> numbers and >>>>> information about support costs, please go to the following address on >>>>> the >>>>> World Wide Web: >>>>> http://support.microsoft.com/directory/overview.asp >>>>> >>>>> Thank you for your understanding and cooperation. >>>>> >>>>> Sincerely, >>>>> Joson Zhou >>>>> Microsoft Online Support >>>>> Microsoft Global Technical Support Center >>>>> >>>>> Get Secure! - www.microsoft.com/security >>>>> ===================================================== >>>>> When responding to posts, please "Reply to Group" via your newsreader >>>>> so >>>>> that others may learn and benefit from your issue. >>>>> ===================================================== >>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>> rights. >>>>> >>>> >>> >> >
My System Specs

02-11-2009	#8 (permalink)
Scott Townsend n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... OMG!!! " Cisco? What Microsoft product is installed on that?" "VPN, that is a Virtual Desktop right?" "Scott Townsend" <scooter133@xxxxxx> wrote in message news:OX2QflJjJHA.3716@xxxxxx Quote: > #8!! Apparently the Vista Networking Team does not do VPN... > > "Scott Townsend" <scooter133@xxxxxx> wrote in message > news:Oj0L$eJjJHA.4976@xxxxxx Quote: >> 7th Transfer... Going on over 30 minutes with not talking to anyone who >> knows what L2TP is... >> >> >> "Scott Townsend" <scooter133@xxxxxx> wrote in message >> news:%23xMJgZJjJHA.4644@xxxxxx Quote: >>> Transferred again... I think I'm up to 6 people.. >>> >>> When I offered the Crash Debug info they said they didn't need it... >>> They didn't really care about the Stop Code... >>> >>> "Scott Townsend" <scooter133@xxxxxx> wrote in message >>> news:O6T6qQJjJHA.3656@xxxxxx >>>> Transferred Again... >>>> "Scott Townsend" <scooter133@xxxxxx> wrote in message >>>> news:O34bAPJjJHA.5124@xxxxxx >>>>> Thanks, though now that I've been transferred to 3 different people I >>>>> don't think they now what I'm asking them... >>>>> >>>>> Any way to get to someone who knows what L2TP is? >>>>> >>>>> Scott<- >>>>> ""Joson Zhou (MSFT)"" <v-josz@xxxxxx> wrote in message >>>>> news:c04i2hCjJHA.5012@xxxxxx >>>>>> Hi Scott, >>>>>> >>>>>> Thank you for posting in newsgroup. >>>>>> >>>>>> To locate the exact problem of the stop error, we need to analyze the >>>>>> crash >>>>>> dump file. Unfortunately, we cannot help you analyze the dump file in >>>>>> newsgroup. To trouble shoot this problem efficiently, I suggest that >>>>>> you >>>>>> speak directly with a Microsoft Support Professional so that the >>>>>> crash dump >>>>>> can be analyzed. Here are some articles that will help prepare you >>>>>> for this >>>>>> call: >>>>>> >>>>>> For a complete list of Microsoft Product Support Services phone >>>>>> numbers and >>>>>> information about support costs, please go to the following address >>>>>> on the >>>>>> World Wide Web: >>>>>> http://support.microsoft.com/directory/overview.asp >>>>>> >>>>>> Thank you for your understanding and cooperation. >>>>>> >>>>>> Sincerely, >>>>>> Joson Zhou >>>>>> Microsoft Online Support >>>>>> Microsoft Global Technical Support Center >>>>>> >>>>>> Get Secure! - www.microsoft.com/security >>>>>> ===================================================== >>>>>> When responding to posts, please "Reply to Group" via your newsreader >>>>>> so >>>>>> that others may learn and benefit from your issue. >>>>>> ===================================================== >>>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>>> rights. >>>>>> >>>>> >>>> >>> >> >
My System Specs

02-12-2009	#9 (permalink)
Neil Pike n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... Scott - you're not using the Cisco VPN client at all? I see no sign of it in your stack trace, so I'm assuming this is a pure MS L2TP session. In which case it looks like a bug - no doubt something in the packets from the Cisco VPN termination device it doesn't like (you did mention Cisco) All you can do is hang on until you get to someone that is interested in the blue screen dump as that's what they'll need to resolve it, and maybe a netmon/wireshark/sniffer trace as well. Not something that anyone without Windows source code access is going to be able to debug, so you need what MS PSS term an "escalation engineer" Quote: > I have 2 machined that are Vista 64bit (all the latest updates) that are > connecting to a L2TP VPN Connection. > > When connected to the VPN and doing data transfers, the machine will > sometimes crash with the bugcheck info below... > We have several other machines that conenct the same way and they do not > have the issue. Neil Pike. Protech Computing Ltd http://www.linkedin.com/in/neilpike
My System Specs

02-12-2009	#10 (permalink)
Joson Zhou n/a posts	Re: Connecting to L2TP VPN on 64bit is crashing... Hi Scott, I am sorry to hear that. Generally, the networking guys in the PLATFORMS SERVER team should be able to help you analyze the issue. Do you get the case ID for this issue? I can help you check the current status of the case if I know the case ID. Thank you for your patience. Sincerely, Joson Zhou Microsoft Online Support Microsoft Global Technical Support Center Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
My System Specs

Similar Threads
Thread	Forum
L2TP VPN Problems	Vista General
IE 64bit Crashing. 32bit OK	Software
help:blue-screen error when connecting vpn whit l2tp protocol	Vista networking & sharing
L2TP with preshared key?	Vista networking & sharing
L2TP VPN Connection	Vista networking & sharing