tsnirone
asked on
Connecting Mac to Windows Server 2012 Essentials
Mac Client OS is 10.6.
Server is Windows Server 2012 Essentials (all updates installed)
http://servername/ <- does not work (not found)
http://servername/connect <- does not work (not found)
ping servername <- times out
ping serverIP <- works just fine
All of the above works on PC on same LAN.
I have verified the prerequisites here:
http://technet.microsoft.com/en-us/library/jj593199.aspx
Ideas?
Edit:
Also tried:
http://servername.local/ <- does not work (not found)
http://servername.local/connect <- does not work (not found)
ping servername.local <- times out
Server is Windows Server 2012 Essentials (all updates installed)
http://servername/ <- does not work (not found)
http://servername/connect <- does not work (not found)
ping servername <- times out
ping serverIP <- works just fine
All of the above works on PC on same LAN.
I have verified the prerequisites here:
http://technet.microsoft.com/en-us/library/jj593199.aspx
Ideas?
Edit:
Also tried:
http://servername.local/ <- does not work (not found)
http://servername.local/connect <- does not work (not found)
ping servername.local <- times out
ASKER
Yes, its the Windows Server 2012 Essentials webserver I'm trying to access.
Using:
http://<IP>/connect
works.....
The mac-clients does probably not use the DNS server on the windows server and this is why its not able to translate <windows_servername> to a <ip-adress>
I could perhaps simply edit the hosts file on the macs? Not sure how to do that though, nor am I comfortable this is the way to go.
Perhaps change the mac clients to use the DNS from the windows server?
I simply dont know.
Using:
http://<IP>/connect
works.....
The mac-clients does probably not use the DNS server on the windows server and this is why its not able to translate <windows_servername> to a <ip-adress>
I could perhaps simply edit the hosts file on the macs? Not sure how to do that though, nor am I comfortable this is the way to go.
Perhaps change the mac clients to use the DNS from the windows server?
I simply dont know.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Your alternative is to use the Windows DNS server, but this may cause problems with laptops when you take them out of the office.
ASKER
I guess the main problem with this setup is that the router in this lan (which I am unable to access) has dhcp thus I had to turn this off on the windows server.
Do you know what I should put into the hosts file?
<serverIP> <servername>
or
<serverIP> <servername.domain>
or
<serverIP> <servername.domain.local>
or all of them? What would you do? Any "best practice" on this?
Do you know what I should put into the hosts file?
<serverIP> <servername>
or
<serverIP> <servername.domain>
or
<serverIP> <servername.domain.local>
or all of them? What would you do? Any "best practice" on this?
You may have to experiment. I would think the first one.
If you want to avoid rebooting between tries, you can flush the DNS cache instead. To do this, type TERMINAL into the Spotlight search window to open the Terminal Command line utility. Copy and paste the following line into the terminal window and hit return:
dscacheutil -flushcache
dscacheutil -flushcache
ASKER
Ok thanks man! Havent implemented yet but I am pretty sure this is it. Thanks again :)
To connect to a file server, use SMB://servername/sharename