Re: Mac file names too long??

Hi Crina,

We have now carried out all these actions and unfortunately we are still
experiencing the same problems..... Is there anything else we can try??

Many thanks

Danny


"Crina Li (MSFT)" <v-crinal@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:3ySxPxTqFHA.472@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Danny,
>
> Thank you for posting in SBS newsgroup. Hi William, Thanks for your
> information.
>
> Generally speaking, for the SBS 2003 domain with MAC clients, some
> particular settings need to be configured. We need to configure the
> networking settings on the MAC; modify the directory service options;
also,
> some settings on the SBS server need to be changed. However, please
> understand that some SBS 2003 features may still not be supported on a MAC
> client. For the MAC in the SBS domain, please refer to the steps of the
> following:
>
> You can check the white paper and ensure both the server and the clients
> are properly configured:
>
> Connecting Mac OS X 10.3 and Higher Clients to a Windows Small Business
> Server 2003 Network
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=89EE677B-0FF6-4558-
> A54B-6070E2C8CD65&displaylang=en
>
> Also, you can refer to my steps to check if you have configured the server
> and client correctly: [note: please notice the ISA section of the bottom
of
> the reply especially]
>
> I. Check the TCP/IP properties of the MAC client. If the MAC client is
> configured to obtain the TCP/IP settings from SBS based DHCP, the settings
> should be properly implemented. If the TCP/IP properties of the MAC client
> are manually configured, please make sure that DNS server is pointing to
> the SBS internal IP address and the internal domain name is configured for
> ''Search Domains''. If you find that the IPv6 is configured, please turn
> off the IPv6 on the MAC client.
>
> II. If the SBS domain is named as domain.local, please enable the .local
> name resolution on the MAC client. For the detailed information, please
> refer to the following KB article:
>
> 836413 You receive an "unexpected error occurred" error message when you
> try to
> http://support.microsoft.com/?id=836413
>
> III. The ''Access Deny'' is probably caused by the SMB signing enabled on
> the SBS 2003 server. By default, security settings on domain controllers
> that run Windows Server 2003 are configured to help prevent domain
> controller communications from being intercepted or tampered with by
> malicious users. For users to successfully negotiate communications with a
> domain controller that runs Windows Server 2003, these default security
> settings require that client computer use both server message block (SMB)
> signing and encryption or signing of secure channel traffic. Since the MAC
> client does not support the SMB encryption, we need to disable the SMB
> signing on the SBS server. For the detailed steps, please refer to the
> following link:
>
> http://www.smallbizserver.net/DesktopDefault.aspx?tabid=98
>
> 811497 Error Message When Windows 95 or Windows NT 4.0 Client Logs On to
> Windows Server 2003 Domain
> http://support.microsoft.com/?id=811497
>
> IV. Configure the Directory Access on the MAC computer:
> 1. Open Directory Access (Macintosh HD > Applications > Utilities >
> Directory Access).
> 2. Click the lock to make changes .
> 3. Enter password for local Macintosh account .
> 4. Select SMB and click Configure.
> 5. Enter the NetBIOS name of the domain in the Workgroup field (see figure
> 2.)
> 6. Enter the IP address of the SBS server in the WINS Server field, and
> then click OK..
> 7. Click OK.
> 8. Click Apply and close Directory Access..
>
> V. Configure the File Sharing for the MAC client:
>
> SBS Server Side:
>
> 1. Install File Services for Macintosh on the SBS server
>
> a. Open Add or Remove Programs in the Control Panel.
> b. Click Add/Remove Windows Components.
> c. Select Other Network File and Print Services and click Details...
> d. Enable File Services for Macintosh.
> e. Click OK.
> f. Click Next.
> g. Wait for the components to install, and click Finish.
> h. Close the Windows installer and the Add or Remote Programs control
panel.
>
> 2. Configuring Shared Folder as File Server for Macintosh
>
> a. Click Start, right-click on My Computer and then click Manage.
> b. Right-click on Shared Folders and then click Configure File Server for
> Macintosh.
> c. Change Enable Authentication to Apple Clear Text or Microsoft.
> d. Click Apply then click OK.
>
> 3. Create shares on the SBS server that Mac will be able to access (other
> than the Microsoft UAM volume)
>
> a. Right-click on My Computer and select Manage.
> b. Expand the Shared Folders icon.
> c. Right-click on Shares and select New Share.
> d. Click Next.
> e. Enter the path to the folder on the hard drive or click Browse to
select
> the folder (for example, Users Shared Folder).
> f. Click Next.
> g. If the folder selected is already shared to your Windows clients,
> uncheck the Microsoft Windows users checkbox.
> h. Enable the Apple Macintosh users checkbox and enter a name (for
example,
> Mac Users Shared Folder) for the share in the Share name field.
> i. Click Next.
> j. Click Finish.
> k. Click Close.
> l. Right-click on the new share and select Properties.
> m. Uncheck the This volume is read-only checkbox and click OK.
>
> Mac OS X-based client Side:
>
> 1. Install Microsoft UAM on the MAC client
>
http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=windows200
> 0sfm
>
> 2. Enable and configure AppleTalk on the Mac OS X
>
> a. From the Apple Menu, select System Preferences .
> b. Click the Network icon .
> c. Select Built-in Ethernet and click Configure.
> d. Click the AppleTalk tab and select the Make AppleTalk Active checkbox
> (see figure 3).
> e. Click Apply Now and close System Preferences.
>
> 3. Configure the AppleTalk protocol
>
> a. Open Macintosh HD.
> b. Click Applications in the left pane.
> c. Open the Utilities folder in the right pane.
> d. Double-click the Directory Access application.
> e. Click the lock to make changes.
> f. Enter the username and password for the local Macintosh user.
> g. Clear Active Directory and SMB.
> h. Select AppleTalk.
> i. Click Apply and quit Directory Access.
>
> 4. Connect to the SBS server
>
> a. From the Finder, press Command-K.
> b. In the Server Address field, enter afp://servername, where servername
is
> the AppleTalk name of the server.
> c. Click Connect.
> d. Enter the username and password to connect to the server.
> e. Select the volume or volumes you wish to mount and click OK.
> f. The volume(s) will mount on the desktop.
>
> For the MAC - SBS access, please also refer to the following KB article:
>
> 830044 Macintosh users cannot connect to Outlook Web Access (OWA) when OWA
> is
> http://support.microsoft.com/?id=830044
>
> In addition, could you please let me know if ISA server is installed on
the
> SBS server? If so, you may also need to modify the ISA configurations. The
> predefined ISA access rules only allow the authenticated users to access
> the Internet. Since the Firewall client cannot be installed on the MAC
> clients, you also need to change the ISA configurations to allow the
access
> from the MAC computers:
>
> 1. Make sure that you have run CEICW on the SBS server to configure the
> internet connections:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> 2. Create a client set for the MAC computers. In ISA Management console,
> expand Policy Elements. Select Client Address Sets. Select "Create a
Client
> Set". For the Name let''s use "MAC Clients". Click ADD and type in the
IP
> addresses or range of addresses that will be used for the MAC computers.
> Click OK.
>
> 3. Create a Protocol Rule to allow MAC Clients to pass through the
> Firewall. Expand Access Policy. Select Protocol Rules. Select "Create a
> Protocol Rule". Let''s use "MAC Rule" for the name. Click NEXT until you
> get to the *** entitled "Client Type". Select "Specific Computers
(client
> address sets), click Next. Click ADD. Select the "MAC Clients" we created
> earlier and click "Add ". Click OK, Click Next, Click Finish.
>
> 4. Create a Site and content rule to allow the MAC Clients to access the
> web sites.
>
> 5. In ISA Management console, right-click the ServerName and choose
> ''Properties''. In ''Outgoing web requests'' tab, uncheck ''Ask
> unauthenticated users for identification'' box. Click ''OK'' to close the
> dialog boxes. Navigate to ''Monitoring''\''Services''. Restart the ISA
> related services.
>
> This response contains a reference to a Third party World Wide Web site.
> You should know that Third party sites are not under the control of
> Microsoft. Accordingly, Microsoft can make no representation concerning
> the content of these sites. Microsoft is providing this information only
> as a convenience to you. This is to inform you that Microsoft has not
> tested any software or information found on these sites and therefore
> 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 on the Internet.
>
> I hope the above information helps. If you have any questions or concerns,
> please feel free to let me know.
>
> Best regards,
>
> Crina Li (MSFT)
>
> 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.
> --------------------
> | From: "Danny" <danny@xxxxxxxxx>
> | Subject: Mac file names too long??
> | Date: Wed, 24 Aug 2005 13:37:16 +0100
> | | Newsgroups: microsoft.public.windows.server.sbs
> ||
> | We have an SBS2K3 server and various WinXP and Mac clients.
> |
> | We have 2 main problems;
> | 1..... is that when we attampt to copy files with names ove 31
characters
> it
> | will not allow this unless we reduce the file name. Is there a way
around
> | this or is this a limitation with using MACs on windows server??
> |
> | 2... is that the MACs can see and share files on the server and talk to
> the
> | internet provided the users passwords are blank....if we create
passwords
> | for the users on the server then we cannot access the server etc
> regardless
> | of the autentication method we try to use. Even without passwords we are
> | unable to perform certain functions from the MACs, i.e. FTP to other
sites
> | even using passive FTP, we cannot listen to the radio through the MACs
> even
> | though realplayer has the correct proxy settings etc. There is no
problem
> | from the WinXP clients so I believe that the ISA server must be
configured
> | OK. We have followed some articles for bypassing the proxy server on the
> | MACs, however even once this has been implemented they still get an ISA
> | authentication error, even though we are trying to bypass it.
> |
> | Any help resolving these issues would be greatly appreciated.
> |
> | D
> |
> |
> |
>


.