VPN connection to ISA Server
 

I installed Linux (Fedora 7) on my home computer as second OS (multiboot). Now I want to connect to our work ISA Server 2004 (or 2006, I'm not sure) from Linux. Server accepts PPTP-connections. I can connect from Windows without any problems. So, I ask our admin to give portion of ISA-log to troubleshoot my problem but cannot find the solution. Can anybody help me? I'll be glad to any suggestions.

There is archive with files that can help:
alisher.city.tomsk.net/tmp/linuxvpn.zip

• ipconfig_novpn.txt - result of ipconfig /all from Windows without VPN-connection established
• ipconfig_vpn.txt - result of ipconfig /all from Windows with VPN-connection established
• route_novpn.txt - result of route print from Windows without VPN-connection established
• route_vpn.txt - result of route print from Windows with VPN-connection established
• isalog.txt - portion of ISA-log
• vpn_linux_session.txt - portion of /var/log/messages with entries related to one PPTP-session
• etc_ppp.zip - configuration files from /etc/ppp (without chap-secrets, of course)

hi alish,

first - what pptp client did you use?

you might take a look a these links :
http://pptpclient.sourceforge.net/#tryit
http://www.poptop.org/

the fedora 7 default vpn client (i've forgot what it was) is using ipsec not basic windows pptp one - so you should ask your administrator the vpn setup config.

HTH.

I use pptp-1.7.1-3 from the pptpclient.sourceforge.net.

Yep, I tried almost all from acceptable things from that site.

Poptop is the server, not client. How it can help me?

I'm not sure our admin will change anything. :(
What's the default VPN-client in Fedora? Did you mean OpenVPN? Yes, I know it does not support PPTP. Therefore, I can't use it now.

Any ideas (except asking admin to add L2TP/IPSec in ISA)?

no - i mean take a look at those ppp configuration on that website,
and see how it helps you to establish the pptp connection.

not asking to add l2tp/ipsec - but see his configuration, what authentication he use etc..

cheers.

fixed
 

I've fixed the trouble. The problem was at my side (not on the server) and related with routing. It's important to specify local interface when creating direct route to the peer. So, the answer was: