I had to rebuild my ISA machine in house because the old machine was put together with spare parts. It would crash when I tried to load W2k3 SP1. But I could VPN in and access any machine via RDP with the machine name (NetBios = mycomputer). I built a new ISA on W2k3 with all updates and then created all rules that were on the old one. I did this with both running side by side to get the order and rules identical. Although I can VPN in and RDP to my desktop, I have to use its FQDN (mycomputer.mydomain.local) to access it. I did use the VPN wizard thingy to configure access on both ISA's. Haven't had a chance to look into this and haven't seen anything like this posted. Hope this sheds some light on the subject. Dan -----Original Message----- From: Danny [mailto:nocmonkey@xxxxxxxxx] Sent: Thursday, January 05, 2006 1:00 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: VPN Client cannot RDP to server on LAN http://www.ISAserver.org On 1/5/06, Mark Morgan <MMorgan@xxxxxxxxxxxxxxxxxxxxx> wrote: > Are you using NetBIOS name or ip addr to rdp to your machines, I had a similar > problem ip addr worked but when trying to use machine name it would fail, until I > setup a 2nd VPN rule to allow dns to VPN client. Don't know why all outbound > didn't work but when I got it to work I dropped it. By IP address. I may try your suggestion, even though, like you say, does not make sense. Thanks, ...D ------------------------------------------------------ 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: intellihome@xxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx