Re: Accessing Administrative Shares
From: Chris McKeown (Chris.McKeownNO@SPAMblueyonder.co.uk)Date: 09/23/02
- Next message: : "Re: Morpheus How can I stop it"
- Previous message: Chris McKeown: "Re: Accessing Administrative Shares"
- In reply to: Chris McKeown: "Re: Accessing Administrative Shares"
- Next in thread: Eric Torbenson: "Re: Accessing Administrative Shares"
- Reply: Eric Torbenson: "Re: Accessing Administrative Shares"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Chris McKeown" <Chris.McKeownNO@SPAMblueyonder.co.uk> Date: Mon, 23 Sep 2002 16:50:59 GMT
"Chris McKeown" <Chris.McKeownNO@SPAMblueyonder.co.uk> wrote in message
news:RzHj9.5497$zE4.52637903@news-text.cableinet.net...
> "Daniel Lohmann" <daniel@uni-koblenz.de> wrote in message
> news:9bguou80rr8houhh9t99j0bqdj1chqsgss@4ax.com...
> > On Mon, 23 Sep 2002 14:34:20 GMT, Eric R Torbenson
> > <ert1@nospam.optonline.net> wrote:
> >
> > net use \\192.168.47.11\C$ /U:Administrator
> >
> > would do it.
>
>
> You're damn right, that works like a charm!
And, in fact, so does using the FQDN of the server instead. I have a server
called mercury in a domain called solar.net:
Mapping to \\mercury\C$ and supplying admin credentials gives the error
previously described.
Whereas mapping to \\192.168.0.1\C$ works fine...
...and so does \\mercury.solar.net\C$
-- Regards,Chris McKeown.
- Next message: : "Re: Morpheus How can I stop it"
- Previous message: Chris McKeown: "Re: Accessing Administrative Shares"
- In reply to: Chris McKeown: "Re: Accessing Administrative Shares"
- Next in thread: Eric Torbenson: "Re: Accessing Administrative Shares"
- Reply: Eric Torbenson: "Re: Accessing Administrative Shares"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|