Jump to content
RESET Forums (homeservershow.com)

Can't access my webservers from inside my network


Stealth
 Share

Recommended Posts

Hi Guy's,

 

I need some help please.

 

I have 2012 Essentials setup at home.  It's been running ok with my own webservers on it for sometime. (small website, email server configured with IIS together with the default remote server access site).

 

I decided to move to a new ISP (BT Internet) so setup the new BT Router with my port forwards to my 2012 Essentials box identical to my previous Sky router.  However I can't seem to access my webservers from inside my network. If I type the following directly on my server I get the following response i.e.

 

http://servername:80 - Page can't be found

 

http://192.168.0.2:80 - Page can't be found (this is my server internal IP)

 

http://localhost:80 - Page can't be found

 

https://localhost:443 - Working ok for remote server access

 

https://server-name:443 - Working ok for remote server access

 

https://localhost:9000  - Page can't be found (IIS for mailserver)

 

https://server-name:9000 - Page can't be found (IIS for mailserver)

 

http://www.mydomainname.com - This page can't be displayed

 

https://mail.mydomainname.com:9000 - This page can't be displayed

 

 

Where as if I use a computer not directly on my network i.e at work or my mobile phone I can access the following ok -

 

http://www.mydomainname.com - My website

 

https://mail.mydomainname.com:9000 My mail server

 

So the port forwards seem to be working.  Is this a DNS issue. If so how do I fix this?

 

I'm using DHCP directly on my server 2012 Essentials DC box.

 

I hope someone can help I have spent hours trying to resolve this.  I believe its probably an issue on the server and not with my ISP / router but I'm no expert.

 

Thanks in advance

 

 

Steve

 

 

 

 

 

 

Link to comment
Share on other sites

  • Replies 53
  • Created
  • Last Reply

Top Posters In This Topic

  • jmwills

    10

  • ikon

    16

  • jem101

    6

  • Stealth

    22

Top Posters In This Topic

OK, the 2nd link you posted, http://192.168.0.2:80, proves that it is something more than a DNS issue. Using the IP address directly like you did completely bypasses DNS altogether.

 

A couple of questions:

Can you PING your server from a local client computer?

Have you tried accessing the web pages from more than one local client computer?

Link to comment
Share on other sites

OK, the 2nd link you posted, http://192.168.0.2:80, proves that it is something more than a DNS issue. Using the IP address directly like you did completely bypasses DNS altogether.

 

A couple of questions:

Can you PING your server from a local client computer?

Have you tried accessing the web pages from more than one local client computer?

 

Yes I get a reply if I ping from a client i.e ping 192.168.0.2

 

Yes I tried several computers in my house both on WiFi and on cable same results

 

Steve

Link to comment
Share on other sites

Do you mean remote to a client from outside my network?

 

If so I haven't tried that as I don't use remote to a client only remote in to pull files from the server.

Link to comment
Share on other sites

I'm sure he'll correct me if I'm wrong, but I think jmwills was asking if you can remote into another local computer on your LAN; one other than the server.

Link to comment
Share on other sites

Just to recap

 

https://192.168.0.2:443 works ok from a client

 

but http://192.168.0.2:80 won't work



I'm sure he'll correct me if I'm wrong, but I think jmwills was asking if you can remote into another local computer on your LAN; one other than the server.

 

Sorry I missunderstood.  Yes if I remote in from my server dashboard to another PC on my LAN it works fine.

Edited by Stealth
Link to comment
Share on other sites

jmwills, are you thinking this is a security permissions issue? I'm wondering if the web server is set up to only permit SSL access on port 443: port 80 is blocked.

 

capall, have you checked the firewall settings?

Link to comment
Share on other sites

jmwills, are you thinking this is a security permissions issue? I'm wondering if the web server is set up to only permit SSL access on port 443: port 80 is blocked.

 

capall, have you checked the firewall settings?

 

I turned the firewall off on the router and the server still the same and it was working before I changed the router.  Put the old router back on but without internet access but still no internal access to port 80 or my second secured port IIS port 9000

Link to comment
Share on other sites

Do you mean remote to a client from outside my network?

 

If so I haven't tried that as I don't use remote to a client only remote in to pull files from the server.

No, client to client.

 

Firewall on the router?  Elaborate....

 

What is the primary DNS setting on the server......what is the IP of the server, and what is the DNS address on the clients?  Let's get the easy stuff out of the way

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×
×
  • Create New...