elmago
asked on
net use
When I execute a batch command, with the folowing sentence
net use /persistent:no
net use * /delete /y
net use LPT1 \\name_pc\shared_prt /user:domain\administrator
the connection produce ok and is connected status, but after one hour or sometimes less minutes, when you check typing at the command prompt net use, appears with the status disconnected lpt1 \\name_pc\shared_prt
and I want that it mantains the status in connected mode
Anyone can tell me any suggestions.
net use /persistent:no
net use * /delete /y
net use LPT1 \\name_pc\shared_prt /user:domain\administrator
the connection produce ok and is connected status, but after one hour or sometimes less minutes, when you check typing at the command prompt net use, appears with the status disconnected lpt1 \\name_pc\shared_prt
and I want that it mantains the status in connected mode
Anyone can tell me any suggestions.
ASKER
Yes, I tried with that option, now is running with that option bit the problem is the same.
While you want a persistent:yes to maintain across logins, I suspect you are left helpless during session.
MS OS has a tendency for both losing connections and for taking too long to find out if they remain. (seemingly opposite). I dunno, but I suspect your use of batch file is best approach, for command line method, for it is easy enough to rerun. But I ponder the need.
Why not use Windows Explorer to manage your shared devices? This, in NT seems easier to do for maintaining shared areas. Then things like syntax are more obvious, and networking of shares provides colors (red = disconnected) to give you a visible feedback on networking. By this one could perhaps isolate timing of an initial problem on the share, and the reason it began (perhaps recycled or out of paper? Or offline too long?)
MS OS has a tendency for both losing connections and for taking too long to find out if they remain. (seemingly opposite). I dunno, but I suspect your use of batch file is best approach, for command line method, for it is easy enough to rerun. But I ponder the need.
Why not use Windows Explorer to manage your shared devices? This, in NT seems easier to do for maintaining shared areas. Then things like syntax are more obvious, and networking of shares provides colors (red = disconnected) to give you a visible feedback on networking. By this one could perhaps isolate timing of an initial problem on the share, and the reason it began (perhaps recycled or out of paper? Or offline too long?)
ASKER
About this suggestion, the requerimient to map the printer with the batch file, is mandatory to execute some functions of a System of third parts.
If I use the map with windows explorer to manage my shared devices, dont function that System, because the system search a port LPT1, it dont understand the shared name.
Thank you.
If I use the map with windows explorer to manage my shared devices, dont function that System, because the system search a port LPT1, it dont understand the shared name.
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
after some tests it functions ok.
net use LPT1 \\name_pc\shared_prt /user:domain\administrator
It should stay connected.