Topic: Access Server via VPN

[Tony Howden]

Hi All

I am chasing my tail here reading everything about vpn's without seeing anything similar. I may be using the wrong search terms.

I have 5.5u6 configured and can connect via a pptp connection. I can see the network, and the other server behind the sme server. The other box is W2K with an accounting system on it that runs on MS-SQL and uses a variety of IP ports. It does not use any windows authentication.

The problem is that the client software can see the server and the connection tests to the various essential ports are ok. But the client cannot actually run any functions of the accounting software.

Ok, on the surface it would appear to be a client problem, except for the fact that at other locations, using a range of VPN solutions, it works fine with no modifications. It is only when its up against the sme vpn that it fails. When my notebook is connected on the local lan it also works fine. However, from a remote location it fails.

Any clues would be appreciated. Thanks

cheers
Tony

[Tony Howden]

Hi All

Ok, its a dns issue ! For anyone looking for problems with access to an application server behind an e-smith vpn, try this.

I have now discovered that the server side of the application, albeit that it has a tcp/ip base and should simply allow connections via the ip address, it also 'features' an internal setting that holds the machine/host name for the server as a point of reference.

The vpn server (sme 5.5u6) was configured in one dns domain, while the server was in another. The dns resolution based solely on hostname failed as the domain suffix was not in the search options.

So adding the appropriate dns suffix to the windows XP client (tcp-ip properties for the vpn connection ->advanced ->dns-> append suffix) meant that the app server could be found via its hostname and all is well. For sake of completeness, I did try using the FQDN for the server and modified the client app to have that setting but it did not work.

cheers
Tony