Test my server for me
 

I just installed Apache and what to make sure it is configured right. Just tell me if you can see this picture:

chollman82.dynip.com/sm3.jpg

nope.

Not Found

The requested URL /sm3.jpg was not found on this server.
Apache/2.0.52 (Win32) Server at chollman82.dynip.com Port 80

Okay, try again, I think I fixed it

I got it.
I love mario, one of the greatest games I've played is Super Mario Bros. 3.

So far nothing..... Wait.... wait....... wait.......... a little more....
It worked but it took quite some time to do so.
It may just be the intense demand that TFP would put on said server though.

SUPER MARIO!

Cool, thanks. Homey_V what speed connection do you have? it is a 200kb file... Then again my upload is capped at 512kb/s

I see Mario all the way in Seattle

It worked first time for me.

Not working for me now!

-Lasereth

well, why not just load http://127.0.0.1 and it will serve pages if apache is working.

for some reason that just seems completely logical to me instead of killing your bandwidth just to see if something is working. glad you don't work in the IT field.

It's possible that he was also trying to test out his firewall rules or a host of other things. There's no need to be rude to someone who is asking for help.

To CHollman, did you take it down? It's no longer showing up.

I see nothing mentioned above about firewall rules. Also, why run apache and not have port 80 open to it? If it were internal, then why say anything about it at all.

My point was that there may have been a more tactful way of going about letting him know about internal testing. To people that are just learning (which I'm making an assumption that he is...hopefully that is true) about setting up Apache and network basics, etc, it can be pretty discouraging when someone says something like that. That being said, your point was completely valid and was a valuable piece of advice.

Hopefully CHollman will keep on trying things like this, and he will have a job in IT at some point.

He didn't say he was a professional and he didn't say he was constructing a server for a business. He simply stated that he installed Apache and wanted to see if it would work. I'd do the same thing if I were experimenting with an Apache installation.

You may be glad he doesn't work in the IT field...I'm glad you don't work in the PR field. :thumbsup:

-Lasereth

Dude, I don't see it.
"the operation timed out"

Luck!!

was grumpy this morning, sorry to be rude earlier. as always lasereth, thanks for pointing that out.

Next time CHollman, i wouldn't ask a forum to test your webserver. You might end up with a Slashdot like effect that could make your ISP very angry with you.

Not working for me either.

Bendsley, I AM just learning this stuff, and I DON'T want a job in IT. Why would a person with a bachelors degree in Comp Sci want to take such a pay cut and work in IT...

and by the way, I know that 127.0.0.1 is the local host address. What I was doing was making sure that DynIP had registered my IP with the DNS servers. You might want to make sure that you know what you are talking about before you go insulting someone next time.

DynIP...
 

Chollman:

A friend of mine happens to work for that company, and gave me a basic idea of what happens if the update client stops unexpectedly:

Their servers update within minutes of the client going up and if your client isn't up, you get shunted to an "offline" page that tells the end user that "the current server you are trying to connect to is offline".

No matter what, everyone here would have seen /something/ regardless of whether or not your web server was listening for requests at the time. If they don't, that means your dynip client is active, but your web server is not (which imo is a no-no, since end users don't really know what's going on!).

By default, Apache listens to all of your network interfaces, including localhost. To test your installation, you can simply go to localhost via your browser. If it doesn't work, you should get an error page sent to your browser as well as an entry in your Apache access / error logs for you to peruse. In essence if it works locally, there's no reason it shouldn't work over the Internet (barring firewall rules of course).

CHollman: I have a Bachelors Degree in Management, and I work in the IT field. I gaurantee you that I did not take any sort of paycut for the job that I do.

As trache said above, apache listens on all interfaces, so, I do know what I'm talking about. If you wanted to make sure that DynIP had registered your IP addy with DNS, all you should actually have to do is ping. This is assuming your firewall isn't blocking ICMP echoes.

By this statement above that I quoted you on, you only wanted to make sure it's configured correctly. By correctly, I automatically assume configured correctly means working correctly. So, in essence, just use http://127.0.0.1. If you're wanting to test your IP against a DNS entry, please say that next time.

I did also apologize above for being cranky yesterday morning. I corrected myself and that should have been the end of it. However, it was not, because you had to attack me back.

Not Available!

The DynIP customer at chollman82.dynip.com is
not connected to the Internet right now.
Please try again later.

As of 1945 hours on 06 Oct.

Not Available!
The DynIP customer at chollman82.dynip.com is
not connected to the Internet right now.

Please try again later.



What is DynIP?
DynIP gives your computer an Internet Name that automatically tracks your current IP Address every time you connect to the Internet. If you want to run a server from your desktop you can give your Internet Name to your customers and they can find your server without ever knowing your current IP Address again! DynIP's Internet Name technology works great with multi-player internet games, video conferencing (i.e. NetMeeting), voice conferencing (i.e. IP Phone) and remote access (i.e. PC Anywhere). You can use your Internet Name with all Internet applications where your current IP Address is required.

operation timed out...