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
LVL 3
tsnironeAsked:
Who is Participating?
 
strungConnect With a Mentor Commented:
You are right that the problem is DNS.

The Mac Hosts file is in a hidden folder which you can access as follows:

Click on the desktop to make sure you are in Finder.

Pull down the Finder menu to Go to Folder and type in the following:

/etc

This will open the hidden etc folder.

Find the file named Hosts. Right-click on it and select Open With. Select TextEdit.

Edit the file, then save, making sure you are saving as TXT, not RTF. Textedit will automatically add a .txt suffix which you then have to remove in Finder.

Reboot to activate the changed
0
 
strungCommented:
Http:// is for connecting to a web server. Is that what you are trying to do?

To connect to a file server, use SMB://servername/sharename
0
 
strungCommented:
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
tsnironeAuthor Commented:
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.
0
 
strungCommented:
Your alternative is to use the Windows DNS server, but this may cause problems with laptops when you take them out of the office.
0
 
tsnironeAuthor Commented:
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?
0
 
strungCommented:
You may have to experiment. I would think the first one.
0
 
strungCommented:
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
0
 
tsnironeAuthor Commented:
Ok thanks man! Havent implemented yet but I am pretty sure this is it. Thanks again :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.