shares to a minlogon

[Guest]

hi

I'm having trouble mapping network locaions to drive letters in my minlogon. The "Workstation Service" component is in the configuration, but when I type to the console:

net use x: "\\MyComputer\MyShare"

I get: "The Workstation service has not been started"

I checked my CurrenControlSet\Services in regedit and found that lanmanworkstation was missing, although lanmanserver was present but empty (no values).

Also in my configuration: "Credential Management User Interface". TCP/IP works fine.

any suggestions?

thanks,
idan

 

[KM]

idan,

Is "Workstation Service" component in your image? If not, add it.
If yes, check you FBALog.txt file for any related errors. Also, you may try
"net start" command to start the service (or see any problem if it errors).

--
KM,
BSquare Corporation

hi

I'm having trouble mapping network locaions to drive letters in my

minlogon. The "Workstation Service" component is in the configuration, but
when I type to the console:

I get: "The Workstation service has not been started"

I checked my CurrenControlSet\Services in regedit and found that

lanmanworkstation was missing, although lanmanserver was present but empty
(no values).

 

[KM]

Forgot to mention. Make sure "Client for Microsoft Networks" component is
also included.

 

[Harsh Shah [MS]]

Make sure you add "TCP/IP Networking with File Sharing and Client for MS
Networks". The dependencies most probably include "NetBios over TCP/IP" but
just to make sure add that one too.

 

[Guest]

thanks for the replies.

I couldn't start the workstation service because it wasn't in the registry, so I imported the relevant registry keys and values from a regular XP install. when I 'net start'ed it gave a message that it was starting the service but then failed with an error number that after an internet search I found out it was related to a Redirector service.
When I tried "net start redirector" it complained that the workstation service did not start. bizzare.

"Net use" worked on one of my bigger configurations, so my guess is that it's one of the "microsoft network client" dependencies (I did not include some) that is missing. So, I am about to embark on a length process of elimination.

C'ya
idan