Here's the command if you want to look under 2k.
Dan
============
NET FILE [id [/CLOSE]]
NET FILE closes a shared file and removes file locks. When used without
options, it lists the open files on a server. The listing includes the
identification number assigned to an open file, the pathname of the file,
the username, and the number of locks on the file.
This command works only on computers running the Server service.
id Is the identification number of the file.
/CLOSE Closes an open file and removes file locks. Type this command
from the server where the file is shared.
-----Original Message-----
From: Krueger, Aaron G. - Lonesome [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 11:47 AM
To: NT System Admin Issues
Subject: RE: Microsoft Mail under W2K
IIRC, this is due to a locked open mail system file, specifically a .mbg
(mailbag) file. This was happening a lot in the last days of our
installation as well (also running in a Novell environment). I made a habit
to look through syscon to see who had what locked open for more than a few
seconds...usually clearing the offending connection did the trick for anyone
having an issue.
Aaron G. Krueger
Sr. Network Analyst
-----Original Message-----
From: Vic Spencer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 10:31 AM
To: NT System Admin Issues
Subject: RE: Microsoft Mail under W2K
Michael,
We have a problem very similar to yours here at Colson (150 clients). We
run Microsoft Mail postoffice on an NT server which we just migrated from a
Novell server last year. Like yours, ours has been in operation several
years now (1996) with little to no maintenance needed except for removing
and adding user accounts.
We have experienced the same problem with delayed messaging and additionally
not being able to administer the Post Office from the server or a
workstation until the server is rebooted. We have also had the odd problem
of cetain users (picked on by the system randomly) not being able to receive
any mail until the server reboots at night.
Now let me tell you what we have done that remedies this for us and lets us
get by w/o purchasing some of the more costly mail server packages. Our
WGPO is shared so if I temporarily remove the share, which will temporarily
disconnect the users from the PO, and then turn right around and renable the
share everything is back to normal. A user who is not receiving mail can
now receive and I can get back into the PO as admin. Hey, I know its
cheesy, but it works for us and when you only have 150 users why buy
something else? I've demoed VOPMail, Exchange 2000 and have worked
elsewhere running Exchange 5.0 - we simply don't need those headaches with
no more than we have to administer. Hope this helps some. At least I
didn't call you gramps or something like some of the other guys did.
-Vic Spencer
Network Admin
Colson Caster Corporation
-----Original Message-----
From: Michael W. Ellis [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 24, 2001 10:34 AM
To: NT System Admin Issues
Subject: Microsoft Mail under W2K
I have a Microsoft Mail postoffice being hosted on a W2K server box. My
clients are a mixture of W95, NT 4.0, and W2K workstations. For a variety
of reasons I do not wish to change over to a full-blown Exchange server
implementation at this time.
Some time ago my users started reporting that they were not receiving their
mail in a timely manner. The client are configured to automatically check
for mail every 10-15 minutes. Sometimes the messages are retrieved
immediately, at other times they may be delayed for several hours. At times
the user may retrieve his mail by manually send/receiving.
Without having anything substantial to back this up, my gut feeling is that
the postoffice database has become corrupted. This has been in use for
several years with little or no maintenance other than adding/deleting
accounts. The files have been moved to at least three separate machines
during this period. Are there any tools to verify and/or repair a
postoffice database?
My only other suspicion is that this might be related to W2K. Again, this
is without substantiation, but I notice that W2K seems to have dropped the
postoffice management tools that NT and W95 provided.
I would appreciate any help you may offer in troubleshooting this problem.
Thanks,
Michael Ellis
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
Want to unsub? Do that here:
http://lyris.sunbelt-software.com/scripts/lyris.pl?enter=ntsysadmin&text_mod
e=0&lang=english
Want to unsub? Do that here:
http://lyris.sunbelt-software.com/scripts/lyris.pl?enter=ntsysadmin&text_mod
e=0&lang=english
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately.
Want to unsub? Do that here:
http://lyris.sunbelt-software.com/scripts/lyris.pl?enter=ntsysadmin&text_mode=0&lang=english
