Mac OSX VPN no longer working after installing Parallels 5 Trial version

HenningG

Bit poster
Hello,

I had a VPN connection (PPTP) configured and working from System Preferences/Network.
Once i installed P5 the VPN no longer works. I can connect to the remote network via the VPN without problem, however I cannot see/connect to any of the systems on the remote network via ssh/browser/etc.

I have found several posts about similar issues but none of them resolved my problem.

Thanks,
hgg
 
Last edited:
So far the only "solution" i have found is to completely remove parallels. Now my VPN works again.
Not exactly what I am looking for though.
 
So far the only "solution" i have found is to completely remove parallels. Now my VPN works again.
Not exactly what I am looking for though.

May be I'll be able to help:

It is not necessary to install Parallels Desktop to do this test.

please establish a VPN-connection, start the /Application/Utilities/Terminal and execute in it command
"ifconfig -a" (without quotes) and post me an output via private message
 
So far the only "solution" i have found is to completely remove parallels. Now my VPN works again.
Not exactly what I am looking for though.

I've received the message with ifconfig outputs.. unfortunately, so far I cannot say what the problem is.

There is a workaround that should work without uninstalling the Parallels: execute in /Application/Utilities/Terminal next two commands:
sudo ifconfig vnic0 down
sudo ifconfig vnic1 down

this should help and should not break anything. Unfortunately, it will work only until next reboot of Mac OS (then commands need to be executed again)
 
Elric,

Thanks for the follow up.

1. when you say it does not break anything...why are these adapters there in the first place? Doesn't PD5 need these for networking? Eventually I need to be able to have internet access as well as VPN functionality on the host os (OS X) as well as the guest OS' WindowsXP and Ubuntu. Will this work?

2. I guess I could make a script to down these two adapters at boot time. Would be really annoying otherwise. I pretty much use the VPN every day all day.

Thanks
HGG
 
Last edited:
Elric,

Thanks for the follow up.

1. when you say it does not break anything...why are these adapters there in the first place?
The only functionality that will not work after such commands, is connecting from Mac to Win using TCP-protocol. I.e. if for example you have Web-Server running in VM, it will not work. But there are not so many customers doing anything like this.[/QUOTE]

2. I guess I could make a script to down these two adapters at boot time. Would be really annoying otherwise. I pretty much use the VPN every day all day.
Yes, if the commands help, then startup script is ok
 
Is there already a solution for this problem? I'm working in OSX Lion and have a Windows 7 VM in Parallels 7. In OSX I can make connection using vpn to my work place but i can't connect to machines that have 10.0.1.X range. When i make a VPN connection in Windows (using parallels) it will work and i can connect the 10.0.1.X machines!

If i doe sudo ifconfig vnic0 down and sudo ifconfig vnic1 down it works!
Is there a way to do this without having a script for it?

plz Help!
 
Is there already a solution for this problem? I'm working in OSX Lion and have a Windows 7 VM in Parallels 7. In OSX I can make connection using vpn to my work place but i can't connect to machines that have 10.0.1.X range. When i make a VPN connection in Windows (using parallels) it will work and i can connect the 10.0.1.X machines!

If i doe sudo ifconfig vnic0 down and sudo ifconfig vnic1 down it works!
Is there a way to do this without having a script for it?

plz Help!

Hi

Parallels Shared/HostOnly networks uses subnets 10.211.55.0/255.255.255.0, 10.37.129.0/255.255.255.0 by default, but it is tunable

So, if this conflicts with VPN-routes, do the next:

From the menu Parallels Desktop -> Preferences -> Advanced -> Change Network Settings change settings for Shared/HostOnly networks to be
192.168.55.0/255.255.255.0, 192.168.129.0/255.255.255.0
 
yepp changing that 10.x.x.x to 192.168.x.x works! :D thanks hehe finally...this problem was a big NO-BUY and found this thread and solved the issue. :) So a BIG-YES to buy the license hehehe

One thing to note was with PPTP and a class A 10.x.x.x network, apparently OSX treat anything that is on the 10.x.x.x as a classful network instead of just subnetted network. My Private VPN network was on 10.10.x.x/16, the output of the netstat -anr when I connected successfully is as followed: (note the 10 only line the first line)

10 ppp0 USc 5 12 ppp0
10.10.1.10 ppp0 UHWIi 25 120 ppp0
10.10.1.93 ppp0 UHWIi 24 2026 ppp0
10.10.2.45 10.10.2.46 UH 1 0 ppp0

In Windows, the private network will only have that route statement of 10.10.0.0/16 instead of the 10.0.0.0/8 (like how OSX is doing it)
 
Back
Top