Currently Being ModeratedMay 16, 2012 10:22 AM (in response to spinglass)
I bet it's a DNS problem.
In terminal type the following:
sudo changeip -checkhostname
What does the output say?
Additionally, you could also try connecting by using the IP Address directly instead of the name of the computer.
It probably looks like 192.168.0.2 or 10.0.0.2 or something like that.
Currently Being ModeratedMay 16, 2012 10:42 AM (in response to gracoat)
Do I use that in terminal on the server?
The IP address is manually set using DHCP. It has not changed. It's 192.168.0.11. I have tried conecting with IP address, but that doesn't work either.
Server admin sees the server, but won't let me connect.
If it were a DNS issue, would it allow me to logon for filesharing?
Currently Being ModeratedMay 16, 2012 10:55 AM (in response to spinglass)
Yeah... Type the changeip thing on the servers terminal application. It's in the Utilities Folder.
There are so many variables to explain why it might work for filesharing. For instance, if you're using a .local hostname, then the client will connect no problem. There's a kerberos issue that comes into play when connecting to a file share that doesn't when using screen sharing.
Currently Being ModeratedMay 16, 2012 11:22 AM (in response to spinglass)
graccoat, I've run the chengeip thing now and it has reported the following:
primary address = 192.168.0.14
current hostname = applepip.local
The DNS hostname is not available, please repair DNS and rerun this tool.
dirserv:success = "success"
oddly enough, now that it's connected to the TV again I can access with screen share.
The reasosn the IP address is different to what I gave you earlier is that It's conected to my router wirelessly now, but usually connects through ethernet.
I have also noticed that the hostname returned using the changeip command is different to the nme given in the sharing settings panel.
Currently Being ModeratedMay 16, 2012 11:25 AM (in response to spinglass)
There's your problem. DNS is 100% reliant on a stable network connection. If you switch from ethernet to airport, it will break things!
You should pick a connection type and stick with that permanently. Remember, a server - even a home based one - is designed with high availability in mind. A changing IP address of any kind on a server defeats this!
The reason the DNS hostname is not available is that your DNS is pointing applepip.local to 192.168.0.11 NOT 0.14.
You might get lucky and find that when you plug back into ethernet things will come back to life as they did before.
Out of curiosity, are you connecting your server to the TV via the HDMI connector on your mac mini?
Currently Being ModeratedMay 16, 2012 11:36 AM (in response to gracoat)
OK. It works when it's on wireless 0.14 and not on ethernet 0.11. However it was working on ethernet and then stopped when I resarted it. Any way, How do i get it to work on ethernet again, i.e. how do I get the DNS to point to the right IP when I connect with ethernet? Every time I connect via ethernet it doesn't work now, and every time it's on airport it does work. I want to use ethernet as it connect straight into my TC so backups are quicker.
Yes, I am connecting via HDMI.
Currently Being ModeratedMay 16, 2012 12:24 PM (in response to spinglass)
I've now done some more investigating. The server is now running wirelessly, on 0.14. The only difference being that it is not conected to a screen. I am not able to connect using screen share. So, by the process of elimination, the issue seems to be whether it is actually connected to a screen or not. Could this be right?
Currently Being ModeratedMay 16, 2012 12:43 PM (in response to spinglass)
Yep it could be. I know that in lion they did some strange things with the way that screen sharing is configured. VNC virtual displays etc.
Also, I know that a few months ago, there was an issue with the new mac mini and it's HDMI port. Pretty sure they fixed it with a firmware upgrade a wihle back. ...and it only affected a certain model. If I recall the issue prevented any display from working.... Though I'm not 100% sure about that.
Do you have the white HDMI to DVI adapter that came with the mac mini? It's about 4 inches long.
I'm curious about whether or not you'll be able to connect with the computer with that plug inserted. You don't have to connect a cable to this little white adapter... Just plug it into the mini by itself. It might be enough to trick the mini into thinking there's a display attached.