I ran into the same problem when I started working for my current company. 100+ computers, all on a 200.1.1.X addressing scheme. Since I was switching the domain controllers from NT4 to 2000 w/ active directory, I had to change all the addressing anyway. The PDC wouldn't let me create a DHCP range that began with '200.', so I just sucked it up and changed it all. But one way around it may be to ignore the LAT (or fudge it somehow) and use the network's users and groups (if the login servers are Windows-based) to create rules instead of basing it off IP addresses. For example, I created a user group called 'Internet Users' on the PDC and added all the users that need to access the Internet to the group. Dunno if this helps any, but I've found that some of the stuff I've been through here has been somewhat unique.. -----Original Message----- From: Massimo Miccio [mailto:massimo.miccio@xxxxxx] Sent: Wednesday, August 29, 2001 3:09 AM To: [ISAserver.org Discussion List] Subject: [isalist] Installing ISA Server on a non-private LAN http://www.ISAserver.org Hi, I am consulting a company that wants to install an ISA Server on the LAN, but the addressing isn't on 192.168 or others private address. I'm tryin to install ISA as a web cache, b'se thre's also a Check Point Firewall/1 for security. Bypassin the FW question, I've tried to connect the internal network on the first LAN adapter, and the router on other side. Everything works fine, BUT ON INTERNET I LOOSE VERY WEB SITES AS THE SAME AS MY INTERNAL CLASS B NETWORK (192.160.0.0). I can't change the addressing, so I want to know how can I make this work. I think I've to reinstall ISA in Integrated Mode, and "joking" with LAT table, but I've tried and nothin' changed. I've readed around that it's possible Every help will be greatly appreciated Massimo Miccio