mac files names problems

[JL]

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

 

[Jim Seifert [MSFT]]

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.

 

[JL]

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]]

Regarding the disconnects, here is some information I posted a while back:

Most likely the client is sleeping the connection and the server disconnects
after not hearing from the client for 2 minutes. Windows 2000/2003 servers
use the AFP2.2 spec that requires this 2 minute forceful disconnect while
the
Mac OS X clients use AFP3.X which allows clients to sleep after notifying
the server. So it is likely that the Mac OS X clients are: 1.) Sending a
idle session sleep notice to the server. 2.) Sleeping the connection. The
server is only aware that the client has stopped sending and after 2 minutes
disconnects session. Both client and server are doing the right thing - it
is an incompatibility between AFP versions. There is no reg key or
configuration
change that can be made to the server to change this behavior.

You can create shortcuts to the server to quickly reconnect.

 

[Rod Dorman]

... Windows 2000/2003 servers use the AFP2.2 spec that requires
this 2 minute forceful disconnect while the Mac OS X clients use
AFP3.X which allows clients to sleep after notifying the server.

Anyone have a reference to when AFP3 first came out?

My impression is it been out for quite a few years, one would think
that Microsoft would have had enough time to support it by now.

 

[Jim Seifert [MSFT]]

It has been a few years. In 2000 or 2001 with OS X as I recall but that was
minus Appletalk which didn't return until 10.1.

 

[JL]

Ok thanks for your help but I have to say that the server is disconnecting
us when we are moving files to him.
Thanks very much
Juan Luis

Regarding the disconnects, here is some information I posted a while back:

Most likely the client is sleeping the connection and the server disconnects
after not hearing from the client for 2 minutes. Windows 2000/2003 servers
use the AFP2.2 spec that requires this 2 minute forceful disconnect while
the
Mac OS X clients use AFP3.X which allows clients to sleep after notifying
the server. So it is likely that the Mac OS X clients are: 1.) Sending a
idle session sleep notice to the server. 2.) Sleeping the connection. The
server is only aware that the client has stopped sending and after 2 minutes
disconnects session. Both client and server are doing the right thing - it
is an incompatibility between AFP versions. There is no reg key or
configuration
change that can be made to the server to change this behavior.

You can create shortcuts to the server to quickly reconnect.


--
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.

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]" <[email protected]> escribió en el mensaje

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.
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