Macs drop connection

  • Thread starter Thread starter John
  • Start date Start date
J

John

Session from user "USERNAME" was timed out and disconnected by the server.
The AppleTalk address of the Macintosh workstation is in the data

I have read the following:

Microsoft Knowledge Base Article - 136300
I have also adjusted the autodisconnect in the registry and I'm still having
this problem...

Anyone figure out how to stop this before I go to MS and open a ticket ?

Thanks for the help.

John
 
You guys are not alone in this item, its happening with my network as
well. If anyone can find a resolve, post it here.

If the error messages were not irritating enough, some of my macs lose
connectivity on 600+ meg file transfers. 2000 OS9 OSX. None of my
PCs have any issues, its just the macs.

One mac would routinely drop large files, setting the sever nic and
the switch to 100Full (not auto detect) seems to have fixed the issue
with one of the macs. The others still have it.
 
I'm seeing this in our environment as well and have never gotten an answer
to the problem. I'd be interested in knowing what you find out.

Thanks,


Jeff
 
I'm seeing this in our environment as well and have never gotten an answer
to the problem. I'd be interested in knowing what you find out.

Thanks,
Click to expand...

This tend to be when a volume is not unmounted properly, IIRC.

For example ... if a volume is unmounted (dragged to trash) it is fine, but
if the machine crashes, or the machine is shutdown and fails to unmount
volumes / drives, or if it loses it's network connection, it takes some time
for SFM to respond. I vaguell recollect it being explained to me as SFM
doesn't want to let the session go in case it comes back after a short blip.

Since we have made sure the logout functions on our Macs definitely unmount
the volumes this has now dropped to a handful a week.

There is information about this in the Apple Knowledge Base somewhere. If I
can dig out the details i will post them here.

Tony Sheppard
 
We are seeing this problem over a WAN. In house, everything is great. Over
the WAN, any copy over 20+Mb will eventually stall and cause the Mac to
autodisconnect all drives. Client is OS X 10.2.6 -- Servers are either
Win2K SP3 or SP4.

Local switch ports are locked at 100/Full at client and 1000 for Server.

Any help would be greatly appreciated.
 
I'll join the group, same problem. Added 2 IMacs to a Server 2003 and they disconnect regularly. I'm trying disabling AppleTalk on them and using only TCP/IP.
----- John wrote: -----

Session from user "USERNAME" was timed out and disconnected by the server.
The AppleTalk address of the Macintosh workstation is in the data

I have read the following:

Microsoft Knowledge Base Article - 136300
I have also adjusted the autodisconnect in the registry and I'm still having
this problem...

Anyone figure out how to stop this before I go to MS and open a ticket ?

Thanks for the help.

John
 
It won't help. We are %100 tcp/ip and we still have the problem. Microsoft and Apple keep doing the finger pointing game and no one wants to really figure it out. We have had the problem ever since we migrated from Novel. My manager has put the thumbscrews on me to figure it out and I think it might be easier to go back to roofing houses!

We have tried everything Microsoft and Apple have recommended. We have brought in expensive contractors. No one has a clue.
 
-----Original Message-----


This tend to be when a volume is not unmounted properly, IIRC.

For example ... if a volume is unmounted (dragged to trash) it is fine, but
if the machine crashes, or the machine is shutdown and fails to unmount
volumes / drives, or if it loses it's network connection, it takes some time
for SFM to respond. I vaguell recollect it being explained to me as SFM
doesn't want to let the session go in case it comes back after a short blip.

Since we have made sure the logout functions on our Macs definitely unmount
the volumes this has now dropped to a handful a week.

There is information about this in the Apple Knowledge Base somewhere. If I
can dig out the details i will post them here.

Tony Sheppard

.
Click to expand...
I successfully tried Tony Sheppard's fix. I had a user
dismount, restart, then copy several files (she was
disconnecting with 1 MB files). Thank you for the solution.

Collin Barrett
 
I'm having a similar problem, however mine is related to Sherlock.
If the Mac users use Sherlock to search a mounted Win Server drive,
the other Mac users on the network either slow down ( OS X) or are locked
out
from accessing the Win Server (Os 9.22) .
Anybody have any clues as to why Sherlock ( which works primarily on
soft indexing a drive to determine its contents) would lock out other
mac clients on the same subnet?
 
I'm having a similar problem, however mine is related to Sherlock.
If the Mac users use Sherlock to search a mounted Win Server drive,
the other Mac users on the network either slow down ( OS X) or are locked
out
from accessing the Win Server (Os 9.22) .
Anybody have any clues as to why Sherlock ( which works primarily on
soft indexing a drive to determine its contents) would lock out other
mac clients on the same subnet?
Click to expand...

Hi Terry!

You're describing a problem that has been around since at least Windows NT
4.0. Have a look at this article for some ideas.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;158796

When one Mac searches a Mac volume shared from an NT-based server, all
connected Macs will hang (showing solid network activity in Mac OS 9) until
the searching Mac has finished searching.

The KB article offers a couple of workarounds from not allowing Macs to
search to changing a registry setting on the server, which decreases the
symptoms for all other Macs and increases search time for the searching Mac.

I haven't been in an environment with multiple Macs and 2000 or 2003 servers
running File Services for Macintosh, so I don't know if or when this issue
has been resolved.

Hope this helps! bill
 
Back
Top