Can't connect to servers within network. Routing issue?

[badlydrawntoy]

Hi. We;ve just installed Open VPN at work for use with the Viscosity client. Two of our staff can successfully connect, two if us can't.

We are all using the same connection settings (export/import)
Connection is established. IP addresses are allocated from our DHP server (router)
It is possible to browse the internet when connected
There is network traffic in and out
I can ping some of the local network machines in the network by both IP address and machine name (machinename.local)
I've followed the trouble shooting guide. DNS is fine. Don;t quite understand hoe to determine if routing is correct
I can see the local network machines in the Finder app

But I can't connect to them.

I've tried two machines from home. Same issue.

Could this be a routing issue? From the troubleshooting guide, I'm not sure what to look for. This is what I see:

Internet:
Destination Gateway Flags Refs Use Netif Expire
default bebox.config UGSc 46 0 en1
default 192.168.1.1 UGScI 0 0 tap0
127 stock.esl.local UCS 0 0 lo0
stock.esl.local stock.esl.local UH 4 3639 lo0
169.254 link#5 UCS 1 0 en1
169.254.1.0 link#5 UHRLW 1 329 en1 4
192.168.1 link#5 UCS 7 0 en1
192.168.1 link#8 UCSI 4 0 tap0
192.168.1.15 0:1b:63:24:1b:5c UHLWI 0 0 tap0 543
192.168.1.21 0:11:24:9:b4:6a UHLWI 0 0 tap0 542
192.168.1.32 stock.esl.local UHS 0 0 lo0

bebox.config is my own broadband connection
192.168.1.1. is the office router

Any help would be appreciated

thanks

[James]

Hi badlydrawntoy,

How do you get on if you manually increase the time before routes are added? You can do this like so:

1. Edit your connection in Viscosity
2. Click on the Advanced tab
3. Add the command "route-delay 30" on a new line in the commands section. You can replace 30 with different a different time to wait (in seconds) if you wish.
4. Click Save and try connecting.

If the server is pushing out the default route, I'd also recommend using the "def1" flag at the end of the pushed "redirect-gateway" command.

Cheers,
James

[badlydrawntoy]

Hi James

Apologies for not replying sooner. Didn't get any notification there had been a response to this thread.

I've tried upping the route-delay. No joy. I took a look at the logs on the VPN server. It shows successful connection and traffic on and out.

Extra commands are as follows:

sndbuf 100000
dev-type tap
setenv SERVER_POLL_TIMEOUT 4
key-direction 1
reneg-sec 604800
rcvbuf 100000
auth-retry nointeract
route-delay 30


How do I know if the server is pushing out the default route? This is what the log shows:

Sun Aug 15 19:43:51 2010: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sun Aug 15 19:43:51 2010: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Sun Aug 15 19:43:51 2010: LZO compression initialized
Sun Aug 15 19:43:53 2010: UDPv4 link local: [undef]
Sun Aug 15 19:43:53 2010: UDPv4 link remote: 87.194.144.59:1194
Sun Aug 15 19:43:53 2010: [OpenVPN_Server] Peer Connection Initiated with 87.194.144.59:1194
Sun Aug 15 19:43:55 2010: Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:4: dhcp-pre-release (2.1.1)
Sun Aug 15 19:43:55 2010: Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:5: dhcp-renew (2.1.1)
Sun Aug 15 19:43:55 2010: Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:6: dhcp-release (2.1.1)
Sun Aug 15 19:43:55 2010: TUN/TAP device /dev/tap0 opened
Sun Aug 15 19:43:55 2010: /Applications/Viscosity.app/Contents/Resources/dnsup.py tap0 1500 1574 init
Sun Aug 15 19:44:01 2010: Initialization Sequence Completed

[James]

It appears you are connecting to an OpenVPN Access Server - try using the latest beta version of Viscosity (1.2b4 at the time of writing) which has greatly improved OpenVPN-AS support. You can download it at:
viewtopic.php?p=134#p134

If that still doesn't work, try the following:

1. Edit your connection in Viscosity
2. Click on the Networking tab
3. Tick the "Send all traffic over VPN connection" option
4. Enter "192.168.1.1" as the Default Gateway
5. Click Save and try connecting again.

Cheers,
James