Thanks, Tom. Yah, the AutoConfiguration IP address should have raised some flags, but I thought ISA was preventing a complete DHCP IP acquisition. I checked the DHCP server, and interestingly enough there are no RRAS lease placeholders as there normally is. I also checked the VPN configuration and Address assignment settings in ISA, and I don't see any issues. Any suggestions before I schedule major maintenance, backup everything, and refresh stuff? Thanks, ...D On 8/1/07, Thomas W Shinder <tshinder@xxxxxxxxxxx> wrote: > > Not related to the SP at all. > > You have a problem with your DHCP server. > > HTH, > Tom > > * > > Thomas W Shinder, M.D. > Site: www.isaserver.org > Blog: http://blogs.isaserver.org/shinder > * > *Book: **http://tinyurl.com/3xqb7* <http://tinyurl.com/3xqb7> > *MVP -- ISA Firewalls*** > > ------------------------------ > *From:* isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] > *On Behalf Of *Danny > *Sent:* Wednesday, August 01, 2007 5:30 PM > *To:* isalist@xxxxxxxxxxxxx > *Subject:* [isalist] SP3 & VPN Client IP address > > Windows Server 2003 SP1, ISA 2004 STD SP3. Since multiple updates > (including ISA SP3) were installed over the weekend VPN Clients (PPTP via > ISA) can no longer RDP to their XP SP2 computers. In troubleshooting, I > noticed the source address for the "VPN Client" changed from > 192.168.1.100-200 (via DHCP server on the LAN) to 169.254.217.248. Since > the ISA policy permiting "VPN Clients" to RDP to their desktops has not > changed and the fact that I am not seeing denied connections while > monitoring the ISA logs, I can only consider spending some focus on SP3. > Unless this is a known issue with a workaround/fix? > > Thanks! > > ...D > > -- CPDE - Certified Petroleum Distribution Engineer CCBC - Certified Canadian Beer Consumer