Bit of a long running one at work this one...
When staff connect remotely to the company network they use the Cisco VPN client. This works just spiffy as long as their network share and internal shortcuts point to IP's rather than FQDN's.
I could just about live with this up until now but some staff want to use Outlook 2007 for their mail rather than OWA and it automatically converts the exchange server IP to a FQDN in the setup process.
Is this normal for Cisco VPN software or have I set it up wrong/missed a trick?
Is there a way to configure the machines to use the work DNS servers when they're connected via vpn?
When staff connect remotely to the company network they use the Cisco VPN client. This works just spiffy as long as their network share and internal shortcuts point to IP's rather than FQDN's.
I could just about live with this up until now but some staff want to use Outlook 2007 for their mail rather than OWA and it automatically converts the exchange server IP to a FQDN in the setup process.
Is this normal for Cisco VPN software or have I set it up wrong/missed a trick?
Is there a way to configure the machines to use the work DNS servers when they're connected via vpn?