I have an unusual situation. I have an office network with a MS ISA server as a firwall to the internet. I have set up my workstation as a host for remote desktop connection. I have assigned it a fixed internal IP address. In the publishing rules on the Server 2000 ISA server ISA Management, I have mapped a public IP address to this internal IP address on my workstation so that I can access my workstation and my network from any RDC client. It works great. Two of my colleagues have asked me to do the same for them. I needed to get another block of IP addresses from my ISP, which I did. I enterered this block into the ISA server. I set up one colleague's workstation, and after ironing out a few wrinkles I got his to work with no problem. The other colleague got a new laptop and decided to use his older laptop, which is quite powerful and heavy (which is why he decided to get a new one) as a workstation. It runs XP business, like all of our workstations. Here's the mystery...I can't access the laptop using the external IP address. Mind you, I am outside our network when testing the public IP address. However, I can access the laptop RDC host internally, using the internal IP address. So it appears the public IP address is not passing through the ISA server correctly. So to test this, I reassigned colleage #1's ISA set up (which I know works) to colleage #2's IP address, but this didn't solve or prove anything. It still didn't allow me to access the laptop's RDC host. Anybody have any idea why?