Greetings Everyone .......
I have a question and I've done some reading on the Wiki, but I'd like to confirm that what I think is correct, is.
A quick rundown of my entire network (main and remote sites.)
Main site UT 9.3.1 Box: 172.16.4.2 / 22 <-- Inside Interface
Remote site UT 9.3.1 Box #01: 172.16.1.1 / 24 <-- Inside Interface
Remote site UT 9.3.1 Box #02: 172.16.2.1 / 24 <-- Inside Interface.
When I'm onsite at my main network, I can ping, browse, RDP, and access any device on either remote network.
With a "road" client - When their tunnel is established - they can hit anything at my main network, but not any devices / resources at either of the remote networks.
Then I read this on the Wiki;
I'm using site-to-site and my software clients can only talk to the main server. Why?
If you have both software clients on the road and site-to-site tunnels, the software clients will only be able to see your main site by default. To allow them to transit the tunnel(s) to other sites, simply add the VPN Address Pool to the Exported Hosts and Networks. After this is done, software clients will be able to reach all exported sites.
I also understand that once I have entries in the exported hosts and networks section - that once a client is created and distributed that it will contain those entries so that a client on the road can access resources at both the main network and remote networks.
With that said, here's the confirmation question. If I want a "road client" to access my 172.16.1.0 / 24 remote network would the line in the exported hosts and networks field be;
Name: 172.16.1 Network IP Address 172.16.1.0 Netmask: 255.255.255.0
or, would it be .....
Name: 172.16.1 Network IP Address 172.16.1.1 Netmask: 255.255.255.0
Where 172.16.1.1 is the inside interface of that Remote Site UT 9.3.1. Box
And obviously it has to be enabled ......... :)
I'm going to do some testing from home later today, but any information anyone can give me I would greatly appreciate it ...... as I need to get this resolved by Friday.
Thanks everyone .....
G.
I have a question and I've done some reading on the Wiki, but I'd like to confirm that what I think is correct, is.
A quick rundown of my entire network (main and remote sites.)
Main site UT 9.3.1 Box: 172.16.4.2 / 22 <-- Inside Interface
Remote site UT 9.3.1 Box #01: 172.16.1.1 / 24 <-- Inside Interface
Remote site UT 9.3.1 Box #02: 172.16.2.1 / 24 <-- Inside Interface.
When I'm onsite at my main network, I can ping, browse, RDP, and access any device on either remote network.
With a "road" client - When their tunnel is established - they can hit anything at my main network, but not any devices / resources at either of the remote networks.
Then I read this on the Wiki;
I'm using site-to-site and my software clients can only talk to the main server. Why?
If you have both software clients on the road and site-to-site tunnels, the software clients will only be able to see your main site by default. To allow them to transit the tunnel(s) to other sites, simply add the VPN Address Pool to the Exported Hosts and Networks. After this is done, software clients will be able to reach all exported sites.
I also understand that once I have entries in the exported hosts and networks section - that once a client is created and distributed that it will contain those entries so that a client on the road can access resources at both the main network and remote networks.
With that said, here's the confirmation question. If I want a "road client" to access my 172.16.1.0 / 24 remote network would the line in the exported hosts and networks field be;
Name: 172.16.1 Network IP Address 172.16.1.0 Netmask: 255.255.255.0
or, would it be .....
Name: 172.16.1 Network IP Address 172.16.1.1 Netmask: 255.255.255.0
Where 172.16.1.1 is the inside interface of that Remote Site UT 9.3.1. Box
And obviously it has to be enabled ......... :)
I'm going to do some testing from home later today, but any information anyone can give me I would greatly appreciate it ...... as I need to get this resolved by Friday.
Thanks everyone .....
G.