Re: I really screwed up this time!
From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 09/24/05
- Next message: SteveE: "Using ShellExecute"
- Previous message: Lanwench [MVP - Exchange]: "Re: I really screwed up this time!"
- In reply to: R. P.: "Re: I really screwed up this time!"
- Next in thread: R. P.: "Re: I really screwed up this time!"
- Reply: R. P.: "Re: I really screwed up this time!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 24 Sep 2005 13:21:05 -0400
In news:pdKdna0qptrG-K_eRVn-iw@comcast.com,
R. P. <r_pol12gar@hotmail.com> typed:
> "Malke" <notreally@invalid.com> wrote:
>> Once you've logged in using your domain account (using cached
>> credentials), and have an IP address on the home network, you can map
>> drives, use printers, whatnot, very easily - one way, in a command
>> line:
>>
>> net use x: \\computername\sharename /user:computername\username
>> <enter>
>>
>> MS KB article about the Net Use command - http://tinyurl.com/3bpnj
>
> Well, I tried this but when I am logged into my domain account
> (through VPN) I can't even ping my desktop PC to which the printer is
> attached.
They probably disable all non-VPN traffic when the tunnel is established
('use remote gateway') which is a very good idea from a security standpoint.
I do the same.
> I can ping it though when I am not in my domain account
> (the VPN tunnel is out)
Right.
> but the net use command still would give me
> the following result: --------------------------------------
> net use * \\MAINPC\LaserPrtr
> The password is invalid for \\MAINPC\LaserPrtr
> Enter the user name for 'MAINPC' : Boss
> Enter the password for MAINPC:
> System error 66 has occured.
>
> The network resource type is not correct.
Why the asterisk? Normally, with Windows network printing, you connect
directly to the shared printer. If you want to spoof it into using an LPT
port, you'd use
net use lpt1: \\computer\printershare
anyway.
> ---------------------------------------
>
> I might add that prior to the above command I did make the printer
> attached to my desktop PC (MAINPC) shareable with the printer under
> the LaserPrtr share name.
> This is really frustrating and I am not even a computer illiterate
> person. I just use Unix more than Windows and I don't have time to
> research and read long tutorials on how to connect printers to
> computers on the local network. Something like this used to be much
> more intuitive in WinME, without all this "net use" stuff.
>
> Rudy
The issue isn't really a technical one, at bottom, I'm afraid. Can you
locally attach your printer to your laptop temporarily so you can print
while using VPN?
- Next message: SteveE: "Using ShellExecute"
- Previous message: Lanwench [MVP - Exchange]: "Re: I really screwed up this time!"
- In reply to: R. P.: "Re: I really screwed up this time!"
- Next in thread: R. P.: "Re: I really screwed up this time!"
- Reply: R. P.: "Re: I really screwed up this time!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|