General discussion

Locked

persistent mappings disconnect on reboot

By GregSH ·
I have a DOS program that requires lpt1 be mapped to the network printer port (set up on an NT print server as an LPR port). I used the command "net use /persistent:yes" before mapping lpt1 on these workstations, which should make all subsequent mappings persistent.

However, two of the three NT workstations (sp4) running the program are presenting a message on reboot that the share name could not be found as it attempts to remap the port. When the user can't print and I type "net use", lpt1 is listed as disconnected. When I delete the mapping and remap lpt1, the user can print from the DOS program again until they restart. Each of the troubled pcs (and the working pc) print to a different Xerox DP N4025 printer using a PCL6 driver.

There are no typos--I wouldn't get a successful mapping in the first place if that were the case. I made sure I used the same case as the share(I don't think net use commands are case sensitive but I tried it anyway without success). I can duplicate the problem on my NT workstation as well. What's going on? And what settings on the working pc should I be comparing with the other two? I can't help but think I'm missing something basic.

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

persistent mappings disconnect on reboot

by dheupel In reply to persistent mappings disco ...

Set the Xerox printer up as a network printer in NT Server, then on the workstations, install the shared printer (queue) and then capture LPT1 to the shared printer. Why fuss with NET USE on command line?

Collapse -

persistent mappings disconnect on reboot

by GregSH In reply to persistent mappings disco ...

I've captured lpt1 on the win95 machines through the printer properties, but it can't be done from NT printer properties--I can only select one of the LPR ports set up on the print server. How do I capture lpt1 without the net use command? The only way I know is to set it up as a local printer.

Collapse -

persistent mappings disconnect on reboot

by dheupel In reply to persistent mappings disco ...

Are there any spaces in the printer's share name, and have you tried reapplying the service pack to the affected workstations?

Collapse -

persistent mappings disconnect on reboot

by GregSH In reply to persistent mappings disco ...

Poster rated this answer

Collapse -

persistent mappings disconnect on reboot

by rick_b In reply to persistent mappings disco ...

The best way to capture a port for a DOS based program is to build a .BAT file and put the shortcut in the client start up folder. We do this all the time on our network.

GO to DOS and at C prompt type
COPY CON
Hit enter
Type REM This is a client printer cpature
Type CAPTURE P=[your printer]L=1 NB NFF
Then hit the CTRL key and the Z key
This will save it to C: drive and then copy to the startup folder in Windows.
Email me if you need a copy of the bat file

Collapse -

persistent mappings disconnect on reboot

by rick_b In reply to persistent mappings disco ...

I re read your question and the above may not work,(to bad we can't delete our answers)

but I had this problem once and found that I didn't have NetBEUI installed and the disconnect was caused by a NETBIOS problem. Once I installed NetBEUI and TCP/IP, The problem went away. I kept the printer on TCP/IP, just added NETBEUI to the protocol stack on the client.

Collapse -

persistent mappings disconnect on reboot

by GregSH In reply to persistent mappings disco ...

Poster rated this answer

Collapse -

persistent mappings disconnect on reboot

by GregSH In reply to persistent mappings disco ...

This question was closed by the author

Back to Networks Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums