S
Scott Balmos
Hi all,
I solved the earlier issue I was having, with not being able to share
directories. It's because the server only knows about its 192.168.x address
when dealing with shares (I have no idea why... if someone could explain that
one, I'd love it). So, after I connect to the server via the VPN, and get a
10.x address, I need to add a routing table entry to force traffic for
192.168.254.254 over the 10.x VPN address.
My question is if there is anything *client side* I can set to run some type
of post-connect batch script, which can automatically add this static route
entry. Explaining to a customer how to read the routing table to get the
assigned 10.x VPN IP, and then how to type in the routing table add entry
would be painful at best.
Any suggestions? Thanks!
--Scott
I solved the earlier issue I was having, with not being able to share
directories. It's because the server only knows about its 192.168.x address
when dealing with shares (I have no idea why... if someone could explain that
one, I'd love it). So, after I connect to the server via the VPN, and get a
10.x address, I need to add a routing table entry to force traffic for
192.168.254.254 over the 10.x VPN address.
My question is if there is anything *client side* I can set to run some type
of post-connect batch script, which can automatically add this static route
entry. Explaining to a customer how to read the routing table to get the
assigned 10.x VPN IP, and then how to type in the routing table add entry
would be painful at best.
Any suggestions? Thanks!
--Scott