pavallokazzo

Sry guys... the rush... just restart and it will release the keys

I've noticed that know I can't log in using a different user... If I use another user it won't ask for the password, seems like it's cached somewhere... How can I release those password saved? any help? thanks

DID IT! You have to first authenticate then open the connection to the shares: net use \\server /user:%user% %pass% net use Z: \\server\private net use Y: \\server\public Plz notice that the public share connection is mapped to guest (using samba on debian, linux), so every connection on that share will be open as a guest user.

I'm sure I am using the right credentials and sure I don't have any other connection opened... However: - this script on win xp DOES work - As I've already saved I've added at the script net use * /delete before the connection to be sure "connection table" was "free" Do anybody knows how can I traceback this error on vista? Like logs, advice etc etc...? Thanks

Hello everybody! I need an help on Vista. I've got a script that connects a vista machine at 2 shares, one public and the other private set user= set pass= net use z: \\server\public if not defined %user% set /p user=Username: net use y: \\server\private /u:%user% %pass% Now who use this script can complete the declaration of variables to auto-login at runtime instead of having to give the "keys" during the script execution. You can reuse it if you want More it creates 2 connections: - public (that's just guest: users are mapped to guest account) - private (it's a folder for every user, given the right credentials the server will open connection to your private folder) On win xp this script DOES works. On Vista instead it will lead everytime to error 1219 I've tried adding a net * /delete before the script, restart the computer etc etc but nothing came out. Still 1219. Any solutions? Do I have to use the "net use \\IP" trick? Is there a way to get by script the IP address from a NBT name? Also on the server-side (is a Linux-Samba machine but that's the same cause I've noticed this also happen on Windows) if I launch smbtree (to get a "tree-view" of the machine+share in the network) every time, for every machine, it tries to get share's list from 192.210.85.something while my network it's in a classic 192.168.0 environment. Result of this operation is always a timeout (the other side didn't respond). What can be this? Maybe we are using an outside WINS server? Or are we under attack?!?!? HELP! Thanks.