Make sure something isn't using the wrong DNS Server after the move.
Having to over-ride with a Host file is a hint that it is a DNS problem.
I don't really understand all that you are doing, so I am going to have to
guess a little.....
If there is only one machine involved and the Site is on that
machine,...then when you access that Site from the machine itself the Name
should always resolve to the actual IP# of the machine itself and not the
Linksys external IP#, and not 127.0.0.1.
Since you would not be running your own internal DNS Server (this is XP
after all), the best approach is to add an entry to the Hosts file of:
<actual machine IP#> <site FQDN>
Remember that you accessing your Site from the inside of the LAN has no
relationship to the public accessing it from outside the LAN. They will be
using the Public IP# and you will be using the internal LAN IP# of the
machine itself,...that is the way it is supposed to be. So make sure that
the <site FQDN> resolves to the correct IP# according to the situation.
If you have multiple machines on your LAN (and still no local DNS) then you
will have to repeat the Host file entry on every machine.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/e...epartners.mspx
-----------------------------------------------------
"zero" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Windows XP With Apache V2
> 3 virtual domains been working for years on Time Warner Cable.
> Router is older Linksys BEFSR81
> Port 80 Forwarding to fixed IP 192.161.1.51.
>
> Moved to another house with Time Warner Cable and a newer Linksys router
> WRT554AG Wireless.
>
> Set up DNS to point to new IP address.
>
> Set up Port forwarding and checked that server is correctly serving pages
> by using a remote PC in another city. All is working well.
>
> What's different?
> The old location, http://domain_name works fine from the server on which
> the domain runs.
>
> The new location, http://domain_name opens window for Linksys Login. I
> can't seem to avoid the LinkSys login... unless I add entry to HOSTS file
> 127.0.0.1 domain_name.
>
> How do I fix this?
>
> Zero