Lees de volgende suggesties maar eens door, mogelijk zit er een oplossing bij. De allerlaatste suggestie zou zeker je probleem moeten oplossen, omdat Windows dan geen verbinding meer verbreekt met de idle clients.
Macs disconnecting from Win 2K Server
This is a known problem that can be solved with a Registry edit (see below). Several readers also have workarounds.
Description of problem and workarounds:
July 17, 2003 -- Lorenz Schwarz has a problem with Mac OS X clients disconnecting from a Windows 2000 Server. He also has a workaround:
We recently bought a new Mac with OS X installed. The integration of an OS X client with a Windows 2000 Server has a problem that we don't see with our Mac OS 9.x Macs. Every 20 minutes or so the OS X Mac is disconnected with a notice that its session-time was over. Entering longer values via the default-session-time command in Windows 2000 didn't make any change.
The workaround I'm using for now: I put an older NT4 Server up again, gave it his own domain and made this domain trusting and a trusted one to the Win 2Kdomain. Then I deleted the OS X user on the Win 2K and reopened it on the NT4. The User gets no session-timeouts anymore and can connect directly to the Win 2K Domain and its Volumes.
July 22, 2003
Adam Camilleri
We have also experienced the same problem; but only when we connect via AFP. If you connect via SMB there are no disconnection problems. Copying the files to the desktop has the same effect.
We have been doing some trials with Windows 2003 Server; and there are no signs of this disconnection problem when connecting via AFP.
July 22, 2003
Pat Leary
I read your work around on this subject but I have been having this problem with almost all of my Macs OS 9 and OS X. I'm in a Win NT domain and I am not running Active directory anywhere.
July 24, 2003
Sonja Shuffler
The way I worked around this problem, was to take the Mac OS X users out of the DHCP range of IP Numbers and gave them Static IP's none of the users have dropped off since.
An explanation
July 22, 2003
Todd Miller
With Windows 2000 server, network connections time out after a specified period of time. This is why on Windows clients, mapped drives will have little red Xs on them. With a Windows client, when you try to connect again, you invisibly re-log in to the server and the drive reattaches automatically. All this happens because on an Windows machine you log into a domain and your credentials are cached. This minimizes the number of open connections on a server. Mac clients don't have this ability or feature and so when the Win 2000 server disconnects after a period of several minutes, they are kind of stuck. Don't hold me to this, but I could have sworn there was a way to disable this disconnection "feature" on Windows 2000 servers. Like there is a registry key or something. Another point I'm not positive about is that I think that Win 9x machines where you are not logged into a domain also can have this problem. Also, again off the top of my head, I don't think you are affected if you connect via AFP rather than SMB.
DAVE allows you log into the domain and so doesn't have this problem.
Solution:
July 29, 2003
James Burrows
Reading your site and saw the above problem, which I have seen before.
The solution is a Registry change of the following key :- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\autodisconnect
Set this to ffffffff and the server will never disconnect clients.
See
Knowledge Base article 297684 for more info.
Microsoft Windows: A thirty-two bit extension and graphical shell to a sixteen-bit patch to an eight-bit operating system originally coded for a four-bit microprocessor which was written by a two-bit company that can't stand one bit of competition.