Overload of client using mac osx

[flavio]

I have two mac with mac os 10.3 installed and when they
connect to two or more condivisions, the win2k server
counts for each mac connection a new user user.

So if the two macs connect to 3 directory, they are
counted like if they are 6 user.

The mac connect using SMB, and on the win2k server we have
also the AFP protocol installed for compatibility with MAC
0S 9.2 which is used by older mac.

Has anyone of you have had the same problem?

I would like also to completely remove the AFP protocol,
in order to speed up the network.

Thanx in advance

Flavio

 

[Sandy]

I have two mac with mac os 10.3 installed and when they
connect to two or more condivisions, the win2k server

What's a "condivision"?

So if the two macs connect to 3 directory, they are
counted like if they are 6 user.

Unfortunately thats not all that unusual with SMB. Make sure you have the
latest updates for Mac OS X, recent updates are supposed to improve SMB
support (it may fix this, but I don't have 10.3.3 handy to test).

I would like also to completely remove the AFP protocol,
in order to speed up the network.

AFP over TCP/IP (which Mac OS 8.6 and later can use) shouldn't slow down the
network, however Windows Server likes to install AppleTalk as well, and that
can cause an additional overhead. Try unbinding AppleTalk (note that will
prevent browsing using the Chooser, and Windows Server doesn't support SLP
which is required to browse for AFP over TCP/IP servers).

-Sandy

 

[Guest]

Hi Sandy,
sorry for my pour english but I am writing from Italy and
I do not have full technical english in my mind.

For condivision I mean a folder that it is available to
different users from a server.

I did tried also what you are suggesting, but it does not
work. Any other idea?

Thanx to everyone.

Flavio

 

[Sandy]

Have you tried connecting using AFP (e.g. "afp://server/volume")?

-Sandy

 

[Flavio]

-----Original Message-----
Have you tried connecting using AFP (e.g. "afp://server/volume")?

-Sandy


.

Yes, I did, but did not work. I will post the solution if
I will find it.

Thanx

Flavio

 

[William M. Smith]

AFP over TCP/IP (which Mac OS 8.6 and later can use) shouldn't slow down the
network, however Windows Server likes to install AppleTalk as well, and that
can cause an additional overhead. Try unbinding AppleTalk (note that will
prevent browsing using the Chooser, and Windows Server doesn't support SLP
which is required to browse for AFP over TCP/IP servers).

Hi Sandy!

The presence of Appletalk on the server is slowing down nothing. It is there
to allow the Macs to browse the network and see what's out there. When a Mac
finds a Windows 2000 or 2003 server sharing to Macs then it will switch to a
TCP/IP connection. I suggest leaving Appletalk bound to the server's NIC to
allow the server to be viewable to the Macs.

Since Flavio has Mac OS 9 clients, then they must connect via AFP unless he
chooses to install a third party application like Dave from www.thursby.com.
Therefore, I suggest sticking with AFP when using Mac OS X to prevent
problems when sharing files among various Mac clients. This will probably
assure that he's making one type of network connection (AFP) instead of
possibly connecting via AFP and SMB from the same Mac.

Hope this helps! bill