Re: MacSrv Event ID 12061 Errors
From: Jim Seifert [MSFT] (jimsei_at_online.microsoft.com)
Date: 08/27/04
- Next message: William Smith: "Re: MacSrv Event ID 12061 Errors"
- Previous message: dwade: "Windows 2003 Server and Mac OS 10.3"
- In reply to: Jane Pitt: "Re: MacSrv Event ID 12061 Errors"
- Next in thread: William Smith: "Re: MacSrv Event ID 12061 Errors"
- Reply: William Smith: "Re: MacSrv Event ID 12061 Errors"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 27 Aug 2004 13:52:40 -0700
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.
-- 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. "Jane Pitt" <jane@first-line-support.co.uk> wrote in message news:OQQasBGjEHA.4032@TK2MSFTNGP09.phx.gbl... > 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]" <jimsei@online.microsoft.com> wrote in message > news:uiQBufFjEHA.1348@tk2msftngp13.phx.gbl... >> 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 stop 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. >> "Jane Pitt" <jane@first-line-support.co.uk> wrote in message >> news:eoCnKBFjEHA.3896@TK2MSFTNGP15.phx.gbl... >> > 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 >> > >> > >> > "Harish.G [MSFT]" <v-harig@online.microsoft.com> wrote in message >> > news:soket$BjEHA.1088@cpmsftngxa10.phx.gbl... >> >> 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. >> > >> > >> >> >> > >
- Next message: William Smith: "Re: MacSrv Event ID 12061 Errors"
- Previous message: dwade: "Windows 2003 Server and Mac OS 10.3"
- In reply to: Jane Pitt: "Re: MacSrv Event ID 12061 Errors"
- Next in thread: William Smith: "Re: MacSrv Event ID 12061 Errors"
- Reply: William Smith: "Re: MacSrv Event ID 12061 Errors"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
