Apache ?Connection refused when attempting to contact www.hingedmind.com?

0 pts.
Tags:
Apache
Bind
DHCP
DNS
Ethernet
IPv4
Linux Distributions
Novell IPX/SPX
Novell NDS
Servers
SUSE Linux Enterprise Server
SUSE Linux Standard Server
TCP
I am running SUSE Enterprise 9 with Apache 2.x. I have recently relocated and everything worked fine on my previous ISP (Cable). In the relocation I changed Cable companies and now when I attempt to connect LOCALLY, I get the following message; ?Connection refused when attempting to contact www.hingedmind.com? When I attempt to connect from another machine on the same network, I get the standard ?The page cannot be displayed.? Any thoughts? Would I get this message if the Cable Provider blocked ports? When I shutdown Apache and restart, there are no errors generated. I am able to see the Apache Server Status when I connect localhostserver-status. I have changed the VirtualHost to reflect a single virtualhost www.hingedmind.com. I am listening on port 80. I tried port 5000 and nothing changed. The DNS servers and gateway appear to be reflecting correct values.
ASKED: August 3, 2005  2:38 PM
UPDATED: August 4, 2005  3:33 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Although you didn’t say so, I’m assuming that you are the owner and operator of hingedmind.com, and that the Apache server in question IS www.hingedmind.com.

Is it possible that the local hosts table contains a reference to your server at its old IP address?

Or that the name server specified in resolv.conf has not been updated?

If you provide a bit more detail, perhaps we can go further with this.

Bob

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Sonyfreek
    I can't see any reason why when you switched ISP's that you wouldn't be able to connect to the server locally. There is no reliance on a network even being there. Are you certain that it worked before? How are you connecting to it (telnet to 127.0.0.1 80, http://localhost)? Can other machines located within your home network browse to the server using the IP address of the internal network? A change of ISP's should only affect your external users connectivity to the DNS entry. Can anyone from the outside connect to the server (if all other tests work) via the IP address/port? The ISP could likely be blocking 80 as a destination port based on their TOS. Hope this helps, SF
    0 pointsBadges:
    report
  • Sapient
    From: bobkberg send a private message to bobkberg Date Sent: 03 Aug 2005 18:36 EDT (22:36 GMT) Subject: RE: Apache ?Connection refused when attempting to contact www.hingedmind.com? Although you didn't say so, I'm assuming that you are the owner and operator of hingedmind.com, and that the Apache server in question IS www.hingedmind.com. Is it possible that the local hosts table contains a reference to your server at its old IP address? Or that the name server specified in resolv.conf has not been updated? If you provide a bit more detail, perhaps we can go further with this. Bob Response: Bob, Thank you for the response. Yes, I am the owner and operator. It resides on a 240 Edge server. Both the host and resolv files are correct. I am now able to connect locally using: localhost, localhostserver-status and www.hingedmind.com However, nothing outside of local. Not even on the same network. Another quick question: I attempted to add port 5000 for http in the services file. After doing so, I should only need to restart the network service, correct? If so, it did not work either. Thanks for the support.
    0 pointsBadges:
    report
  • PeterMac
    Can't get connection, DNS is returning 24.205.237.130 If this is expected IP then likely you have ports blocked soewhere along route. If not then problem is DNS.
    15 pointsBadges:
    report
  • Astronomer
    Another way to test if this is a DNS problem is to try connecting to the web site using the IP address instead of the DNS name. For example, I just connected to www.google.com using http://66.102.7.104/. I found this address of google by using nslookup. If you are doing fancy things on your web server this may not work. It fails on our IIS server. rt
    15 pointsBadges:
    report
  • Bobkberg
    Second question first - yes, you should be able to just do httpd stop and httpd start (or httpd restart) for the new port. First question - regarding other hosts connecting - as someone else suggested, see what IP address DNS is returning from other workstations. Just another guess off the top of my head - is it possible that you're running TCPWrappers on this machine, didn't update the configuration during the ISP migration? HTH, Bob
    1,070 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following