Re: mac files names problems

Perfect! I can connect and move files AFP is the solution! Although I have a
little permissions problems but it's nothing important.

Now we found two problems AFP OSX disconnections problems vs a W2003 and
people who is copying cd's comunnicate me that the OsX seems to run more
slowly than copying by SMB protocol

Thank You Very Much!!!!!



"Jim Seifert [MSFT]" <jimsei@xxxxxxxxxxxxxxxxxxxx> escribió en el mensaje
news:euOZj6yTFHA.2996@xxxxxxxxxxxxxxxxxxxxxxx
> SMB file sharing does not translate disallowed character names on the
> server. It would appear that you are connecting to the w2k3 Server with
SMB
> and the w2k Server with afp. To have the SFM service translate these
> characters you will need to connect to the w2k3 Server using
> afp://servername. Note: w2k3 Macintosh shares are created read only so
that
> setting will need to be changed to write the files to the Server. This
> setting is a checkbox on the general tab for the share.
>
> --
> Please do not send e-mail directly to this alias. This alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "JL" <juanluisESTONOVA@xxxxxx> wrote in message
> news:OiBdQBwTFHA.2680@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi I write you from Barcelona in Spain please, excuse my english :)
> >
> > We have a mixed LAN pc's and Macs but our servers are Windows. We just
> > installed a w2003 server with lots of terabytes ( Adaptec DAS ) when we
> > started to move files from mac cd's ( using a MIniMAC ) to the new
2003
> > server we found lots of file names characters problems ( * / " ... ).
> >
> > We started to use a script to rename this files and then move them to
> > w2003.
> >
> > We have another file server with w2000 s.o. Then moving files from our
> > w2000
> > server ( the old server ) to the w2003 ( the new ) I notified that the
old
> > server ( w2000 ) is translating files names and accepting "strange"
> > characters but w2003 is not accepting this files because of his names
> >
> > In both servers The Macfile configuration is exacly the same I try to
find
> > if it is a client connection problem but afp connection from macosX to
> > w2003
> > don't keep folder permissions and we can not copy files.
> >
> > So the problem is why w2000 accept all files names ( because he
translate
> > the characters like * or / ) and w2003 is not translating this
characters
> > so
> > he does not accept the files. Is it a server configuration ? or it is a
> > client ( mac osX ) connection problem ( afp vs smb )
> >
> > Any help posibble?
> >
> > thanks anyone
> >
> >
>
>


.

Relevant Pages

  • Re: SFM and Long Filenames in Win2K Server
    ... We have a 2K server, and all of our Mac Clients are having issues ... SFM only supports 31 characters but your Macs are probably trying to ... I suggest you look into using another AFP ...
    (microsoft.public.win2000.general)
  • Re: Macs getting kicked off Win2k
    ... Windows Server 2003 uses the ... older AFP 2.2 file sharing protocol and Mac OS X uses AFP 3.1. ... Be sure that none of your Mac clients have their Energy Saver settings ... advantage of Access Control Lists (ACLs). ...
    (microsoft.public.win2000.macintosh)
  • Re: Cant connect OSX 10.3 & OS9 clients to same Win2k Share
    ... What about Windows 2003 Server would that help? ... the UAM will only apply to AFP connections that you make. ... Mac OS X's version of SMB will split the Mac ...
    (microsoft.public.win2000.macintosh)
  • Re: Netware 4, 5, 6 - AFP-Server-Fragen
    ... was der Server behauptet zu können. ... AFP reply from localhost:548 ... Network address: 192.168.92.3:548 (TCP/IP address and port) ...
    (de.comp.sys.novell)
  • sometimes users unable to save - network home folder environment
    ... The server is a G5 w/ 6gb ram, ... While we don't use many other apps other than MS Office apps, ... There is nothing in the system log or the console, and the AFP log has ...
    (microsoft.public.mac.office)