Logon Script Hangs


G

Guest

Various users sporatically are getting the following message when the Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending on the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N) [N]:

I have tried various forms of the logon script to force the user not to have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB
 
Ad

Advertisements

P

Pegasus \(MVP\)

MTB said:
Various users sporatically are getting the following message when the Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending on the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N) [N]:

I have tried various forms of the logon script to force the user not to have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB

Try this:

net use /persistent:no
net use * /delete /yes

The first command will prevent old connections from
being remembered. The second command will knock
out all old connections. After a week or two you can
remove both commands.
 
G

Guest

So should my logon script look something like this:

net use * /delete /yes
net use h: \\bbmdnas\home\%username% /persistent:no
net use l: \\bbmdnas\data /persistent:no
net use p: \\bbmdnas\apps /persistent:no
net use q: \\bbmdnas\data /persistent:no
net use t: \\bbmdtnb\cpas /persistent:no
net use r: \\bbmdtnb\audit /persistent:no

Thanks,

MTB

Pegasus (MVP) said:
MTB said:
Various users sporatically are getting the following message when the Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending on the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N) [N]:

I have tried various forms of the logon script to force the user not to have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB

Try this:

net use /persistent:no
net use * /delete /yes

The first command will prevent old connections from
being remembered. The second command will knock
out all old connections. After a week or two you can
remove both commands.
 
P

Pegasus \(MVP\)

No. The first command should be
net use /persistent:no
as suggested before. Subsequent commands do
not require the /persistent switch.


MTB said:
So should my logon script look something like this:

net use * /delete /yes
net use h: \\bbmdnas\home\%username% /persistent:no
net use l: \\bbmdnas\data /persistent:no
net use p: \\bbmdnas\apps /persistent:no
net use q: \\bbmdnas\data /persistent:no
net use t: \\bbmdtnb\cpas /persistent:no
net use r: \\bbmdtnb\audit /persistent:no

Thanks,

MTB

Pegasus (MVP) said:
MTB said:
Various users sporatically are getting the following message when the Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending on the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N) [N]:

I have tried various forms of the logon script to force the user not
to
have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB

Try this:

net use /persistent:no
net use * /delete /yes

The first command will prevent old connections from
being remembered. The second command will knock
out all old connections. After a week or two you can
remove both commands.
 
G

Guest

Ok, but what is confusing to me is that I thought that by having the "delete"
line at the bottom of the script, it would delete everything that was just
mapped???

net use /persistent:no
net use * /delete /yes

Thanks for being patient with one that knows so little.

Matthew

Pegasus (MVP) said:
No. The first command should be
net use /persistent:no
as suggested before. Subsequent commands do
not require the /persistent switch.


MTB said:
So should my logon script look something like this:

net use * /delete /yes
net use h: \\bbmdnas\home\%username% /persistent:no
net use l: \\bbmdnas\data /persistent:no
net use p: \\bbmdnas\apps /persistent:no
net use q: \\bbmdnas\data /persistent:no
net use t: \\bbmdtnb\cpas /persistent:no
net use r: \\bbmdtnb\audit /persistent:no

Thanks,

MTB

Pegasus (MVP) said:
Various users sporatically are getting the following message when the
Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending on the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N) [N]:

I have tried various forms of the logon script to force the user not to
have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB

Try this:

net use /persistent:no
net use * /delete /yes

The first command will prevent old connections from
being remembered. The second command will knock
out all old connections. After a week or two you can
remove both commands.
 
P

Pegasus \(MVP\)

net use /persistent:no
net use * /delete /yes
net use s: \\SomeServer\SomeShare
net use t: \\SomeServer\OtherShare
net use u: \\SomeServer\ThirdShare

Delete the first two lines after two weeks.


MTB said:
Ok, but what is confusing to me is that I thought that by having the "delete"
line at the bottom of the script, it would delete everything that was just
mapped???

net use /persistent:no
net use * /delete /yes

Thanks for being patient with one that knows so little.

Matthew

Pegasus (MVP) said:
No. The first command should be
net use /persistent:no
as suggested before. Subsequent commands do
not require the /persistent switch.


MTB said:
So should my logon script look something like this:

net use * /delete /yes
net use h: \\bbmdnas\home\%username% /persistent:no
net use l: \\bbmdnas\data /persistent:no
net use p: \\bbmdnas\apps /persistent:no
net use q: \\bbmdnas\data /persistent:no
net use t: \\bbmdtnb\cpas /persistent:no
net use r: \\bbmdtnb\audit /persistent:no

Thanks,

MTB

:


Various users sporatically are getting the following message when the
Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending
on
the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N) [N]:

I have tried various forms of the logon script to force the user
not
to
have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB

Try this:

net use /persistent:no
net use * /delete /yes

The first command will prevent old connections from
being remembered. The second command will knock
out all old connections. After a week or two you can
remove both commands.
 
Ad

Advertisements

G

Guest

Ok, I think I have it now. I will run this for a while and post the results.

Thanks for your help.

MTB

Pegasus (MVP) said:
net use /persistent:no
net use * /delete /yes
net use s: \\SomeServer\SomeShare
net use t: \\SomeServer\OtherShare
net use u: \\SomeServer\ThirdShare

Delete the first two lines after two weeks.


MTB said:
Ok, but what is confusing to me is that I thought that by having the "delete"
line at the bottom of the script, it would delete everything that was just
mapped???

net use /persistent:no
net use * /delete /yes

Thanks for being patient with one that knows so little.

Matthew

Pegasus (MVP) said:
No. The first command should be
net use /persistent:no
as suggested before. Subsequent commands do
not require the /persistent switch.


So should my logon script look something like this:

net use * /delete /yes
net use h: \\bbmdnas\home\%username% /persistent:no
net use l: \\bbmdnas\data /persistent:no
net use p: \\bbmdnas\apps /persistent:no
net use q: \\bbmdnas\data /persistent:no
net use t: \\bbmdtnb\cpas /persistent:no
net use r: \\bbmdtnb\audit /persistent:no

Thanks,

MTB

:


Various users sporatically are getting the following message when the
Domain
Logon Script runs:
There are open files and/or incomplete directory searches pending on
the
connection to h:
Is it OK to continue to disconnecting and force them closed? (Y/N)
[N]:

I have tried various forms of the logon script to force the user not
to
have
to deal with this. The scripts and its variations are below:

Original Version:

net use h: /delete
net use h: \\bbmdnas\home\%username%


Verions 2:

net use h: \\bbmdnas\home\%username% /y /persistent:no


Verision 3:

net use h: /delete
net use h: \\bbmdnas\home\%username% /persistent:no

Anybody have any idea how to fix or bypass this error message?

Thanks,

MTB

Try this:

net use /persistent:no
net use * /delete /yes

The first command will prevent old connections from
being remembered. The second command will knock
out all old connections. After a week or two you can
remove both commands.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top