Have a Windows 2000 server setup. Windows 98, ME, 2000, and XP Pro clients.
About 19 connections to the server. 25 user license on the server.

Server was Novel 3.2 then upgraded to 2000.

Having problems with some workstations getting locked out of the server.
They will suddenly not have connections to the mapped drives. Trying to
reconnect will give them a security error. Logging off and then back on
does not help. The workstations have to be rebooted to get the connection
back on.

Has anyone seen this. Had a friend of mine say that he had a problem with
this on a server he was managing. He had been using VB scripts for logon.
He said once he swapped to just batch files he was good to go. Currently we
are not running any scripts on the network. There are not enough mapped
drives to make this neccessary.

Any help will be greatly appreciated.

Thanks,

Jon

What is the exact error message you're getting?

Are you getting it consistently across all clients?

Note that this is a newsgroup related to setup and deployment issues. I
would say that microsoft.public.win2000.networking would be a better bet.

Cheers

Oli

"J Jones" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Have a Windows 2000 server setup. Windows 98, ME, 2000, and XP Pro
clients.
> About 19 connections to the server. 25 user license on the server.
>
> Server was Novel 3.2 then upgraded to 2000.
>
> Having problems with some workstations getting locked out of the server.
> They will suddenly not have connections to the mapped drives. Trying to
> reconnect will give them a security error. Logging off and then back on
> does not help. The workstations have to be rebooted to get the connection
> back on.
>
> Has anyone seen this. Had a friend of mine say that he had a problem with
> this on a server he was managing. He had been using VB scripts for logon.
> He said once he swapped to just batch files he was good to go. Currently
we
> are not running any scripts on the network. There are not enough mapped
> drives to make this neccessary.
>
> Any help will be greatly appreciated.
>
> Thanks,
>
> Jon
>
>

That crossed my mind, but once the name's been resolved, it should be cached
by the WINS client, shouldn't it?

Therefore, either the drive would map or it wouldn't. You wouldn't expect
connections to just drop.

Still, I draw the line at helping people to run WIndows 98/ME in a business
environment. It wouldn't be doing them any favours.

Cheers

Oli


"NIC Student" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Sorry to jump in, just a thought - You are not using any scripts on the
> network? I'd try logon scripts since that's easier.
>
> Do you lose connections if you remap the shares with the IP addresses of
the
> server rather than the name of the server? ie- \\192.168.1.2\share rather
> than \JJ-Server\share. If you stop losing the connections when you may
have
> a WINS problem.
>
> --
> Scott Baldridge
> Windows Server MVP, MCSE
>
>
> "J Jones"
> > This is a deplyment and setup issue. This is a new install of 2000
> Server.
> >
> > The error does not happen on all the clients. Currently only two are
> > getting this regularly. One is running WinME the other is Win98.
> > Occasionally another 98 system will get locked out as well.
> >
> > I do not have the exact error message in front of me, but when they
first
> > experience the loss the message deals with the loss of the share. The
> drive
> > is not accessible.
> >
> > When you just log off and then log back on the same message occurs.
> >
> > The system must be restarted to gain access to the shares again.
> >
> > What is strange about this is that one of the users was out for about a
> week
> > and during her illness the rate that this occured dropped drastically.
> The
> > ME machine losses connection about once a day, the 98 system losses
> > connection about once a week if that. The other 98 system has since
then
> > been upgraded to XP and that has not lost connection. It looks like
this
> > may be an ME problem rather than a server problem, but I am trying to
> > eliminate all the possiblilites.
> >
> >
> >
>
>

Hi Oli,

You are right about the caching names, but lots of things can mess it up and
if there is no WINS server to keep it straight ..., also if machines get
removed from one domain and added to another I've seen name resolution get
screwed up. Lots a things can happen in a workgroup environment too.

I agree about the 9x client thing... we still have plenty of them, and
plenty of OS7 through 9 Macs too. We have about 3200 machines in our school
district, about 60% are 2000 or XP, the rest are 9x/mac. It's getting
better, but not fast enough for us IT folks.

--
Scott Baldridge
Windows Server MVP, MCSE

> That crossed my mind, but once the name's been resolved, it should be
cached
> by the WINS client, shouldn't it?
>
> Therefore, either the drive would map or it wouldn't. You wouldn't expect
> connections to just drop.
>
> Still, I draw the line at helping people to run WIndows 98/ME in a
business
> environment. It wouldn't be doing them any favours.
>
> Cheers
>
> Oli
>