Re: [Wrapper-user] W2K Service Accessing Network share in non-domain environment (workgroup)

[Leif M. <le...@ta...>]

Dan,
    Network drives on Windows are always a bit finicky.   Usually you 
will want to start
by getting things working in console mode while logged in as the user 
you will be
running as as a service.   If it doesn't work in console mode then it 
will not work as a
service.

    When running as a service, you must specify a user to run as if you 
wish to access
network or printer resources.  It sounds like you have this part figured 
out however.

    I am surprised that you are not about to make things work when 
running in console
mode.  In every case that I have seen, if you can see a drive in the 
file explorer, you
can also see it when running under console mode.  This is because any 
such drive will
already be logged in and connected at that point.

    I have seen problems on system startup when referencing mapped 
network drives
while running as a service.   It appears that such drives are not always 
actually
mapped until an actual user logs on to the system.  This is not true on 
all systems.
But I have seen it on a customer's W2k system.
    The solution was to reference the drive using the direct 
//x.x.x.x/share format
as you appear to be doing.

    Other than that I don't have any other advice at this point other 
than to suggest
double checking the drive URIs and the login information.

    Post back if you get any more info.

Cheers,
Leif
   

Dan Feather wrote:

>Hello,
>    I have a W2k system that is unable to access a network share on
>another W2k system. Basically I try to list the files in
>"//x.x.x.x/share" and I get null back from the list() method. I ran into
>this at another location, and set the service up to run as a
>specific user, and that fixed the problem there. However, it isn't working
>this time. The one difference I know of at this location is that they
>don't use a domain.
>    The crazy thing is, the user we are running the service as (the local
>administrator account) can browse the share and all that good stuff. We
>did run the wrapper from the command line with the -c option logged in as
>the same user to see if that would help, but that didn't work either. Has 
>anyone run into anything like this before? If so, were you able to fix it
>or did you have to work around it somehow? I
>appreciate any help or condolences!
>
>--
>P.S. List Admin. Sorry for the double post. The first time I sent it I
>didn't realized I had subscribed with the wrong e-mail address.
>
>  
>