Kitz Forum

Computer Software => Windows => Topic started by: broadstairs on November 05, 2008, 09:39:01 AM

Title: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: broadstairs on November 05, 2008, 09:39:01 AM
On my XP system just recently I have found that my mapped network drives have recently stopped reconnecting at boot up. This seems to have happen in the past week or so probably since doing a Windows Update. I know that there was a recent fix for some high risk problem which I think (if memory serves me) was network related. Has anyone else seen this? Prior to this I've not had any problems withn the drives reconnecting at logon.

Update - turned out that somehow the option in 'Folder Options - View - Automatically search for network folders and printers' had been turned off. Now its on all is OK and drives reconnect at boot/logon.
Title: Re: Solved - Problem with mapped network drives not reconnecting at boot up on XP
Post by: kitz on November 05, 2008, 11:45:08 PM
Glad you found out what it was :)
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: broadstairs on November 06, 2008, 08:39:01 AM
This moring I discovered that my networked drives had NOT been reconnected. Yesterday I did reboot and they came back just fine but this morning after boot up they were strill disconnected. The Folder option was still set just as it should be. Still puzzling....
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: toulouse on November 06, 2008, 08:54:15 AM
Don't know if this is the same problem, but.........

I sometimes get a similar message about Windows being unable to attach Network drives which relate to the memory card slots in my HP OfficeJet printer.

As far as I can recall, I have NEVER used those memory card slots, so I don't know why it's an ISSUE for Windows, temperamental B*tch that she is.

I also don't like to point the finger, but I think I'm right in saying that this first started after I had tried (unsuccessfully) to install XP SP3, as did a number of other strange things on my system.


Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: Anne r on November 19, 2008, 06:09:18 PM
Check the Workstation service is running ok, -start up type automatic
 :)

Also, have read that the TCP/IP NetBIOS Helper service could help ..... if not running start it, -- set startup type as automatic too.

Hope it helps,


Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: broadstairs on November 19, 2008, 08:35:20 PM
Check the Workstation service is running ok, -start up type automatic
 :)

Also, have read that the TCP/IP NetBIOS Helper service could help ..... if not running start it, -- set startup type as automatic too.

Hope it helps,




Both started and set on automatic already, and no it still does not work.

I'm convinced SP3 changed something because it always did work for ages....
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: toulouse on November 19, 2008, 09:12:16 PM
Yes, I also think it's SOMETHING that has happened since I first tried to install SP3.

It's not actually causing me a problem as such, but it would be nice to know how to stop it happening.

I think it's a YYGT !!!!


TTFN


Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: broadstairs on November 19, 2008, 10:53:23 PM
YYGT !!!!

Its a long time since I've seen that phrase being used..... first heard it over 30 years ago and yes it was in IT  ;D
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: toulouse on November 20, 2008, 07:22:17 AM
Yes, IT is my background as well. I worked in Data Processing / IT (same thing basically) at NatWest between 1970 to 1991.

YYGT was a term used by the the real techies when there was a problem for which they didn't have an immediate answer, and as some of you may be aware it stands for 'Yeah, You Get That'. Not sure, but I suspect it may have been an IBM'ism along the same lines as 'FUBAR'.
I think many of the issues with Windows could be described as YYGTs, certainly this network drive reattachment thing is one of them. Would be nice to know how to resolve it though.


TTFN


Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: broadstairs on November 20, 2008, 08:11:24 AM
Yes, IT is my background as well. I worked in Data Processing / IT (same thing basically) at NatWest between 1970 to 1991.

YYGT was a term used by the the real techies when there was a problem for which they didn't have an immediate answer, and as some of you may be aware it stands for 'Yeah, You Get That'. Not sure, but I suspect it may have been an IBM'ism along the same lines as 'FUBAR'.
I think many of the issues with Windows could be described as YYGTs, certainly this network drive reattachment thing is one of them. Would be nice to know how to resolve it though.


TTFN




Well that's interesting I worked for IBM from 1966 to 2002 when they made me an offer I could not refuse, and during that time one of the client's I worked with extensively on and off was Nat West, mainly in London but I did visit Kegworth on more than one occasion! I remember we often used the YYGT phrase in technical review meetings when appropriate.  ;D
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: Pwiggler on November 20, 2008, 08:14:13 AM
have you tried deleting the network drives and recreating them??
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: broadstairs on November 20, 2008, 08:30:49 AM
have you tried deleting the network drives and recreating them??


Yes, more than once.....
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: toulouse on November 20, 2008, 09:42:57 AM
Ok Stuart, let's try and get to the bottom of this annoying problem. As you may have gathered, I also get this problem occasionally, and as far as I can recall it started after I had tried to install XP SP3. The network drives concerned on my system are two memory card slots built into my HP Officejet printer. My system is a Packard Bell Imedia 1208 (or something like that). In my case, it doesn't appear to cause a major problem because if I look at My Computer after system startup the memory card on HP shows as available / active.

As I said, I get this problem from time to time, with no discernible pattern, hence my earlier suggestion that it was a YYGT.

TTFN


Mick

 
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: broadstairs on November 20, 2008, 10:33:43 AM
Mick probably 80% or more of the time the drives which are hard disks on another PC which runs 24x7 using W2K, I'm sure all this started after SP3 or perhaps a subsequent M$ update and now usually show as disconnected. They always used to come up OK.  They also active OK as soon as I click on them. I noticed the problem when an application failed because they were no there. I've bypassed the problem with the application by specifying them as network drives rather than their connected drive ID letter. I've tried all sorts of things to get them to come up. One thing which has been suggested is that the network comes up too late in the boot process for them to reconnect, but always in the past when either network or rarely the other PC was not there and pretty sure I used to have had a message from XP saying do you want to reconnect these drives next time.

Right now I cannot think of anything else to try.
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: guest on November 20, 2008, 10:35:50 AM
Do you actually need them mapped or is it just for convenience?

I only ask as I realised last year that I was mapping drives out of habit rather than necessity (can't remember the last time a program actually needed a drive letter) and yes I used to get the same intermittent problem.

If its just for convenience then just create a shortcut to the network path on the desktop - or create a folder on the desktop with all the shortcuts in it, which is what I do for media files stored on the network.
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: toulouse on November 20, 2008, 11:22:56 AM
@rizla -

not too sure what you are asking as, to the best of my knowledge, I have never actually done anything to cause mapping of these drives. I think it's all done by Windows XP - or am I wrong. In addition to the two memory card slots on my HP OfficeJet, I also have a multi card reader attached via USB. Each of those show up as removable drives F:, G:, H: and I:, whereas the OfficeJet one shows up as 'memory card on HPxxxxxxxxxxxx Z:' (xxxxxxxxxxxx is the Ethernet address of the Officejet printer). I've never inserted a memory card into either slot in the OfficeJet, and I only actually power the printer up when I intend to do any printing; maybe that's related to my  problem.

I sure would like to know for sure though, as I don't like things happening which can't be explained, in other words I don't like YYGTs.

TTFN



Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: Pwiggler on November 20, 2008, 11:42:44 AM
toulouse - do you get this problem the next reboot after using your printer??

if you do it because xp has found the 'drives' (card reader) on the printer and is expecting to see them on the next boot.

if the printer is off then obviously xp wont find the drives??
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: toulouse on November 20, 2008, 12:58:50 PM
Hey pwiggler, that could well be the problem. It's not a big deal for me, but I will conduct a small test and come back and let you know the outcome.

TTFN


Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: broadstairs on November 20, 2008, 01:12:19 PM
Yes I think we have different problems as my disks are on another PC not a printer.
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: Pwiggler on November 20, 2008, 03:13:16 PM
broadstairs - system restore back to a time when it worked ok, test, then keep an eye on what M$ updates are being installed??
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up o
Post by: guest on November 21, 2008, 07:53:16 AM
I doubt that will work as I remember seeing this problem first around the time Windows 2000 came out, so I reckon the updates are a red herring....
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: jabns on December 13, 2008, 09:46:18 AM
I would first check for services that sound like they may have something to do with networking or authentication that are set to manual and try setting them to automatic and see if that makes it work (start > run > services.msc). If its the same problem I used to have one of the services was set to manual but when I double clicked the drive it would reconect because it enabled the service.

It might also be a group policy setting that some software has enabled(I will have a quick search now). Did you install any software before this happened like AV or Firewall in particular?
Title: Re: Not Solved - Problem with mapped network drives not reconnected at boot up on XP
Post by: Anne r on December 13, 2008, 11:00:22 PM
What about the SSDP Discovery Service, Looks for Universal Plug and Play drives on your network

...set start up type to automatic.