Not necessarily DHCP-based. ISA 2004 gives far more control over VPN sessions than ISA 2000 ever considered. Use the VPN weirdzard to make sure the settings are what you expect them to be. Also check your monitoring tab for any whining ISA might be doing. -----Original Message----- From: Tom Rogers [mailto:trogers@xxxxxxxxxxxxxxxxxx] Sent: Friday, February 17, 2006 6:03 AM To: [ISAserver.org Discussion List] Subject: [isalist] Next Issue with News ISA 2004 SP2 rollout... http://www.ISAserver.org Next up, from inside my office I can MSTSC /console /v:server_name to all my servers EXCEPT the ISA server. From home, when I VPN in, I can only MSTSC /console /v:server_name to my MAIN AD Server, no other servers. For this, I think it is a DHCP issue - I did have my ISA server acting as the AD DHCP server but unauthorized it and authorized the DHCP server on my main AD server. So when I checked my IP address that I was handed out via VPN through the ISA server, I get an IP address of 169.254.30.161 with a subnet of 255.255.255.255 and a gateway of 169.254.30.161. My network at work is 192.168.1.x I guess I should have read the book FULLY before starting the upgrade from ISA 2000, because EVERYTHING was working fine under ISA 2000. Any detailed help would be greatly appreciated. -TRogers ISA 2004 Rookie ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx All mail to and from this domain is GFI-scanned.