error 676 when connecting to W2003 VPN-server

  • Thread starter Christian Krackowizer
  • Start date

C

Christian Krackowizer

Hi,

To document all the necessary settings for a VPN connection using different
clients to different servers, we've setup 2 servers with RRAS as VPN-
Servers. One has W2000 SP4, the other W2003 installed. Both are members of
a W2000 AD. Both have 2 NICs, one for intranet LAN with private IP, one for
internet access with offical IP.
The DC is a certificate server, both VPN-Servers got their certificates
through policy. An IPSec policy is created locally for UDP/2701
The client test machine is multibooting Windows XP, 2000 and NT 4.0. For
access with Windows NT 4.0 is MSLT2P client installed. The settings for the
VPN-Connections are defaults. As user authorisation a valid AD user is used
(with dialup rights). There's an ISDN modem on the machine to dial up
internet. The certificates where installed from floppy. An IPSec policy is
also created locally for UDP/2701
There's no NAT involved.
Well, the client test machine can establish the tunnel when connecting to
the W2000 VPN-Server, using either PPTP or L2TP. Everything's fine. Access
works.
When connecting to W2003 VPN-Server, only PPTP works (with indentical
settings on the client machine). L2TP fails with 'error 676 line is busy'.
With a network monitor, I can see the tunnel is already up, as only
protocol 50 is active. But after a few packages the communication stops and
the error is displayed. Looks like the PPP communiction failed, but the
settings are the same as with PPTP used ...
The security event log on the W2003 VPN-Servers says IKE authorisation is
established.
Changed from certificates to pre-defined keys, still the same. W2000 works,
W2003 not. Installed the W2003 fresh from CD, same error.
? any ideas what's different ?
 
Ad

Advertisements

K

Kadirvel C Vanniarajan [MSFT]

Can you post the logs (enabled from RRAS Properties->Logging->Log additional
Routing and Remote Access Information)? Probably, from the logs we can
gather more information onto why the line is failing.One potential reason
why the 'line is busy' can occur is where there is no ports free for L2TP on
the server to accept the call.
 
C

Christian Krackowizer

Can you post the logs (enabled from RRAS Properties->Logging->Log
additional Routing and Remote Access Information)? Probably, from the
logs we can gather more information onto why the line is failing.One
potential reason why the 'line is busy' can occur is where there is no
ports free for L2TP on the server to accept the call.
Hi Kadir,

there are a lot of logs, I think the most interesting is RASTAPI.LOG
there's extract: I configured with the default of 128 ports for both PPTP
and L2TP. I removed all entries but those for port 127. VPN4-127 is L2TP,
VPN5-127 is PPTP. Logging started at 14:30. Only all VPN5-ports changed
their listen state !?
In RRAS/Ports looking at the status of the L2TP ports, they show
'Condition-listening' too!?
At 14:41 I tried to connect with LT2P, you'll see the error.

[2328] 09-29 14:30:25:985: PortOpen: VPN4-127
[2328] 09-29 14:30:25:985: Opening line in owner mode
[2328] 09-29 14:30:26:001: PortOpen: successfully opened VPN4-127
[2328] 09-29 14:30:26:202: PortOpen: VPN5-127
[2328] 09-29 14:30:26:202: Opening line in owner mode
[2328] 09-29 14:30:26:202: PortOpen: successfully opened VPN5-127
[2328] 09-29 14:30:26:326: PortOpen: PPPoE6-0
[2328] 09-29 14:30:26:326: Opening line in owner mode
[2328] 09-29 14:30:26:326: PortOpen: successfully opened PPPoE6-0
[2328] 09-29 14:30:27:688: DeviceListen: Changing State for VPN5-127 from 1
-> 2
[2328] 09-29 14:30:27:688: DeviceListen: Changing Listen State for VPN5-127
from 0 -> 2
[1576] 09-29 14:41:19:092: RasTapicallback: msg=23 , param1=0l ,
param2=66013l
[1576] 09-29 14:41:19:092: RasTapicallback: msg=2 , param1=2l , param2=0l
[1576] 09-29 14:41:19:092: RasTapicallback: linecallstate=0x2
[1576] 09-29 14:41:19:092: DwProcessOfferEvent: hcall=0x101dd
[1576] 09-29 14:41:19:092: DwProcessOfferEvent: Couldn't find a listening
port. Dropping call 0x101dd
[1576] 09-29 14:41:19:092: DwProcessOfferEvent 0x80004005
[1576] 09-29 14:41:19:092: DwProcessOfferEvent failed. 0x80004005
[1576] 09-29 14:41:19:092: RasTapicallback: msg=2 , param1=16384l ,
param2=0l
[1576] 09-29 14:41:19:092: RasTapicallback: linecallstate=0x4000
[1576] 09-29 14:41:19:092: RasTapiCallback: FindPortByCallHandle, hcall =
0x101dd failed
[1576] 09-29 14:41:19:092: RasTapicallback: msg=2 , param1=1l , param2=0l
[1576] 09-29 14:41:19:092: RasTapicallback: linecallstate=0x1
[1576] 09-29 14:41:19:092: RasTapiCallback: FindPortByCallHandle, hcall =
0x101dd failed
[1576] 09-29 14:41:19:092: RasTapicallback: msg=12 , param1=65996l ,
param2=0l
[1576] 09-29 14:41:19:092: LINE_REPLY. param1=0x101cc
[1576] 09-29 14:41:19:092: PortByRequestId found
[1576] 09-29 14:41:19:092: RasTapiCallback: LINE_REPLY Deallocatingcall.
hcall = 0x101dd
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top