Many of our remote users connect to our corporate network from Hotels, airports, and etc. through our ISA server running Routing and Remote Access. The problem is our private network uses IP subnet 192.168.1.XXX which is such
a standard now that many hotels, airline lounges, and hotspots are using the same. The remote users connect and authenticate fine but cannot reach any corporate resources such as Exchange server or internal websites.
The only solution I know is to change the local subnet addressing but I don’t know what the effect will be on DNS and Active Directory. There are approximately 50 nodes on the corporate network and I should also mention
that in addition to the corporate site I have 3 remote sites, all part of the same Domain and connected via VPN using Cisco PIX. They are different subnets.
I would appreciate any advice or suggestions as to how to approach this.
a standard now that many hotels, airline lounges, and hotspots are using the same. The remote users connect and authenticate fine but cannot reach any corporate resources such as Exchange server or internal websites.
The only solution I know is to change the local subnet addressing but I don’t know what the effect will be on DNS and Active Directory. There are approximately 50 nodes on the corporate network and I should also mention
that in addition to the corporate site I have 3 remote sites, all part of the same Domain and connected via VPN using Cisco PIX. They are different subnets.
I would appreciate any advice or suggestions as to how to approach this.