I am testing the latest demo version 2.01 on my network. I have installed and tested the server and client parts inside my network. They are working correctly. I am now trying to access Vault from outside my network.
Would it be possible to change the IIS server where Vault resides to a port other than port 80 and forward it from the NAT router? I just wanted to ask before spending a lot of time on it.
Thanks in advance,
Hector
Multiple IIS servers behind NAT
Moderator: SourceGear
The Vault server doesn't care a bit what port it runs on, so as long as IIS is properly configured to run it, it should work. You'll need to append the port to the server string when connecting from the client (like "server.foo.com:8080").
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
-
- Posts: 3
- Joined: Thu Apr 08, 2004 8:52 am
Thanks!
Yes, I knew about IIS and ports. I was wondering about at the actual router.
I got it working in any case. My router does not let me assign different ports on the inside interface. It has to be the same port number on the WAN and LAN interfaces. So I changed the port to 81 on IIS, then set a port on the router config screen. Now the Vault client is connecting.
My firewall appliance is a Netgear FVS318.
- Hector
Yes, I knew about IIS and ports. I was wondering about at the actual router.
I got it working in any case. My router does not let me assign different ports on the inside interface. It has to be the same port number on the WAN and LAN interfaces. So I changed the port to 81 on IIS, then set a port on the router config screen. Now the Vault client is connecting.
My firewall appliance is a Netgear FVS318.
- Hector