TIA,
-=John=-
MCSE,MCP+I,CCNA,CCA

You don't want an internal DNS server?

Chris

I need to get part 2 of that web publishing article up. Its due for next week, so expect to see it then.

John, when you publish a web server, you got to make sure that there is a DNS entry on an public DNS server for the FQDNs for your web sites. If there isn't one, then no one will be able to access the site via FQDN, and they'll have to use an IP address. If you use an IP address, you can only publish one site per IP address, and even then, there are some "issues" when publishing multiple sites using IP address.

HTH,
Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

I have the FQDN residing on our ISP DNS servers, so it will resolve properly. I have configured the ISA server to allow Incoming web requests (on port 80). I have setup a destination set called www.mydomain.com using www.mydomain.com as web address (I have also tried to add directories, etc). I then created a web publishing rule to use the above destination set, and forward all requests to the internal web server (using it's IP address). Seems pretty straight forward, just doesnt seem to work for me<G>.

Chris... I am putting up an internal DNS server. Just haven't gotten to it yet (it's on that long list of things I never have time for <G> ).

Am I missing something? I am using the true release of ISA server (NOT enterprise, not RC1). I keep thinking i'm missing something, but I can't figure it out.

Thanx again for the help.

-=john=-

You do seem to have all your bases covered. The only other thing I can think of is whether you have a rule on the ISA Server that allows the internal server outbound access? Although, now that I think about it, you really don't need such a rule.

What kind of Protocol and Site/Content rules do you have on the ISA Server? How about the LAT? I the LAT and the routing table on the ISA Server configured correctly?

HTH,
Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

At this point, I think I am going to uninstll ISA, and start fresh. It only a test box currently, andi'm the only one connected. I'm thinking that I must have screwed something up during the configuration.

So, I figure i'll start from scratch, and see what happens. Thanx for all the help, I really appreciate it (don't worry - you'll be hearing from me again )

I'll let you know what happens.

Thanx again,

------------------
-=john=-
MCSE,MCP+I,CCNA,CCA

Whacking the installation and starting over can fix many things! There have been MANY people on this board that found themselves with a hopeless situation only to find it magically fixed after uninstalling and reinstalling.

I've had to do this a few times myself. Such as when I applied a security template and it completely whacked the Content Download Service!

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/