DOS Printing: System Error 66

I just replaced a WinXP laptop with a WinVista laptop. I was able to
print from DOS programs to a network printer on the XP machine via
'redirecting' LPT1 via the command

NET USE LPT1 \\servername\printername password /user:username

Using the same script on the new Vista laptop, however, gives me the

System error 66 has occurred
The network resource type is not correct

response. This occurs regardless of whether I precede the correct
command with a precautionary 'delete'

NET USE LPT1 /delete

Any thoughts? Web based research turned up several dead ends.

Thanks,

Jim

Are you opening the command prompt with "Run as administrator"?
--
Paul


"Jimbo" wrote:

> I just replaced a WinXP laptop with a WinVista laptop. I was able to
> print from DOS programs to a network printer on the XP machine via
> 'redirecting' LPT1 via the command
>
> NET USE LPT1 \\servername\printername password /user:username
>
> Using the same script on the new Vista laptop, however, gives me the
>
> System error 66 has occurred
> The network resource type is not correct
>
> response. This occurs regardless of whether I precede the correct
> command with a precautionary 'delete'
>
> NET USE LPT1 /delete
>
> Any thoughts? Web based research turned up several dead ends.
>
> Thanks,
>
> Jim
>
>
>
>
>

On Wed, 18 Jul 2007 18:48:00 -0700, PaulB
<PaulB@discussions.microsoft.com> wrote:

>Are you opening the command prompt with "Run as administrator"?


Thanks for the response, Paul. I don't know the answer to that
question--I just checked, and my "Command Prompt" shortcut has all
options in the relevant tab ("Compatibility") greyed out.

FWIW, I am logged in as an administrator, and all of the other NET USE
commands succeed. (The "NET USE LPT1" command is part of a start-up
type batch file that I run manually when needed.)

Jim

Right click on the CMD shortcut and click on "Run as administrator" When the
Command Prompt opens the heading will be Administrator Command Prompt.
--
Paul


"Jimbo" wrote:

> On Wed, 18 Jul 2007 18:48:00 -0700, PaulB
> <PaulB@discussions.microsoft.com> wrote:
>
> >Are you opening the command prompt with "Run as administrator"?
>
>
> Thanks for the response, Paul. I don't know the answer to that
> question--I just checked, and my "Command Prompt" shortcut has all
> options in the relevant tab ("Compatibility") greyed out.
>
> FWIW, I am logged in as an administrator, and all of the other NET USE
> commands succeed. (The "NET USE LPT1" command is part of a start-up
> type batch file that I run manually when needed.)
>
> Jim
>
>
>
>

Thanks Paul. Doing this still gives me the error #66. Given that I'm
signed on as Administrator anyway, should I have expected different
results?

Jim



On Thu, 19 Jul 2007 13:40:02 -0700, PaulB
<PaulB@discussions.microsoft.com> wrote:

>Right click on the CMD shortcut and click on "Run as administrator" When the
>Command Prompt opens the heading will be Administrator Command Prompt.

I went back and reassigned LPT1 on my system and the only time I get that
error is when the servername\printername is wrong. I'm not sure what the
problem is.
--
Paul


"Jimbo" wrote:

> Thanks Paul. Doing this still gives me the error #66. Given that I'm
> signed on as Administrator anyway, should I have expected different
> results?
>
> Jim
>
>
>
> On Thu, 19 Jul 2007 13:40:02 -0700, PaulB
> <PaulB@discussions.microsoft.com> wrote:
>
> >Right click on the CMD shortcut and click on "Run as administrator" When the
> >Command Prompt opens the heading will be Administrator Command Prompt.
>
>

On Mon, 23 Jul 2007 10:46:03 -0700, PaulB
<PaulB@discussions.microsoft.com> wrote:

>I went back and reassigned LPT1 on my system and the only time I get that
>error is when the servername\printername is wrong. I'm not sure what the
>problem is.


Thanks PaulB. Here is the specific syntax, and as mentioned, it works
fine on my XP clients but does not work on my Vista clients. I've
tried adding colons, etc., to "LPT1", but I always get error 66. Is
it possible that the syntax has changed from XP to Vista? The 'net
use' help appears to be very similar between the two OSes.

Net Use LPT1 \\server2007\hp50000 password /USER:Administrator

Jim

Hi Jim,
The only part of the syntax that I'm not sure of is the password. I don't
use that.
You probalby know this but type net use /? and check it out. I wish I
could be of more help.
--
Paul


"Jimbo" wrote:

> On Mon, 23 Jul 2007 10:46:03 -0700, PaulB
> <PaulB@discussions.microsoft.com> wrote:
>
> >I went back and reassigned LPT1 on my system and the only time I get that
> >error is when the servername\printername is wrong. I'm not sure what the
> >problem is.
>
>
> Thanks PaulB. Here is the specific syntax, and as mentioned, it works
> fine on my XP clients but does not work on my Vista clients. I've
> tried adding colons, etc., to "LPT1", but I always get error 66. Is
> it possible that the syntax has changed from XP to Vista? The 'net
> use' help appears to be very similar between the two OSes.
>
> Net Use LPT1 \\server2007\hp50000 password /USER:Administrator
>
> Jim
>
>
>
>
>

Thanks Paul; it's not the first Vista bug I've encountered :-)



On Tue, 24 Jul 2007 15:24:03 -0700, PaulB
<PaulB@discussions.microsoft.com> wrote:

>Hi Jim,
>The only part of the syntax that I'm not sure of is the password. I don't
>use that.
>You probalby know this but type net use /? and check it out. I wish I
>could be of more help.

Has anyone EVER solved this problem? It is many months and a Vista
Service Pack later and this still seems to fail for me. This is a REAL
pain for me Thanks for any pointers.

Harvey


--
fishman@panix.com

So far the information you gave is not sufficient to even define your exact
problem, let alone try to find a solution. System Error 66 has several
possible causes, many related to network printing.
Since you did not give the conditions that exist when the error occurred,
all I can suggest is that you do is search the MSKB using Vista and system
error 66. At least half a dozen references were visible when I recently did
so. I should also mention that the search engine or the web site seemed to
be acting up a bit.

What printer make & model?
Which Vista version?
What are you doing when the error occurs?
Is there any reason why you are using "DOS" ? (Obsolete Application, etc)

"fishman@panix.com" <guest@unknown-email.com> wrote in message
news:30961bfb18d2e081d36856048db739dd@nntp-gateway.com...
>
> Has anyone EVER solved this problem? It is many months and a Vista
> Service Pack later and this still seems to fail for me. This is a REAL
> pain for me Thanks for any pointers.
>
> Harvey
>
>
> --
> fishman@panix.com

This is Vista32 Ultimate. Since I am trying to virtualize the printer so
that I can access it from a program written in C some twenty years ago
but still very useful, the details of the printer are not material to
the problem. But for the moment it is a Hewlett-Packard LJ2430 connected
via an Ethernet port. As to why DOS, I MUCH prefer working in a command
line environment rather than a GUI. I have been running programs in a
DOS emulator since I switched to Windows NT from OS/2. This has always
functioned in previous versions of Windows (NT4, 2000, and Xp) but
falls flat in Vista. The actual command line that I am trying is

net use lpt3: \\boink\lj2430

where BOINK is the actual machine name and lj2430 is the share name
assigned in the printer driver setup. This for the PCL6 personality of
the printer. I also have drivers installed for the PCL5 and PostScript
personalities, but they are not shared.

net view \\boink

shows lj2430 as a valid asset.

Now is that enough information about what I am trying to do and why? It
is extremely frustrating to not be able to access the printer from these
programs. Why am I getting System Error 66? And I do not seem to be
alone in this; Googling gives me lots of hits on people having the
problem, but seemingly none on solutions. Thanks for any help.

Harvey


Chuck;700770 Wrote:
> So far the information you gave is not sufficient to even define your
> exact
> problem, let alone try to find a solution. System Error 66 has several
> possible causes, many related to network printing.
> Since you did not give the conditions that exist when the error
> occurred,
> all I can suggest is that you do is search the MSKB using Vista and
> system
> error 66. At least half a dozen references were visible when I recently
> did
> so. I should also mention that the search engine or the web site seemed
> to
> be acting up a bit.
>
> What printer make & model?
> Which Vista version?
> What are you doing when the error occurs?
> Is there any reason why you are using "DOS" ? (Obsolete Application,
> etc)
>
> "fishman@xxxxxx" <guest@xxxxxx-email.com> wrote in message
> news:30961bfb18d2e081d36856048db739dd@xxxxxx-gateway.com...> > >
> > >
> > > Has anyone EVER solved this problem? It is many months and a Vista
> > > Service Pack later and this still seems to fail for me. This is a
> > REAL
> > > pain for me Thanks for any pointers.
> > >
> > > Harvey
> > >
> > >
> > > --
> > > fishman@xxxxxx > >


--
fishman@panix.com

[karrah2303]

I was getting the same error when I was trying to install a new network printer using a Vista machine. Ultimately what I had to do was plug in the printer to the network, go to the server, install the driver, then using the IP address of the printer, install the printer. Once that was installed, I shared the printer, then I went back to the Vista machine, used the net use lpt1 /delete command. Then I installed the printer to the local machine, and then went in and used the net use lpt1 \\location\printername.

Also, when I tried to do the run as administrator from Vista, I typed in net use to see my stats and it told me everything was unavailable. So I just went in normally and it worked perfectly.

Hope this helps.

KR