MacSrv Event ID 12061 Errors

[Mike B]

We are constantly getting people with MAC's booted off the
Windows 2000 MAC Services Server. They loose the file
they were working if it is not saved. Seems to be timeout
issues. Can this be turned off or increased to a much
larger time value fro the MAC's. Does not seem to be a
problem for the PC's that also share files from this File
Server. Very annoying and the complaints are increasing.
See info below:

Event Type: Error
Event Source: MacSrv
Event Category: None
Event ID: 12061
Date: 8/24/2004
Time: 1:15:50 PM
User: N/A
Computer: DWS1
Description:
Session from user "John Smith" was timed out and
disconnected by the server. The IP address of the
Macintosh workstation is in the data.
Data:
0000: 00040000 00520002 00000000 00002f1d
0010: 00050382 c000013b 00000000 00000000
0020: 00000000 00000000 c0a822de

Thank You for your help.

 

[Harish.G [MSFT]]

Hi,

Event ID: 12053 or 12054 or 12061 Session from user "USERNAME" was timed
out and disconnected by the server. The AppleTalk address of the Macintosh
workstation is in the data.

Check the following knowledge base to article.

http://support.microsoft.com/?id=136300
Event ID 12053 or 12054 Caused by Macintosh Client Disconnect

Please let me know if this information helps!


Thank You,

Harish.G

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jane Pitt]

Hi,

I have exactly the same 12061 errors showing up every day on a brand new
2003 server with OSX. I have changed all infrastructure related hardware;
NIC, cables, hubs, even the firewall. Nothing I do makes a difference to the
problem. I have trawled the Internet and every newsgroup I can find for an
answer and no-one has one. It is nothing to do with the Macs shutting down,
they are working away normally when these disconnects happen. The PCs on the
network are not affected.

Does anyone have an answer??? I can't believe that no-one has ever found a
solution to this long-discussed problem.

Thanks frustratedly.

Jane

Hi,

Event ID: 12053 or 12054 or 12061 Session from user "USERNAME" was timed
out and disconnected by the server. The AppleTalk address of the Macintosh
workstation is in the data.

Check the following knowledge base to article.

http://support.microsoft.com/?id=136300
Event ID 12053 or 12054 Caused by Macintosh Client Disconnect

Please let me know if this information helps!


Thank You,

Harish.G

This posting is provided "AS IS" with no warranties, and confers no

rights.

 

[Jane Pitt]

Okay, thank you. But surely the Macs would disconnect almost constantly if
that were the case? They are frequently idle for two minutes but only
disconnect a couple of times a day. Also, they seem to disconnect when they
are in use rather then when idle. Sometimes, all Macs on the network will
disconnect at the same time and sometimes only one. There's no consistency
here.

I have replaced several NT servers with 2003 servers and the users are
demanding to know why things are worse now than they use to be with the old
servers. I haven't got a convincing answer as yet...

Any thoughts?

 

[Jim Seifert [MSFT]]

Connections can be slept on a per connection basis - the Mac client may or
may not be in use at the time a connection is slept and applications with
files open on the shared volume may or may not generate the activity to keep
the connection open. If the server is receiving traffic from the client in
the required interval then the connections should not drop. This has been
our observation using the network monitor tool in previous investigations
and is why an afp incompatibility seems likely here. Using the network
monitor tool on the server and looking at the time stamps of the traffic
between the client and server during these drops can confirm.



NT 4 servers only supported afp over Appletalk connections while the newer
Windows server versions support afp over Appletalk and afp over TCP/IP. The
Mac clients will prefer afp over TCP/IP if the server supports it.
Appletalk itself generates enough network traffic when a share is mounted
that the connections don't get timed out. If you are supporting Appletalk
on your network then the clients should be able to force an Appletalk
connection to the server by using 'afp:/at/server' instead of afp://server
at the connect to server dialog. The connection type can be confirmed by
checking the properties on the share.

 

[William Smith]

Connections can be slept on a per connection basis - the Mac client may or
may not be in use at the time a connection is slept and applications with
files open on the shared volume may or may not generate the activity to keep
the connection open. If the server is receiving traffic from the client in
the required interval then the connections should not drop. This has been
our observation using the network monitor tool in previous investigations
and is why an afp incompatibility seems likely here. Using the network
monitor tool on the server and looking at the time stamps of the traffic
between the client and server during these drops can confirm.

NT 4 servers only supported afp over Appletalk connections while the newer
Windows server versions support afp over Appletalk and afp over TCP/IP. The
Mac clients will prefer afp over TCP/IP if the server supports it.
Appletalk itself generates enough network traffic when a share is mounted
that the connections don't get timed out. If you are supporting Appletalk
on your network then the clients should be able to force an Appletalk
connection to the server by using 'afp:/at/server' instead of afp://server
at the connect to server dialog. The connection type can be confirmed by
checking the properties on the share.

Hi Jim!

AFP 3.x has been in use on Mac OS X for a few years. Any idea when/if
Windows Server will catch up?

For anyone having this problem, I'd be curious to know if a third party
AFP 3.x server such as ExtremeZ-IP fixes the problem. It should if Jim's
description of the problem is correct.

Thanx! bill

 

[Nativtxn]

I had this issue this past week. Turns out the network card on the server
had been manually set to "100Mb/Full Duplex". We set it to "AutoDetect"
and the problem went away. For some reason the routers we use don't like
the servers having their network cards with a manual speed setting.

 

[eye]

If none of the previous works, you can upgrade to Windows 2003 Server, this
will transfer the files at the same speed but will not disconnect the AFP
session.

You can also tweak the Ethernet Adapter settings on the MAC client from
Automatic to Full or Half duplex, you do see a significant amount of
difference.

I ended upgrading to Windows 2003, its the only solid solution.

EyeFx
www.eyefx.co.uk

 

[Eric Barnes]

I have a Win2003 server and this problem still exists.

 

[Marimuthu [msft]]

Hi,

Just try this one out ....

1. Loginto Macintosh machine goto "System Preferences" --> under "Hardware"
title ---> openup the "Engery Saver"

Slect "sleep" tab

a) Set the computer to sleep when it is inactive for: to---> "NEVER"
b) Set the display to sleep when the computer is inactive for: to --->
"NEVER"
c) Uncheck --> "Put the display to sleep when the computer is inactive
for:"
d) Uncheck --> "Put the hard disk(s) to sleep when possible"

Select "Options" tab

Under Wake Options,

a) Uncheck "Allow power button to sleep the computer"



--
Regards,
Marimuthu.P

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This posting is provided "AS IS" with no warranties, and confers no rights.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~