3.1 Why Workstation Name Not Discovered with VPN Connection
Problem
Profiles linked at the workstation level are not working. We're on a LAN but have a VPN connection. Is there a reason this doesn't work and is there a workaround?
Solution
In order to use some RecTrac 3.1 features that require a 'Workstation name' (such as Profiles linked at the workstation level), the server(s) needs to be able to perform a successful Reverse DNS Lookup by client IP address to discover the workstation name. Without this, profiles may not be recognized at the workstation level.
Apparently by default, Reverse DNS is not allowed on some VPN connections so the workstation is not recognized and thus profiles are not known. During the installation and configuration process, VSI staff should operate on the assumption that clients connecting through a VPN connection will need manual configuration at the local site to accommodate Reverse DNS Lookup.
This is similar to a WAN connection. For WAN, you currently have to link a VIC profile at the default level and when a user tries to connect to 3.1 it has VIC send in the workstation name and then once logged in and the workstation name is set, the profiles on the workstation level now work (including VIC).
The immediate workaround is to link a VIC profile at the default level.
Also put in a request to the customer's IT department to find a way to allow the Reverse DNS Lookup to work with a VPN connection.