Website switching to localhost

[Peter]

IIS6 on Windows Server 2003

I have a DotNetNuke website which works fine as long as I am openning the
webpage on the web server, but when I try to open the same website from any
client the webpage gets redirected

from:
http://reports01/Reports/Default.aspx
to
http://localhost/Reports

same thing happens on the webserver but since it is the localhost it works.
I think the problem is a setting someplace, but I can't find it - it works
fine on my development workstation and anyother websites on this webserver
work just fine.


Thank You


Peter

 

[Hans Kesting]

Peter was thinking very hard :

IIS6 on Windows Server 2003

I have a DotNetNuke website which works fine as long as I am openning the
webpage on the web server, but when I try to open the same website from any
client the webpage gets redirected

from:
http://reports01/Reports/Default.aspx
to
http://localhost/Reports

same thing happens on the webserver but since it is the localhost it works. I
think the problem is a setting someplace, but I can't find it - it works fine
on my development workstation and anyother websites on this webserver work
just fine.


Thank You


Peter

At what point does the redirect happen? Is there some code at that
point that uses a hardcoded "localhost" servername?
Otherwise search through all the files for "localhost" and see what you
find...


Hans Kesting

 

[Cowboy \(Gregory A. Beamer\)]

You don't have an entry for reports01 in the DNS routing table. You can do
this by command line or in the HOSTS file, I would suspect. But that means
on each client machine.

One option is to set up a domain name and put in an actual DNS entry.
Something like reports.mycompany.com. It can be internal, if these are only
internal clients, and served from an internal DNS server (no confusion in
the ether). You then just reconfigure the clients (probably a config
change?).

 

[Peter]

You don't have an entry for reports01 in the DNS routing table. You can do
this by command line or in the HOSTS file, I would suspect. But that means
on each client machine.

One option is to set up a domain name and put in an actual DNS entry.
Something like reports.mycompany.com. It can be internal, if these are
only internal clients, and served from an internal DNS server (no
confusion in the ether). You then just reconfigure the clients (probably a
config change?).

But I do not understand what could be causing this, other websites (None
DotNetNuke) are working just fine.

(yes this is intranet only)

 

[Peter]

You don't have an entry for reports01 in the DNS routing table. You can do
this by command line or in the HOSTS file, I would suspect. But that means
on each client machine.

One option is to set up a domain name and put in an actual DNS entry.
Something like reports.mycompany.com. It can be internal, if these are
only internal clients, and served from an internal DNS server (no
confusion in the ether). You then just reconfigure the clients (probably a
config change?).

I changed the HOSTS file and it did not make any difference, so I still
think it setup someplace on the website, but I don't know where or what

 

[Peter]

You don't have an entry for reports01 in the DNS routing table. You can do
this by command line or in the HOSTS file, I would suspect. But that means
on each client machine.

One option is to set up a domain name and put in an actual DNS entry.
Something like reports.mycompany.com. It can be internal, if these are
only internal clients, and served from an internal DNS server (no
confusion in the ether). You then just reconfigure the clients (probably a
config change?).

The problem was with DotNetNuke I had to add a portal allias