XP SP2 - 3019 event in event log...

  • Thread starter Thread starter Brad
  • Start date Start date
B

Brad

*** I posted this earlier, but didn't get a response,
trying again***

I've been testing Windows XP SP2 on our network, and for
the most part, everything seems okay. I disabled the
firewall since we have a hardware firewall on our
perimeter. This will 'fix' a lot of the problems related
to XP I assume.

One problem I have noticed is constant 3019 errors in the
event log (referencing mrxsmb error). This happnens
every time I try to access a remote drive (mapped). I
read in the KB that XP gives this error from time to
time, but I never had this problem before.

Any suggestions?

Thanks in advance
 
Error Message: The Redirector Failed to Determine the Connection Type
http://support.microsoft.com/?kbid=315244

And possibly:

Programs that connect to IP addresses that are in the loopback address range
may not work as you expect in Windows XP Service Pack 2
http://support.microsoft.com?kbid=884020
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

Are You Ready for WinXP SP2?
http://support.microsoft.com/default.aspx?pr=windowsxpsp2

What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/devioussoftware.mspx

AumHa Forums
http://forum.aumha.org
 
Don't woory about, it's FYI.
It means that you are probably running netbios over
tcp/ip (find check boxs under advanced tap in network
stuff.)

It means the redirector can not determines the speed or
type of connection because the netbios is in side a
tcp/ip paket.

It will only occur the first time the share is make or
wake up from hibernation.

So if you have 3 P/C with two Shared Document folders and
each user clicked on the other two, ewww, math
You get the point. :)

But it still works. Logging can't be to granular or why
have it. :)

SJ
 
This warning does not occur when you map a drive to the local PC, but when
you map the same drive to the same share on the same PC more than once.
Mapping a drive to the same PC from where it is mapped does not cause these
warning, but instead mapping it more than once does. Windows would realize
two things when mapping the drive the second time:
-This drive letter already exists.
-The share where the "new" mapping wants to point to is already mapped to a
drive letter. Hence, the redirector fails to determine the connection type.
To conclude, this is a logic error, not a system error. This error can be
safely ignored.


www.helpline4it.com
The Best IT Community Portal!
www.helpline4it.com
-----------------------------------
 
Back
Top