[isalist] Error establishing a VPN to the ISA server

  • From: "Glenn P. JOHNSTON" <glenn.johnston@xxxxxxxxxxx>
  • To: <isalist@xxxxxxxxxxxxx>
  • Date: Wed, 28 Jun 2006 12:13:37 +1000

http://www.ISAserver.org
-------------------------------------------------------

Hi,
 
Maybe, maybe not directly and ISA question, and I've posted this in an SBS 
forum as well, but you people are pretty bright & I thought you might have some 
worth while input on this.
 
One of my clients has an issue with VPN tunnel. This has been inplace since 
Sunday afternoon, but they only rang me this morning.
 
One of their directors is at a week long conference, and the Hotel where he is 
staying, has provides an in room broadband service. 
The BroadBand in the hotel is using a 192.168.110.0/24 address range, the 
internal address of the clients network at the office is also a 
192.168.110.0/24 range.
 
The VPN tunnel  establishes fine, and the VPN connector on his notebook get an 
address, of course, in the 192.168.110.100 to 192.168.110.199 range of the DHCP 
server on the SBS server.
 
Once the tunnel is established, he can acess nothing on the SBS. This is to be 
expected as the address ranges are the same, does anyone have any bright idea's 
on how to get around this. The Director is yelling and screaming about not 
being able to get his e-mail.
 
Unfortunately he is out out direct reach in another state, and has very little 
tolerance for such problems.
 
Regards
Glenn
------------------------------------------------------
List Archives: //www.freelists.org/archives/isalist/
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server Articles and Tutorials: http://www.isaserver.org/articles_tutorials/
ISA Server Blogs: http://blogs.isaserver.org/
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
To unsubscribe visit http://www.isaserver.org/pages/isalist.asp
Report abuse to listadmin@xxxxxxxxxxxxx

Other related posts: