I see a few comments about this on the forums so did research to get attention on this problem. See below for full details.
I have a Mitel 6.0 (commercial) box running, as well as a Mitel 5.6 commercial and an SME 6.0-01.
Both Mitel boxes allow fast and error-free PPTP Session establishment. The SME 6.0.01 server however gets half way, stops for a breather and then tears down the call with the fabled MS Error 619.
Each server is configured identically for RAS (but Mitel’s commercial version 6.0 has some IPSec options, (added as part of their commercial package called 6040) that SME Server doesn’t have.
I tested using an XP Pro (all patches on and all RAS Services started) laptop and with winxplogon.reg applied. I made a PPTP VPN call to each box in turn, using the default configs for PPTP VPN setup on my XP machine. I tested for connection, verification of login and registration and finally authentication on each server in sequence, looking for difference in behaviour. Only the SME 6.0.01 failed. It stopped at the verification of login stage, failing to progress to registration or authentication.
Looking at the SME 6.0.01 box Log Files via server-manager, I have extracted the following relating to when an error 619 happens on a bad session:
Mar 30 16:04:26 major pptpd[9214]: MGR: Launching /usr/sbin/pptpctrl to handle client
Mar 30 16:04:26 major pptpd[9214]: CTRL: local address = 192.168.0.77
Mar 30 16:04:26 major pptpd[9214]: CTRL: remote address = 192.168.0.250
Mar 30 16:04:26 major pptpd[9214]: CTRL: pppd speed = 460800
Mar 30 16:04:26 major pptpd[9214]: CTRL: pppd options file = /etc/ppp/options.pptpd
Mar 30 16:04:26 major pptpd[9214]: CTRL: Client 217.42.122.5 control connection started
Mar 30 16:04:26 major pptpd[9214]: CTRL: Received PPTP Control Message (type: 1)
Mar 30 16:04:26 major pptpd[9214]: CTRL: Made a START CTRL CONN RPLY packet
Mar 30 16:04:26 major pptpd[9214]: CTRL: I wrote 156 bytes to the client.
Mar 30 16:04:26 major pptpd[9214]: CTRL: Sent packet to client
Mar 30 16:04:26 major pptpd[9214]: CTRL: Received PPTP Control Message (type: 7)
Mar 30 16:04:26 major pptpd[9214]: CTRL: Set parameters to 1525 maxbps, 64 window size
Mar 30 16:04:26 major pptpd[9214]: CTRL: Made a OUT CALL RPLY packet
Mar 30 16:04:26 major pptpd[9214]: CTRL: Starting call (launching pppd, opening GRE)
Mar 30 16:04:26 major pptpd[9214]: CTRL: pty_fd = 5
Mar 30 16:04:26 major pptpd[9214]: CTRL: tty_fd = 6
Mar 30 16:04:26 major pptpd[9214]: CTRL: I wrote 32 bytes to the client.
Mar 30 16:04:26 major pptpd[9214]: CTRL: Sent packet to client
Mar 30 16:04:26 major pptpd[9215]: CTRL (PPPD Launcher): Connection speed = 460800
Mar 30 16:04:26 major pptpd[9215]: CTRL (PPPD Launcher): local address = 192.168.0.77
Mar 30 16:04:26 major pptpd[9215]: CTRL (PPPD Launcher): remote address = 192.168.0.250
Mar 30 16:04:26 major pppd[9215]: pppd 2.4.2b1 started by root, uid 0
Mar 30 16:04:26 major pppd[9215]: Starting negotiation on /dev/pts/0
Mar 30 16:04:26 major pptpd[9214]: CTRL: Received PPTP Control Message (type: 15)
Mar 30 16:04:26 major pptpd[9214]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Mar 30 16:04:28 major pptpd[9214]: GRE: Discarding for incorrect call
Mar 30 16:04:55 major last message repeated 7 times
Mar 30 16:04:56 major pppd[9215]: LCP: timeout sending Config-Requests
Mar 30 16:04:56 major pppd[9215]: Connection terminated.
Mar 30 16:04:56 major pppd[9215]: Exit.
Mar 30 16:04:56 major pptpd[9214]: GRE: read(fd=5,buffer=804d940,len=8196) from PTY failed: status = -1 error = Input/output error
Mar 30 16:04:56 major pptpd[9214]: CTRL: PTY read or GRE write failed (pty,gre)=(5,6)
Mar 30 16:04:56 major pptpd[9214]: CTRL: Client 217.42.122.5 control connection finished
Mar 30 16:04:56 major pptpd[9214]: CTRL: Exiting now
Mar 30 16:04:56 major pptpd[3068]: MGR: Reaped child 9214
Is this a bug? Many people have seen it...
Chris