Topic: DNS & 5.6 Install

[Jon]

Hi,

I'd appreciate some help as I have a few very frustrating problems.

I've just upgraded from version 5.2 (I think) to 5.6. I needed a bigger hard disc and so upgrading (reinstalling) seemed a good idea.

The system is mostly working well, but with a few exceptions:

1) I can only access the webserver from my intranet using https. e.g. https://192.168.1.2 or https://scullion.
2) The website can only be accessed via the intranet ip address. i.e. 192.168.1.2 and server name (scullion). If I use the FQDN (www.mydomain.net) then it fails.
3) If I try and access the website (www.mydomain.net) from outside of my network then it also fails. However, I can access webmail (https://www.mydomain.net/webmail from outside of my network.
4) When I load https://www.mydomain.net/webmail the login page is already populated with the username admin. I would rather that no username were known to anyone who by chance happened upon that page.

My DNS setup for the domain hasn't changed. It's handled by my ISP and correctly points to my external address.

I'm confused by this as I haven't changed any other part of my network setup, and, as far as I can tell, I've configured my server as before.

It's running in Server Only mode as I have a separate firewall (floppyfw, which hasn't changed).

Aside from the above the system is working perfectly, and I'd like to thank the development team for having produced a system that is easy to administer and that provides a range of services that are perfect for a sophisticated home system.
Any pointers on what is wrong would be very gratefully received.

Thanks,

Jon

[Bill Talcott]

Jon wrote:
>
> I've just upgraded from version 5.2 (I think) to 5.6. I
> needed a bigger hard disc and so upgrading (reinstalling)
> seemed a good idea.

There was no 5.2 unsupported version. Probably 5.1.2.

> The system is mostly working well, but with a few exceptions:
>
> 1) I can only access the webserver from my intranet using
> https. e.g. https://192.168.1.2 or https://scullion.
> 2) The website can only be accessed via the intranet ip
> address. i.e. 192.168.1.2 and server name (scullion). If I
> use the FQDN (www.mydomain.net) then it fails.
> 3) If I try and access the website (www.mydomain.net) from
> outside of my network then it also fails. However, I can
> access webmail (https://www.mydomain.net/webmail from outside
> of my network.
>
> My DNS setup for the domain hasn't changed. It's handled by
> my ISP and correctly points to my external address.
>
> I'm confused by this as I haven't changed any other part of
> my network setup, and, as far as I can tell, I've configured
> my server as before.
>
> It's running in Server Only mode as I have a separate
> firewall (floppyfw, which hasn't changed).

As you seem to know hostname->IP is DNS, so that's most likely where all these problems are. What server are your LAN PCs using for DNS? What are the details of your firewall device?

The external DNS can only point to your external IP. From there your firewall/router device needs to forward the proper ports to the proper servers on the LAN. If you're using the SME for internal DNS, the Hostnames panel is where you can set that up.

Also, are you sure the httpd service is running? Since https works, but not http, you might just have a simple problem of the http server not running...

> 4) When I load https://www.mydomain.net/webmail the login
> page is already populated with the username admin. I would
> rather that no username were known to anyone who by chance
> happened upon that page.

This has been covered before. I think all you have to do is edit "$accountname" out of a template or something similar. It's an easy fix. A search should turn up directions on how to do it.