Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ISA Configuration between domains

Status
Not open for further replies.

eman28

MIS
Sep 13, 2002
7
US
I'm having problems getting end users to access the internet via ISA server. My scenario is as follows:

Currently, all end users are in an NT domain. I have a new AD domain (prepping to migrate to AD - it has a one-way trust to the NT domain). My ISA Server sits in the AD domain and is configured for integrated authentication and basic authentication (with the domain set to the NT domain). The server itself is able to access the internet with no trouble and can also access resources on the NT domain. Machines in the NT domain are able to access the AD domain and its resources.

Here's the problem. The machines in the NT domain aren't able to access the internet if configured to use the ISA Server in the AD domain.

I know I'm missing something, but don't know what else to try. Please advise...
 
ok just a guess here but ,

try editing the LMHOSTS file on the NT machines to pre cashe the ISA machine on startup i believe the command is
#PRE <computer name> <ip>
Then you can just propogate that file to the other NT machines.
Again this is just a guess but also make sure you got a 2way trust , that will have to be set up on the AD of course.
This prolly isnt the answer as im just a novice at this but i saw no replies so i figured id take a stab at it at least :)
 
Thanks for the assist. Actually, the problem isn't in getting the machines to see the ISA Server located in AD, but actually getting the rules working properly. Here's my setup:

ServerA (in the NT domain) is the primary ISA server. All users connect to the internet through this server. I have ServerB (in the AD domain) as a backup ISA Server. In the event that the internet connection for ServerA fails, I want it to automatically point to ServerB for internet connectivity. I am trying to do this using the routing rules. I setup a &quot;Normal Routing&quot; rule on ServerA that gets requests directly from the internet. A modified the Default Rule (the last rule) to point to the upstream ISA server (ServerB) as an alternate route. In theory, this looks right. However, when I test this (by disconnecting the external NIC on ServerA), it doesn't route to ServerB.

Am I doing something wrong? or am I missing something that needs to be in there in order for this to work?

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top