> >> As it turned out, Dejan had the username configured improperly. > > >> > > >> I added some more info here: > > >> > > >> > > > http://wpkg.org/FAQ#WPKG_Client:_I_configured_WPKG_Client_to_access_a_n > > >> etwork_path_as_.22user.22_-_it_doesn.27t_work._Why.3F > > > > > > > > > I'll try that, but it's kind of weird that the configuration you > saw > > only > > > creates problem on 4 PC's and on the rest of them (24) works OK. > > > > > > Thanks for your help. > > > > Maybe these other hosts are allowed to access this share regardless > of > > the > > user/password? > > > > It's easiest to verify it in Samba logs for a given host (log level = > > 3) - > > when the workstation connects, Samba will log which user attempts to > > access the share, and an error if it exists. > > > > Comparing log for a workstation which works with a log for a > > workstation > > which doesn't work should give you some ideas. > > > > Anyway, accessing the network share as a user with no "DOMAIN\..." is > > not > > supported. Maybe we could add some automatic expansion in WPKG > Client, > > because it confuses some users right now. > > > > > Well first I changed the profile from test to my default profile and rebooted the PC: I got the same error "The network location cannot be reached". The samba share is world readable and all wpkg clients are using the same username to access wpkg share. Browsing samba log as you suggested revealed nothing. I compared the logs from those clients that connect with those that don't and I couldn't see anything different. Thanks Dejan
------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/wpkg-users
