Server don't answer...

[pparadis]

First, excuse my english, it is not my first language....

Main location :
NT Domain with several working station. A dedicate pc with Wingate as Proxy and Firewall and VPN connection. Adress of the server 129.11.10.2

Location 2.
Workgroup and high speed internet connection. VPN server (192.168.3.1)on a dedicated server. Few workstations(192.168.3.2).

Both VPN server can ping each other and on both IP adress (internal-external)

From main location, workstation on the domain. I can ping a workstation on location 2 but can't ping the VPN server. On my workstation, I got the VPN server as default gateway.
Tracert give me 129.11.10.2 and 192.168.3.2 So, it prove me my routing is ok.

Samething from location 2. From a workstation on location 2, I can ping a workstation on main location and trace route. But can't do it from location vpn server.

For a reason I don't get, the vpnserver is "invisible". I really need this machine available from the main location. Will need remote desktop and backup program to run from distance.

[Pascal]

This rather lengthy post has some interesting details about NT domains and the visibility of the server. Organekd did a lot of useful research and right at the end is a good link to a Microsoft Knowledge Base article which might be of assistance.

It's a long read, but describes a problem similar to yours.

[pparadis]

Nope, this is not solving my probleme.

Lot of workaround, here is the current situation.

Location 2 server can ping the main location. Main can't ping. Workstations on location 2 can access everything on main location. Main location can access everything except the server on location 2.

Location 2 server and workstation are now log on NT domain and the PDC is on main location.

[pparadis]

As complement of information, Server 2 can be seen on the Network neighborhood but can't be access. It can only be access from Server 1 and from device on remote location.

Server 2 can access all devices of main location.

Server can't be access from the internal IP adress (192.168.3.1) but can be access from external.

[Pascal]

Location 2 server can ping the main location.

That is good. I assume it is pinging the internal IP of the main location's server? If that is the case, it's good because we know the tunnel is established.

Are you running any third party firewalls on that main location?

[pparadis]

Yep the tunnel is up and running.

I got Wingate 6.04 acting as proxy and firewall on location 1. I try to desactivate the firewall service and still the same.

I can access the server 2 from the internet address but not from 192.168.3.1

[Pascal]

WinGate / WinGate VPN's firewall won't interfere with the VPN at all. So hang on, you can access the remote server from your local network by typing \\<external ip> into a run cmd. But not when using \\192.168.3.1 from the local side?

[pparadis]

Correct. I can access the remote pc on 69.157.205.xxx but not at 192.168.3.1

If I ping server_name it try to ping at 192.168.3.1 so I enter the IP adress 69.xx.xx.xx in my local DNS and I can access the remote server.

It work fine like that but only in my testing. I have a fix IP here on test but when everything will work, I register VPN server and move the server to a location where I have a dynamic IP :(

[Pascal]

Just calling in some reinforcements here - not too sure what else to suggest as it seems as if the tunnel is up and running.

[genie]

Do you have any other firewall products installed on your VPN server?

[jamesc]

Recapping Facts pparadis has stated for readibility

1st Post:
Both VPN server can ping each other and on both IP adress (internal-external)

From the "Main Location" on a client machine, he can ping "Location 2" clients, But not the "Location 2" VPN Server.

From the "Location 2" on a client machine, he can ping "Main Location" clients, But not the "Main Location" VPN Server.

2nd Post:
Location 2 server can ping the main location. Main can't ping