SOLVED: this was a non-issue. I moved a PC from my existing local network, to a new SME Server local network. The DHCP stuff refreshed all the network connections, but somehow the browser had cached something nasty (perhaps it was going direct to the MAC address). So when I went to the server-manager of the new server, the PC was actually going to the server-manager page of the *old* server, by tunneling through the new server, and without telling me. A couple of reboots of the PC sorted it out.
Which of course, makes me wonder: can we display the server name on the server-manager login page? What is displayed in the URL does not necessarily tell you which server you are connecting to. A FR perhaps?
------------------------------------------------
(This is in relation to
http://bugs.contribs.org/show_bug.cgi?id=2951, and I seem to have overwritten my own original post - so apologies if the following does not make sense without the context!)
Ok, I think I know why the password is not being accepted. I'm actually seeing the login screen to the wrong server! Doh. I don't understand why though.
This is the setup I have:
Internet
| (Serves DHCP)
|
| 80.x.y.z
|
| (Consumes DHCP)
SME server1 (my main server)
| (Serves DHCP)
|
| 192.168.1.x
|
| (Fixed IP 192.168.1.20)
New server2 (one I have just set up)
| (Serves DHCP)
|
| 192.168.10.x
|
| (Consumes DHCP)
A test PC with a browser
It seems that when I connect to
https://server2/server-manager, I am actually seeing
https://server1/server-manager I guess some funny DNS thing is happening, but I don't know why. If the PC is requesting access to server 'server2', then surely server2 already knows it is 'server2' and should just return its own IP address, and then handle the HTTP request? It seems not.
-- JJ
Edited: Is this because an SME server does not go to the next DNS up the chain to resolve its names, but rather goes direct to the root nameservers?
2 Replies
1658 Views