chimp153
asked on
The webpage cannot be found
Hi all,
I have a web page that works find when I view it internally, but when I go offsite and try to view it it comes up with http 404 error code. The web page cannot be found. I have multiple websites on this server using the same static ip but using host headers in IIS7 and all the others work fine from the internal and external network and this one works fine internally.
I am just wondering what I should be looking for as I am at a bit of a loss.
thanks
I have a web page that works find when I view it internally, but when I go offsite and try to view it it comes up with http 404 error code. The web page cannot be found. I have multiple websites on this server using the same static ip but using host headers in IIS7 and all the others work fine from the internal and external network and this one works fine internally.
I am just wondering what I should be looking for as I am at a bit of a loss.
thanks
Sounds like your DNS records aren't set right for the new site.
ASKER
if i do a dnslookup for the site it comes back with the correct IP address.
Has this site ever worked from outside, or is it new?
Can you PING the server using the domain name?
I couldn't tell from your question, but do all the web pages for that site return 404, or just one page?
Can you PING the server using the domain name?
I couldn't tell from your question, but do all the web pages for that site return 404, or just one page?
ASKER
Just this site returns the 404. All the rest of the sites work fine and they are on the same server under the same inetpub/wwwroot directory. They are just differentiated via host headers.
And it only returns the 404 externally.
And it only returns the 404 externally.
Use NetworkTools.com to do a Tracert to your website to see whether it is getting the right IP address. This will use an external DNS server rather than your own.
http://network-tools.com/
Also check the WHOIS record to be sure it has the right Domain Servers defined,
http://network-tools.com/
Also check the WHOIS record to be sure it has the right Domain Servers defined,
Also check the web error log for the new web site.
ASKER
The domain is correct because we have a www.coffsccs.nsw.edu.au running on the same webserver and it works fine.
I will check the error log and see what that tool tells me. thanks
I will check the error log and see what that tool tells me. thanks
ASKER
I did a trace through the site you provided and it aborted. See below:
TraceRoute to 58.6.40.187 [develsite.coffsccs.nsw.ed u.au]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.46 -
2 0 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.lev el3.net
3 3 0 0 4.69.145.254 vlan90.csw4.dallas1.level3 .net
4 0 0 0 4.69.151.170 ae-93-93.ebr3.dallas1.leve l3.net
5 32 32 32 4.69.132.77 ae-3-3.ebr2.losangeles1.le vel3.net
6 32 32 32 4.69.137.22 ae-72-72.csw2.losangeles1. level3.net
7 32 32 32 4.69.144.80 ae-2-70.edge1.losangeles6. level3.net
8 50 35 35 4.68.62.10 reach-level3-xe.losangeles .level3.ne t
9 36 35 35 202.84.251.190 i-0-1-0-0.1wlt-core01.bi.r each.com
10 173 173 174 202.84.140.22 i-0-2-0-0.sydo-core02.bx.r each.com
11 179 179 179 203.50.13.53 tengige0-2-0-2.oxf-gw1.syd ney.telstr a.net
12 184 191 191 203.50.6.5 bundle-ether1.ken-core4.sy dney.telst ra.net
13 187 179 179 203.50.6.146 bundle-ether1.ken39.sydney .telstra.n et
14 180 179 179 139.130.15.30 iinetl1.lnk.telstra.net
15 186 227 212 203.215.20.95 te1-4.syd-mas-bdr1.iinet.n et.au
16 180 180 180 203.215.20.152 te1-2.syd-mas-bdr2.iinet.n et.au
17 179 179 179 203.215.18.21 te9-1.syd-mas-bng1.iinet.n et.au
18 Timed out Timed out Timed out -
19 Timed out Timed out Timed out -
20 Timed out Timed out Timed out -
21 Timed out Timed out Timed out -
Trace aborted.
Does this mean that it is not getting past iiNet? that is who our ISP is.
TraceRoute to 58.6.40.187 [develsite.coffsccs.nsw.ed
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.46 -
2 0 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.lev
3 3 0 0 4.69.145.254 vlan90.csw4.dallas1.level3
4 0 0 0 4.69.151.170 ae-93-93.ebr3.dallas1.leve
5 32 32 32 4.69.132.77 ae-3-3.ebr2.losangeles1.le
6 32 32 32 4.69.137.22 ae-72-72.csw2.losangeles1.
7 32 32 32 4.69.144.80 ae-2-70.edge1.losangeles6.
8 50 35 35 4.68.62.10 reach-level3-xe.losangeles
9 36 35 35 202.84.251.190 i-0-1-0-0.1wlt-core01.bi.r
10 173 173 174 202.84.140.22 i-0-2-0-0.sydo-core02.bx.r
11 179 179 179 203.50.13.53 tengige0-2-0-2.oxf-gw1.syd
12 184 191 191 203.50.6.5 bundle-ether1.ken-core4.sy
13 187 179 179 203.50.6.146 bundle-ether1.ken39.sydney
14 180 179 179 139.130.15.30 iinetl1.lnk.telstra.net
15 186 227 212 203.215.20.95 te1-4.syd-mas-bdr1.iinet.n
16 180 180 180 203.215.20.152 te1-2.syd-mas-bdr2.iinet.n
17 179 179 179 203.215.18.21 te9-1.syd-mas-bng1.iinet.n
18 Timed out Timed out Timed out -
19 Timed out Timed out Timed out -
20 Timed out Timed out Timed out -
21 Timed out Timed out Timed out -
Trace aborted.
Does this mean that it is not getting past iiNet? that is who our ISP is.
ASKER
PS: Our www.coffsccs.nsw.edu.au comes up with the same trace but the site works fine from outside our campus.
I'll keep thinking on it, but I'm baffled.
Do you have any subdomains other than "www" working from that server? www is somewhat special.
Your DNS records look correct.
Do you have any subdomains other than "www" working from that server? www is somewhat special.
Your DNS records look correct.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Make sure there is no .htaccess file in the develsite folder that may be blocking external access.
Eyal: yes, as I understand it, both sites have the same IP and can both be accessed successfully from within his local network. I don't see how it could be related to IP as, you say, port 80 works and it is the same port on the same server for both web sites. Seems to me the problem must be in the web site configuration or web site access control files.
Eyal: yes, as I understand it, both sites have the same IP and can both be accessed successfully from within his local network. I don't see how it could be related to IP as, you say, port 80 works and it is the same port on the same server for both web sites. Seems to me the problem must be in the web site configuration or web site access control files.
ASKER
I checked the IP bindings and it had our internal IP address whereas the other sites had All Unassigned. I changed this to all Unassigned and it now seems to be working externally.
I appreciate the help from both of you.
I appreciate the help from both of you.