Problem with SFM and OS X 10.4

[Michael Russell]

Up to this point, we've been using OS 9 clients on our network. Windows
2000 SFM has been working fine for providing AppleTalk print and file
services.

Now, we have a new employee with a PowerBook running 10.4, and he is
unable to connect to any of our AppleTalk shares (although AppleTalk
printers and SMB mounting work fine). I understand that 10.4 now
requires AppleTalk over TCP/IP, but I thought that's what SFM provided.
I see no option to turn it on, on the server.

Am I missing something, or am I going to have to use different file
sharing software on the server, like ExtremeZ-IP?

Thanks,
Michael Russell

 

[William Smith]

Up to this point, we've been using OS 9 clients on our network. Windows
2000 SFM has been working fine for providing AppleTalk print and file
services.

Now, we have a new employee with a PowerBook running 10.4, and he is
unable to connect to any of our AppleTalk shares (although AppleTalk
printers and SMB mounting work fine). I understand that 10.4 now
requires AppleTalk over TCP/IP, but I thought that's what SFM provided.
I see no option to turn it on, on the server.

Am I missing something, or am I going to have to use different file
sharing software on the server, like ExtremeZ-IP?

Hi Michael!

Macs have been using AFP over IP since Mac OS 8. Mac OS X 10.4 has
introduced nothing new other than maybe some performance tweaks.

Your server may have its security set to require Microsoft
Authentication and your Macs may have the Microsoft UAM installed while
your new employee doesn't. Or in his connection dialog he may be forcing
a secure connection that your server doesn't understand.

For the Microsoft UAM, you can download it from Microsoft's website
<http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=window
s2000sfm>.

Also make sure his password to the server is eight characters or less
unless he's connecting via SMB or with the UAM installed.

Hope this helps! bill

 

[Michael Russell]

Hi Michael!

Macs have been using AFP over IP since Mac OS 8.

I know, and I didn't mean to question that.

Mac OS X 10.4 has

introduced nothing new other than maybe some performance tweaks.

Features like Spotlight, Dashboard, Automater, etc., weren't in 10.3.
They might have existed elsewhere in the computing world, though. Don't
see how this affects my problem.

Your server may have its security set to require Microsoft
Authentication and your Macs may have the Microsoft UAM installed while
your new employee doesn't.

It doesn't.

Or in his connection dialog he may be forcing

a secure connection that your server doesn't understand.

He's not.

For the Microsoft UAM, you can download it from Microsoft's website
<http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=window
s2000sfm>.

Also make sure his password to the server is eight characters or less
unless he's connecting via SMB or with the UAM installed.

This isn't an issue.

Hope this helps! bill

The reason for asking about difference in 10.4 vs. older OS X is because
we have a vanilla installation of 10.3 that connects instantly using the
connection string: afp://<ip address/projects . Using the same on the
new 10.4 box results in an error that the system could not mount the volume.

Michael

 

[Jim Seifert [MSFT]]

The reason for asking about difference in 10.4 vs. older OS X is because

we have a vanilla installation of 10.3 that connects instantly using the
connection string: afp://<ip address/projects . Using the same on the
new 10.4 box results in an error that the system could not mount the
volume.

Michael

While this could be due to changes in 10.4 but we have investigated this
previously and a static mapping of the network configurations on the Mac
client fixes the connectivity problems. You don't need a static IP but
entering the gateway and dns information might help. If Appletalk is
enabled on the Mac client interface and the network you can try
afp:/at/Server/.