Sys error 1219 - why Windows auto connect?

  • Thread starter Thread starter Paul Kraemer
  • Start date Start date
P

Paul Kraemer

Hi,
I have several Win2k pro PC's in a small peer-to-peer
network. One of these PC's acts as a file server. All
the other PC's have a .bat file in the startup folder
that has the following command.

net use w:
\\FileServer\Sharename /user:FileServer\netuser password

....this way, users of these other pc's can access the
share using the 'netuser' account. This works for me
most of the time, but sometimes I get system error 1219 -
"The credentials supplied conflict with an existing set
of credentials."

This is always because the user is already logged on to
this share as someone other than 'netuser'. I can see
that this is true if I type 'net use' at the command
prompt - I can see the existing connection. I can get
around this by manually entering the following at the
command prompt...

net use \\FileServer\Sharename /delete

....after this, my startup batch file works fine. I would
like to make my startup batch file to work at startup all
the time without my intervention. I think Windows must
be automatically forming a connection to this share
before my .bat file can run. I'm just wondering where I
can look to see why Windows is creating this connection
and hopefully prevent it from happening.

Any input will be appreciated.

Thanks,
Paul
 
Hi,
I have several Win2k pro PC's in a small peer-to-peer
network. One of these PC's acts as a file server. All
the other PC's have a .bat file in the startup folder
that has the following command.

net use w:
\\FileServer\Sharename /user:FileServer\netuser password

...this way, users of these other pc's can access the
share using the 'netuser' account. This works for me
most of the time, but sometimes I get system error 1219 -
"The credentials supplied conflict with an existing set
of credentials."

This is always because the user is already logged on to
this share as someone other than 'netuser'. I can see
that this is true if I type 'net use' at the command
prompt - I can see the existing connection. I can get
around this by manually entering the following at the
command prompt...

net use \\FileServer\Sharename /delete

...after this, my startup batch file works fine. I would
like to make my startup batch file to work at startup all
the time without my intervention. I think Windows must
be automatically forming a connection to this share
before my .bat file can run. I'm just wondering where I
can look to see why Windows is creating this connection
and hopefully prevent it from happening.

Any input will be appreciated.

Thanks,
Paul
Click to expand...
why not just use the batch to first kill any possible connections,
then establish your preferred connection?


you can also net use /PERSISTENT: NO to prevent windows from attempting to
recconect to the network share at boot.
 
I actually do use the /PERSISTENT: NO switch in my net
use statement, so I think something other than my batch
file is causing the connection to be made.

When my batch file works, if I type 'net use' to list the
open connections, I see "Remote" listed
as "\\FileServer\ShareName" and "Local" is listed as "W:"
(my mapped drive letter)

When my batch file does not work, 'net use' still shows
remote as "\\FileServer\ShareName", but "Local" is blank.

I will try your suggestion of puttin the "net
use ... /delete" statement before my "net use w: ... "
statement to try to delete any existing connections
first. I am just curious what is making this initial
connection.

Thanks again,
Paul
 
I actually do use the /PERSISTENT: NO switch in my net
use statement, so I think something other than my batch
file is causing the connection to be made.

When my batch file works, if I type 'net use' to list the
open connections, I see "Remote" listed
as "\\FileServer\ShareName" and "Local" is listed as "W:"
(my mapped drive letter)

When my batch file does not work, 'net use' still shows
remote as "\\FileServer\ShareName", but "Local" is blank.

I will try your suggestion of puttin the "net
use ... /delete" statement before my "net use w: ... "
statement to try to delete any existing connections
first. I am just curious what is making this initial
connection.

Thanks again,
Paul




[quoted text muted] All
[quoted text muted] password
[quoted text muted] 1219 -
[quoted text muted] set
[quoted text muted] to
[quoted text muted] would
[quoted text muted] all
[quoted text muted] must
[quoted text muted] I
[quoted text muted] connection
[quoted text muted] connections,
[quoted text muted] from attempting to
[quoted text muted]
Click to expand...
Click to expand...

just a stab in the dark, but it sounds like another application could be
kicking in the net share???? don't know what could do this, but if the
local drive letter is not assigned, maybe an app that is mapped to that
drive as default is reconnecting...
 
just a stab in the dark, but it sounds like another application could be
kicking in the net share???? don't know what could do this, but if the
local drive letter is not assigned, maybe an app that is mapped to that
drive as default is reconnecting...
.
Click to expand...
I'll buy that, but how can I find out what app is doing
it? Whatever it is, it is doing it at startup, but not
100% of the time because sometimes my 'net use w: ...'
statement works. Maybe this just depends on the timing
of what runs first - my .bat file or this mystery app.

I know that I can type 'net use' to see that the
connection exists. Is there another command I can use to
see what exactly made the connection? Is there anything
I can log that would give me some insight?

Thanks again,
Paul
 
[quoted text muted] application could be
[quoted text muted] this, but if the
[quoted text muted] mapped to that
[quoted text muted]
Click to expand...
I'll buy that, but how can I find out what app is doing
it? Whatever it is, it is doing it at startup, but not
100% of the time because sometimes my 'net use w: ...'
statement works. Maybe this just depends on the timing
of what runs first - my .bat file or this mystery app.

I know that I can type 'net use' to see that the
connection exists. Is there another command I can use to
see what exactly made the connection? Is there anything
I can log that would give me some insight?

Thanks again,
Paul
Click to expand...
I suppose you've looked at which PC's this error occurs on? IE: if it
happens consistently on one but not the other, and there is a different
program running on the guilty one....

a netstat will give you protocol information and show you which network
resources are accessed via which ports, etc...this may give you something
you can work with.
 
Back
Top