Can't Access Server Out Side Home Network

[killa kain b]

Ok i have been trying to get a server to work online for at least a week. when im in my home network i can just type in my ip or my domain name and i go straght to it but, i've only got it to work out side of my home network on my smart phone on the hospitals wirrless internet but on any computer even in the hospital my phone access it on i get the default windows browser page. this is how i have it set up.

windows xp sp2
apche 2.2
server hook straght to modom
cable internet ( wich does not block any ports)
the firewall allowing trafic through port 80
dyndns name

please help im lost.

[ua549]

What do you mean by the "default Windows browser page"?
Is it an error message? What is the error number?
Are you using your own PC or the hospital's PC when it works?
What is the security setup on the server and apache?
What do the firewall logs show? system event logs? apache logs?

[killa kain b]

CGI Error
Couldn't connect to 24.xxx.xxx.xxx:80: No route to host
is a message i get on some computer and on other computer i get the standerd can not connect to page with trouble shooting things.

httpd.exe: Could not reliably determine the server's fully qualified
domain name, using 192.xxx.xxx.xxx for ServerName
[Sun Jun 15 10:24:34 2008] [notice] Child 320: Child process is running
[Sun Jun 15 10:24:34 2008] [notice] Child 320: Acquired the start mutex.
[Sun Jun 15 10:24:34 2008] [notice] Child 320: Starting 64 worker threads.
[Sun Jun 15 10:24:34 2008] [notice] Child 320: Starting thread to
listen on port 80.ce] Child 1292: Starting thread to listen on port
80.
thats what my error log repeats and the access log just shows my other computers accessing the internet thout the server computer. i can only access it when im on my computer in my home network or when im on my smart phone on the wireless at the hospital. the computer at the hospital can not access the server at all. the server is allowing traffic though port 80 and apache is set to allow traffic on port 80.

[ua549]

You have a DNS issue, not an Apache issue.

[killa kain b]

well how would i fix this problem. i don't realy know a lot about dns and networking.

[ua549]

Is your domain name registered with an internet registrar?
Is the dns configuration with your dns provider correct?
Are you running the software required by your dns provider, if any?
Is that software configured correctly?

There are a few tools available to help you diagnose dns issues - dig, trace route, ping, ... For Windows many tools are combined into a toolbox called Sam Spade that is available for download free. For many other tools Google is your friend.

Dig will return dns records about your domain.
At a minimum the following records should be present:
SOA (tells about the domain)
A (defines hosts in the domain, 1 for each host)
CNAME (defines an alternate name for an A record host)
NS (defines the name servers, there should be at least 2)

The dns provider will typically generate the correct entries based on the completion of a form containing details of the hosts.

Trace route will display the route followed to reach a given destination. In Windows the name is tracert and is run from a cmd window. If you enter a FQDM, it will first be resolved to an IP - tracert mydomain.com and tracert 11.22.33.44 will produce the same results.

[Carla Schroder]

Good suggestions all, ua549. DNS is fairly complex and easy to get wrong; I suggest doing some serious study. A Safari subscription gets you online access to thousands of computer books for cheap.
http://safari.oreilly.com/

These articles should also be helpful:
http://www.google.com/search?hl=en&as_q=dns+schroder&as_epq=&as_oq=&as_eq=&num=10&lr=&as_filetype=&ft=i&as_sitesearch=enterprisenetworkingplanet.com&as_qdr=all&as_rights=&as_occt=any&cr=&as_nlo=&as_nhi=&safe=images

[killa kain b]

useing Sam Spade this is what happens.

when i trace i get this:
fast traceroute 24.xxx.xxx.xxx
trace 24.xxx.xxx.xxx 0ms 0ms 0msn TTL:128 (name of computer .upmchartermi.net fraudulent rdns)


and when i dig i get this:

07/02/08 00:25:30 dig 24.xxx.xxx.xxx @ 24.xxx.xxx.xxx
Dig 197.xxx.xxx.xxx.in-addr.arpa@24.xxx.xxx.xxx ...
failed, couldn't connect to nameserver

i realy dont know what this means?
thanks for the links i'll take a look at the books too.

[Carla Schroder]

If your wireless is on a different network segment and it's getting through, then perhaps it's a routing problem.

[wmstudio]

Even if you're not using a name server a web server responds to an IP address.... That's the first thing you should test.

[ua549]

Good point WM.

Can you connect by entering the IP as the URL?
http://11.22.33.44

[wmstudio]

Yes of course you can. You will have a problem however if you have multiple websites on one IP address.

[ua549]

I was wondering if the OP could connect using an IP.

[wmstudio]

Op?

[ua549]

Original Poster

[wmstudio]

he should be able to connect using his IP address. That's the first thing he should test. Then you can also check if router, NAT, port forwarding and/or firewall settings are ok. Only then he should try fooling around with dynamic dns.

[Carla Schroder]

OP = orbital possums, sheesh, kidsthesedays dunno nuthin.

[ua549]

That's only if you are an Oregono. Or is that an oregano?

[wmstudio]

mea culpa mea maxima culpa

[ua549]

That's a line from a Jimmy Buffett tune. ;)

[wmstudio]

I have no idea who or what Jimmy Buffet is:confused:

[ua549]

Jimmy Buffett is an author and musician (tropical/beach music). He is one of the few authors to have best sellers on both the fiction and non-fiction lists. His web site is Margaritaville.com

[wmstudio]

and is he also able to help the OP with his web server problem?:)