Symantec Altiris - Local and public IP
Hi,
There is a single Symantec Altiris server serving a single location office. Workstations connect to the Altiris server on the LAN using a local IP.
They would like it configured such that workstations connected to the LAN continue to connect on the local IP, but that when employees are travelling; their laptop workstations will connect to the Altiris server on our of their public IP's.
My question is:
How can we configure the Altiris Clients to look at the local Altiris Server IP first, and when that can't be found (i.e. when out of the office) it tries to connect to the Altiris server on the public IP? (hopefully this change can be pushed out by the Altiris server, rather than manually making a change on every workstation)
I understand it will mean making changes at firewall level to route the traffic accordingly, and that is fine. My question is purely about the Alitiris client configuration.
Thanks,
There is a single Symantec Altiris server serving a single location office. Workstations connect to the Altiris server on the LAN using a local IP.
They would like it configured such that workstations connected to the LAN continue to connect on the local IP, but that when employees are travelling; their laptop workstations will connect to the Altiris server on our of their public IP's.
My question is:
How can we configure the Altiris Clients to look at the local Altiris Server IP first, and when that can't be found (i.e. when out of the office) it tries to connect to the Altiris server on the public IP? (hopefully this change can be pushed out by the Altiris server, rather than manually making a change on every workstation)
I understand it will mean making changes at firewall level to route the traffic accordingly, and that is fine. My question is purely about the Alitiris client configuration.
Thanks,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Rigan's way would not necessarily work for the reasons I posted above. Is the external FQDN actually accessible whilst internal? If not, clients will fail in 50% of connection attempts.
And even if it is accessible thus - you would have clients going outside of your network onto the public FQDN to communicate with a server that is on the LAN even when the PCs are in the LAN environment.
Use an alias and your clients will only resolve the internal address when in the LAN.
And even if it is accessible thus - you would have clients going outside of your network onto the public FQDN to communicate with a server that is on the LAN even when the PCs are in the LAN environment.
Use an alias and your clients will only resolve the internal address when in the LAN.
Sorry but I believe you've given points for a technically erroneous answer.
An alias is a better way forwards:
http://support.microsoft.com/kb/168321
In this case, it'd be a name that matched an externally registered FQDN.