VPN permission/authentication?

I'm trying to get non-Windows clients to connect to a Windows 2003 server
VPN setup using PPTP. While my Windows 2000 laptop is able to connect
without any issues, none of the other clients I have tried (Mac OS 10.4 and
OpenBSD command line) have worked. I cannot find any errors in the Windows
logs, so I am not really sure where to look next. However I suspect the
problem is that the non-Windows clients are using some authentication that
the native Windows client does not and fails due to that. Both of my
non-Windows clients time out and eventually come back with a "server does
not respond" type of an error.

My setup is as follows:
* Domain Controller running Windows 2003
* Second windows 2003 server acting as the VPN host with dual NIC's
* The second NIC in the VPN server is attached to a router (to simulate "an
external ie. internet" connection)
* From the second NIC in the router I have a cross-over cable running to the
client system
* The router is running DHCP to provide a valid IP to the clients

In all cases, and platforms, I can ping from the client to both sides of the
router, and the "WAN" NIC of the VPN server. The router is not running any
kind of a firewall or filtering, so there is not an issue of any kind of a
block there - a fact verified by the Win2k client which does make a
successful PPTP connection. I can also monitor the bytes in column in
Routing and RAS manager when the various clients try to connect in and I can
see the numbers going up.

So, what am I missing? What secret magic handshaking do Windows clients
have that neither OS X or the *BSD PPTP setup cannot do? Is there something
on the server that I can turn off to not be so rigid about the clients which
it will accept?

Thanks,
Peter

The answer I think is MSCHAP
You will need to allow CHAP in routing and remote access right click on your
RRAS server and click properties under the security tab press Authentication
methods and check CHAP.

"Peter Bako" wrote:

> I'm trying to get non-Windows clients to connect to a Windows 2003 server
> VPN setup using PPTP. While my Windows 2000 laptop is able to connect
> without any issues, none of the other clients I have tried (Mac OS 10.4 and
> OpenBSD command line) have worked. I cannot find any errors in the Windows
> logs, so I am not really sure where to look next. However I suspect the
> problem is that the non-Windows clients are using some authentication that
> the native Windows client does not and fails due to that. Both of my
> non-Windows clients time out and eventually come back with a "server does
> not respond" type of an error.
>
> My setup is as follows:
> * Domain Controller running Windows 2003
> * Second windows 2003 server acting as the VPN host with dual NIC's
> * The second NIC in the VPN server is attached to a router (to simulate "an
> external ie. internet" connection)
> * From the second NIC in the router I have a cross-over cable running to the
> client system
> * The router is running DHCP to provide a valid IP to the clients
>
> In all cases, and platforms, I can ping from the client to both sides of the
> router, and the "WAN" NIC of the VPN server. The router is not running any
> kind of a firewall or filtering, so there is not an issue of any kind of a
> block there - a fact verified by the Win2k client which does make a
> successful PPTP connection. I can also monitor the bytes in column in
> Routing and RAS manager when the various clients try to connect in and I can
> see the numbers going up.
>
> So, what am I missing? What secret magic handshaking do Windows clients
> have that neither OS X or the *BSD PPTP setup cannot do? Is there something
> on the server that I can turn off to not be so rigid about the clients which
> it will accept?
>
> Thanks,
> Peter
>
>
>