VISTA VPN ISSUES

Just recently we’ve started getting VPN issues between Windows Vista and
Windows XP SP2 and an SBS Server

So far I discounted the RAS configuration and routers. There is the office
site where SBS is located. There are 4 remote sites which i’ll name “MMH”
“AMH” “DSH” & “SMH” there are then 6 machines that i’ve used for testing the
issues:

MMLT – Vista Business Tablet
MMDT – Vista Ultimate w/OneCare
DSLT – XP Tablet SP2
AMDT – XP Pro SP2
AMLT – XP Pro SP2
SMDT – XP Pro SP2

I’ve tested machines that work at different remote sites so i know each works.

I’ve managed to get the MMDT to connect today which was the OneCare Firewall
issue from MMH to the OFFICE

MMLT is not connecting and getting error 800, i’ve added PPTP 1723 and GRE
47 to the firewall exceptions and run Port Query which gets to the server.
I’ve tested the connection from both the OFFICE LAN and other sites and only
get error 800. I’ve also tested the User privileges

DSLT can connect to RAS from the OFFICE but no other locations

All the other machines can connect using different locations inc. MMH

Have run a diag log


-------------------------------------------------------------------------------
C:\Windows\tracing\RASTAPI.LOG
-------------------------------------------------------------------------------

[2148] 02-20 12:12:30:335: PortOpen: VPN1-1
[2148] 02-20 12:12:30:335: Opening line in monitor mode
[2148] 02-20 12:12:30:335: PortOpen: successfully opened VPN1-1
[2148] 02-20 12:12:30:335:
[2148] 02-20 12:12:30:351: DeviceConnect: calling lineMakeCall for VPN1-1,
address=[RAS SERVER OFFICE]
[2148] 02-20 12:12:30:351: DeviceConnect: Changing state for VPN1-1 from 1
-> 4
[4056] 02-20 12:12:30:351: RasTapicallback: msg=12 , param1=65622l , param2=0l
[4056] 02-20 12:12:30:351: LINE_REPLY. param1=0x10056
[4056] 02-20 12:12:30:351: RasTapicallback: msg=2 , param1=16384l , param2=2l
[4056] 02-20 12:12:30:351: RasTapicallback: linecallstate=0x4000
[4056] 02-20 12:12:30:351: RASDiag: Mapping to new error code: 807
(ERROR_VPN_DISCONNECT) instead of 651 (ERROR_FROM_DEVICE)
[4056] 02-20 12:12:30:351: RasTapiCallback: LINECALLSTATE_DISCONNECTED for
port VPN1-1. AsyncErr = 807, param2=0x2
[3988] 02-20 12:12:30:351: DeviceWork: VPN1-1. State = 4
[2148] 02-20 12:12:30:351: PortDisconnect: VPN1-1
[2148] 02-20 12:12:30:351: InitiatePortDisconnection: VPN1-1
[2148] 02-20 12:12:30:351: InitiatePortDisconnection: Changing state for
VPN1-1 from 4 -> 5, id=0x103ce
[2148] 02-20 12:12:30:351:
[2148] 02-20 12:12:30:351:
[4056] 02-20 12:12:30:351: RasTapicallback: msg=12 , param1=66510l ,
param2=2147483720l
[4056] 02-20 12:12:30:351: LINE_REPLY. param1=0x103ce
[4056] 02-20 12:12:30:351: RasTapiCallback: lineDropped. port VPN1-1,
id=0xffffffff
[2148] 02-20 12:12:40:054: PortClose: VPN1-1
[2148] 02-20 12:12:40:054: No more ports opened for dialout on this line
[2148] 02-20 12:12:40:054: Closing line
[2148] 02-20 12:12:40:054: PortClose: Changing state for VPN1-1 from 5 -> 0
[2148] 02-20 12:12:40:054:
[2148] 02-20 12:12:40:054: PortOpen: VPN0-1
[2148] 02-20 12:12:40:054: Opening line in owner mode
[2148] 02-20 12:12:40:054: PortOpen: successfully opened VPN0-1
[2148] 02-20 12:12:40:054:
[6032] 02-20 12:12:40:069: PortClose: VPN0-1
[6032] 02-20 12:12:40:069: Closing line
[6032] 02-20 12:12:40:069: PortClose: Changing state for VPN0-1 from 1 -> 0
[6032] 02-20 12:12:40:069:
--

Mark Masiak
devlinfisher*


.

Relevant Pages

  • Re: Windows Server 2003 SP2 and Vista Issue.
    ... I will leave SP2 off until it is pushed out to more people and see if the issue is more common. ... then I will have to do a reinstall which is a big job for this server. ... and browse the shares of the server from Windows Vista (I have two installs ... of Vista) it is very slow to resolve folder names. ...
    (microsoft.public.windows.server.networking)
  • Re: Slow communication after Windows 2003 SP2 installation
    ... On the principal production server I've unistalled the SP2, and all works fine now with Vista clients. ... I have other two x64 servers with SP2 installed, not so critical as the other, and I'll test with them what "mmmm" sugests in his posts. ... >>> XP SP2 machine can communicate without any delay. ...
    (microsoft.public.windows.server.general)
  • Re: Windows Server 2003 SP2 and Vista Issue.
    ... Most cases like this have been resolved using the command netsh interface tcp set global autotuninglevel=disabled on the Windows Vista client. ... I cringe at a solution of "well, I'll just uninstall SP2", so I hope this works for you. ... >> and browse the shares of the server from Windows Vista (I have two ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 SP2 and Vista Issue.
    ... Most cases like this have been resolved using the command netsh interface tcp set global autotuninglevel=disabled on the Windows Vista client. ... I cringe at a solution of "well, I'll just uninstall SP2", so I hope this works for you. ... I have installed Windows Server 2003 SP2 on my R2 server. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 SP2 and Vista Issue.
    ... Just re-installed SP2 for Winows Server 2003, ... I will have to roll back the Vista machines to XP at this rate. ... I have installed Windows Server 2003 SP2 on my R2 server. ... Ran a robocopy from the Server to the Vista machine (surprise surprise, ...
    (microsoft.public.windows.server.networking)