RE: Domain naming issue
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 23 Sep 2005 04:17:15 GMT
Hi Jasony,
Thanks for posting here! Also thanks for Gregg's input.
For your description, I understand that you have some concern to the domain
name when Mac clients are in an SBS network. If I am off base, please don't
hesitate to let me know.
For your now scenario, you are using the .local label for the full DNS name
of your internal domain, we can do some procedures to make Macintosh
computers discover other computers on the network. To do this, complete
these steps, using the procedures that follow them:
1. Configure TCP/IP settings on the client computers. Configure the TCP/IP
settings on the client computers to specify the search domain explicitly,
so that the client computers resolve .local names correctly.
2. Enable unicast .local resolution on the client computers. Enable the
client computers to use unicast DNS (also called standard DNS) instead of
multicast DNS to resolve names in the domain.local address space. Using the
script described in the procedure, you can configure a Macintosh computer
to look up all .local names on the local network by using either Rendezvous
technology or unicast DNS (if the host is not available via Rendezvous).
The client computer continues to use multicast DNS to look up all other
names.
3. Modify the proxy exclusion list. Add the NetBIOS server name, the fully
qualified domain name, and the NetBIOS domain name to bypass the proxy
settings.
4. Verify DNS resolution. Verify that the NetBIOS server name, the fully
qualified domain name, and NetBIOS domain name are resolving correctly on
the Macintosh computer.
For detail steps to configure above settings, please refer to the Step 3 of
the Microsoft white paper about how to connect Macintosh OS X 10.3 and
Higher Clients to a Windows Small Business Server 2003 Network:
http://go.microsoft.com/fwlink/?LinkId=46578
===============================
If you will reinstall SBS 2003 server, it is recommended that do not .local
domain name if you have MacX clients. Check out the release notes:
"Do not use the .local domain name during Setup if you have client
computers running Macintosh OS 10.2. The Macintosh OS 10.2 operating system
uses the .local extension for its Rendezvous service. As a result, client
computers running OS 10.2 will be unable to discover other computers that
are members of a Windows Small Business Server network that uses the .local
extension."
If your Windows Small Business Server network contains client computers
running Macintosh OS 10.2 or later, change the default domain name during
Setup to use a domain extension other than .local. For example, you could
use a .lan or .office extension. However, it should be remembered that we
can not use public domain suffixes such as .com or .net as our internal
domain name.
For more information, visit the Apple Web site (http://www.apple.com) and
search the Knowledge Base for the article "Mac OS X 10.2: About Your
Computer''s Rendezvous Name."
===============================
More information:
RWW won''t work on native MacOS client. It uses an Active X control to make
the connection. You might be able to do a Remote Desktop connection if you
do a normal TS to the server and then connect from there. There is a Mac
Remote Desktop application that you can download if you make a direct
connection (outside of RWW):
http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/DOWNL
OAD/MISC/RDC.xml&secid=80&ssid=9&flgnosysreq=True
One thing that will support desktop sharing with a Mac is Microsoft Office
Live Meeting:
http://office.microsoft.com/home/office.aspx?assetid=FX010909711033&CTT=6&Or
igin=ES790020011033
Error Message Occurs When You Use a Macintosh OS X-Based Computer to View a
Windows Server 2003-Based Computer
http://support.microsoft.com/?id=316076
Macintosh client cannot connect to Services for Mac on Windows Server 2003
http://support.microsoft.com/?id=834498
Windows Server 2003 Server and Macintosh
http://www.macwindows.com/Win2003.html
NOTE: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.
Hope this helps. Please feel free to let me know if you have any questions
or if you need further assistance on the issue. I am looking forward to
your reply!
Have a nice day!
Best Regards,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Domain naming issue
>thread-index: AcW/nuWmRC87YeurRDuxL8K7sKMINg==
>X-WBNR-Posting-Host: 216.58.132.120
>From: =?Utf-8?B?SmFzb255?= <Jasony@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: Domain naming issue
>Date: Thu, 22 Sep 2005 10:56:02 -0700
>Lines: 9
>Message-ID: <3170079C-7CED-4572-8A27-36410CFF4FBB@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:155621
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>I have just encountered the problem of with having a .local domain name
and
>Macintosh PC on the same network. I just installed the SBS2003 and it is
not
>a big loss if I start over.
>
>I am going to reinstall to change the domain name, but I would like to
know
>if there are any issues with using the .lan or .office as the top level
>domains.
>
>Thanks.
>
.
- Prev by Date: RE: ConnectComputer after SP1
- Next by Date: RE: Terminal Server Licensing after the 120 day temporary license.
- Previous by thread: RE: ConnectComputer after SP1
- Next by thread: RE: ISA authentication for OWA?
- Index(es):
Relevant Pages
|
