Vault 2014 Remote Connection Problem.

[dnlrcc]

I've been using autodesk vault 2014 basic on windows 7 and i've been trying to set up a remote connection on my server. The local server works perfectly but when i try to set up a remote connection to the vault it never works. I've followed the "Configuring a remote vault connection using FQDN" part of this tutorial "http://download.autodesk.com/us/vault/2014/2014_Advanced_Config_Guide-2014.pdf" and there are some things that aren't clear to me. In the 4th step it says that after i've right clicked on the website i should select "properties" but i can't find this option. So i managed to find the configuration page by clicking on "binding" right after selecting the website. When i'm on the "binding" dialog box i see three option i can edit: ip, port and hostname but i don't know how to configure them ( i guess that i'd have to register to no-ip to get a fqdn and then edit those options). At the end of the day i'd like to have my vault working on my local lan with two pc (which already does) and another client from another city connected to my vault through a remote connection. So how can i configure it? Thanks in advance.

[JeffPaquette6500]

If you are on a local LAN, you shouldn't need to configure FQDN. Only use the FQDN if you are connecting to Vault over the internet. If you are having a connection problem while on your LAN, note the error message, and search this blog:

http://crackingthevault.typepad.com/crackingthevault/

Otherwise, Step 4 should say, Right-click the Default Web Site, Manage Web Site, Advanced Settings.

[JeffPaquette6500]

I just realized those instructions were written for a prior version of IIS. Please try these instructions:

To configure the Vault Server to allow remote connections over the internet using a Fully Qualified Domain Name (FQDN):

1. Create a DNS "A" or host record for your current FQDN with your ISP.
2. Install Autodesk Vault Server on your server and verify that it works properly.
3. On your server, open the Internet Information Services Manager and expand the Websites folder.
4. Select website that contains the AutodeskDM virtual directory (typically “Default Web Site”), and click Bindings.
5. In the Site Bindings, select the IP address, enter the Host Name,and enter the Port #.
6. Click OK and Close to exit Site Bindings.

[dnlrcc]

I still have some questions for you. My server is running windows 7 and i read on the internet that it's impossible to establish remote connections on iis on win 7 (http://technet.microsoft.com/en-us/library/cc731771(v=ws.10).aspx). Are you sure it can be done (access to my vault remotely) with my server running windows 7???

I have another question. In the "binding" box of iis i already have an option set (http for protocol, * for ip, 80 for port and blank hostname).

I'm guessing this one is for the local use of the vault (which, as i have already wrote, works perfectly) and i was wondering: in order to "add" a remote connection to the local one do i have to edit the one already existing or do i have to create a new one (in order to keep both the local and the remote connection working)?

One last thing, let's just say i buy a domain from godaddy.com. To get a fqdn i'd have to create a host like this "myservername.domain.com" and then point it to my server ip address right??? The problem is that my server has a dynamic ip and in order to get a static one i should create an account at no-ip to get a static host and than point my fqdn at this host right??? Or do i need to get a "real" static ip in oder to use it with the fqdn??

And finally, what ip should i set on the binding section of iis for the remote connection?? My server ip, the fqdn ip or the local ip (example 192.168.0.1) from which i access my server in local?

Thanks

[JeffPaquette6500]

That article is written for Windows Server. I believe that topic is different than what you are trying to accomplish.

Honestly I have not personally setup a Vault connection via FQDN. Hopefully someone else in the community can contribute here.

As for the IIS bindings, you would add a binding. Keep the current blank with port 80 for the local connection.

Another thing to consider is if your ISP allows you to run a server. Some ISPs do not allow it.