I could log into the VPN on my server remotely...but I didn't have access to my network or anything else.
I put that project on the back burner until tonight, when I found out my ObiHai110 was having issues and I was going to remotely admin it...over the VPN...
Very long story with much rebooting and Googling/OpenVPN forums reading...
I was missing a command on my server, the command that tells the OpenVPN software to route my home network traffic actually to the home network. For example, the 192.168.x.x number for a networked security cam should be routed to the home network...and to make networking easier, I have my home non routeable IP address to a hopefully offbeat number...
Anywho, because I am not home, I can't edit the server settings, but I can edit the client. So drumroll please...
...the missing line was
route 192.168.x.0 255.255.255.0
(where x is in the home network IP address...normally they default to "1" as in 'route 192.168.1.0 255.255.255.0' your mileage may vary)
I also have the line '--script-security 2', but I am not sure it is necessary for adding that command.
Now the correct way to do this would to have a 'push' command on the server, so as the client is logging in, this is automatically set (in case you change the numbers on the server at some point)
But this will work for me. I can access all my shared drives, and networked devices now.
As a side note, for some reason Win7 removed the popup bubble tool tips from the taskbar icons...the unintended consequences of that caused the OpenVPN context menu (right click on taskbar icon) to not pop up...that headache took a couple of hours by itself.
the registry setting that cause that is...
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"EnableBalloonTips"=dword:00000000
I simply deleted the setting, but apparently you can set it to "2".
Good luck!
Posts
No comments:
Post a Comment