Question

Locked

Vista VPN wont disconnect

By brendan-news ·
Hi there,

I'm using Vista's VPN client to connect to our ISA 2004 server across the net.

I can connect/disconnect fine, until I start using applications like Microsoft Office across the VPN. From this point, if I try to disconnect it hangs completely and seems to prevent the computer from going to sleep, often resulting in a BlueScreen stop.

Any ideas?

Cheers,
Brendan

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

See how you go with this

by Jacky Howe In reply to Vista VPN wont disconnect

My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.
<br><br>
Restart the PC normally as this will allow the PC to Blue Screen. Take note of Stop 0X000000 error message and Google it.
<br><br>
Or if you are feeling adventurous
<br><br>
Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp
<br><br>
How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263
<br><br>
To download and install the Windows debugging tools, visit the following Microsoft Web site:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
<br><br>
Instructions on using Windbg.
<br><br>
Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
<br><br>
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.
<br><br>
Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
FAULTING_THREA 864f6a98
<br><br>
DEFAULT_BUCKET_I GRAPHICS_DRIVER_FAULT
<br><br>
CUSTOMER_CRASH_COUNT: 1
<br><br>
BUGCHECK_STR: 0xEA
<br><br>
PROCESS_NAME: logon.scr
<br><br>
LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea
<br><br>
STACK_TEXT:
f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

<br><br>
STACK_COMMAN .thread 0xffffffff864f6a98 ; kb
<br><br>
FOLLOWUP_IP:
sgiul50!DrvBitBlt+585
bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)
<br><br>
SYMBOL_STACK_INDEX: 0
<br><br>
SYMBOL_NAME: sgiul50!DrvBitBlt+585
<br><br>
FOLLOWUP_NAME: MachineOwner
<br><br>
MODULE_NAME: sgiul50
<br><br>
IMAGE_NAME: sgiul50.dll
<br><br>
DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7
<br><br>
FAILURE_BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
<br><br>
BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
<br><br>
You couls also try this.

<br><br>
I would download filemon from SysInternals. Then logon as a normal user, right click and select runas then use the Administrator Account to start filemon.
<br><br>
Then stop filemon from logging just after your freeze. Then look in the Filemon Log for any discrepancies.
<br><br>
Filemon:
<br><br>
http://www.sysinternals.com/Utilities/Filemon.html

Collapse -

Thanks!

by brendan-news In reply to See how you go with this

Thanks Jacky,

I hadn't thought of using filemon. Will give it a crack. And I've changed the Startup and Recovery options.

Cheers,
Brendan

Collapse -

Keep us posted

by Jacky Howe In reply to Thanks!

to let us know how you are getting on.

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums