J
John Lewis
Having trouble establishing a connection between a W2K SP4
client and a linux PPTP server. Seems the DUN client is cooperating to make
the initial link, but blows up somewhere just before authentication.
Regressing to SP3 fixes things, haven't found anything else that helps.
Tried KB329050 & KB254631 even though the symptoms were not quite the same,
thinking perhaps I wasn't seeing the whole picture, but that didn't help.The
balance of this message is rather lengthy, but provides the details. I
posted a couple days ago to win2000.networking without any bites. Hoping
for better results here . . . .
Everything works fine if I do not use authentication.
Also works if I remove SP4 which leaves the client machine
at W2K SP3. Debug log on the server indicates that the
initial link is negotiated, auth protocols are agreed
upon. The server sends multiple chap challenges, to which
the client responds with an ack in GRE. The client does
not send a chap reply. Ethereal on both machines
indicates that this is an accurate representation.
I enabled logging and made a connection with SP4 (which
failed) then with SP3 (which went well). Can't find any
information about the output in the logs, but I have
noticed the following in comparing the two sets.
The RASMAN.LOG files are similar to the point that
the 'good' log shows 'PppStarted...VPN2-1'. The 'bad' log
has no such line, and there are several lines in that area
that say 'PostReceivePacket - Queueing packet on pcb. VPN2-
1'. The number of these lines corresponds to the number
of chap challenges that were sent by the server. There
are no such lines in the good log.
The first line of the 'bad' PPP.LOG
indicates 'PPPEMSG_Start recvd' at the time the
RASMAN.LOG shows 'ConnectCompleteRequest:', which seems to
be good. There are no further entries until after
the 'PostReceivePacket' lines and a 'WorkerThread:
Disconnect event signaled on port' in the RASMAN.LOG. I
can't get the timing close enough to tell, but it seems
this corresponds to the termination request sent by the
server due to authentication failure.
The next bit of information is posted to PPP.LOG just over
11 minutes later, well after the connection is physcally
closed. Wasn't smart enough to pay attention, but I think
the timing corresponds to a shutdown of Windows. Both the
RASMAN and PPP logs show clean up activities at this
time. The PPP log shows 'PCB not found for port 3' in
this sequence 7 times, which corresponds to the number of
'Queing packet on PCB' entries in the RASMAN.LOG earlier.
Seems to me that RAS is not passing proper parameters to
PPP? Really haven't the first clue. Sorry for the
lengthy post, but was really hoping someone could give me
some clue how to fix this. Any ideas are appreciated.
client and a linux PPTP server. Seems the DUN client is cooperating to make
the initial link, but blows up somewhere just before authentication.
Regressing to SP3 fixes things, haven't found anything else that helps.
Tried KB329050 & KB254631 even though the symptoms were not quite the same,
thinking perhaps I wasn't seeing the whole picture, but that didn't help.The
balance of this message is rather lengthy, but provides the details. I
posted a couple days ago to win2000.networking without any bites. Hoping
for better results here . . . .
Everything works fine if I do not use authentication.
Also works if I remove SP4 which leaves the client machine
at W2K SP3. Debug log on the server indicates that the
initial link is negotiated, auth protocols are agreed
upon. The server sends multiple chap challenges, to which
the client responds with an ack in GRE. The client does
not send a chap reply. Ethereal on both machines
indicates that this is an accurate representation.
I enabled logging and made a connection with SP4 (which
failed) then with SP3 (which went well). Can't find any
information about the output in the logs, but I have
noticed the following in comparing the two sets.
The RASMAN.LOG files are similar to the point that
the 'good' log shows 'PppStarted...VPN2-1'. The 'bad' log
has no such line, and there are several lines in that area
that say 'PostReceivePacket - Queueing packet on pcb. VPN2-
1'. The number of these lines corresponds to the number
of chap challenges that were sent by the server. There
are no such lines in the good log.
The first line of the 'bad' PPP.LOG
indicates 'PPPEMSG_Start recvd' at the time the
RASMAN.LOG shows 'ConnectCompleteRequest:', which seems to
be good. There are no further entries until after
the 'PostReceivePacket' lines and a 'WorkerThread:
Disconnect event signaled on port' in the RASMAN.LOG. I
can't get the timing close enough to tell, but it seems
this corresponds to the termination request sent by the
server due to authentication failure.
The next bit of information is posted to PPP.LOG just over
11 minutes later, well after the connection is physcally
closed. Wasn't smart enough to pay attention, but I think
the timing corresponds to a shutdown of Windows. Both the
RASMAN and PPP logs show clean up activities at this
time. The PPP log shows 'PCB not found for port 3' in
this sequence 7 times, which corresponds to the number of
'Queing packet on PCB' entries in the RASMAN.LOG earlier.
Seems to me that RAS is not passing proper parameters to
PPP? Really haven't the first clue. Sorry for the
lengthy post, but was really hoping someone could give me
some clue how to fix this. Any ideas are appreciated.