Re: Telnet and shares
- From: Malke <notreally@xxxxxxxxxxxxxxx>
- Date: Thu, 22 Jun 2006 06:32:05 -0700
Tim Slattery wrote:
"Jack Gostl" <gostl@xxxxxxxxxxxxx> wrote:Exactly. Maybe if the OP told us what his end goal is we could give
"NoStop" <nostop@xxxxxxxxxx> wrote in message
news:e7cjvp0s17@xxxxxxxxxxxxxxxxxxxxx
On Wednesday 21 June 2006 03:24 pm, Jack Gostl had this to say in
microsoft.public.windowsxp.general:
I am running XP Pro (not server). When I telnet in (from a Unix
box), I don't see any of the shared folders I have set up.
I'm not sure how to proceed on this.
I don't really understand what you're trying to accomplish? When you
telnet
in to a computer you end up working on that computer. Any shares on
that computer wouldn't be of use to you. If you want to share
directories on your Windoze machine with your *NIX machine, you need
to have a samba client installed and running on your *NIX machine.
Then you can access the Windoze shares just as you would from
another Windoze box.
Machine A (Windows) has a folder. The folder is shared with the
Workgroup.
Machine B (Windows) accesses the shared the folder as drive S:. When
logging into Machine B, and opening a command prompt its visible and
available.
The "S:" designation is local to machine B. Another machine may access
the same share and call it "Q:".
Machine C (Unix) logs into machine B. the "S:" drive isn't there.
No. The host machine doesn't know anything about a drive "S:". It
knows that it's making a particular directory available as a network
share. It doesn't know or care what other machines are calling it.
Doing a
"net use" from inside the telnet session shows the shares correctly,
but
shows them as unavailable.
If you've connected via telnet you're on the host machine, just as if
you were sitting at its console. Therefore, you don't use the network
to get to its disk drives, you just use them as you would if you were
at the machine itself.
focused help. If he just wants to access shares on a Windows machine,
why isn't he using Samba? Why mess around with telnet - and certainly
telnet is not a good choice for this sort of thing because it sends
passwords in the clear.
Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User
.
- References:
- Telnet and shares
- From: Jack Gostl
- Re: Telnet and shares
- From: NoStop
- Re: Telnet and shares
- From: Jack Gostl
- Re: Telnet and shares
- From: Tim Slattery
- Telnet and shares
- Prev by Date: Re: Firewall Security Problem
- Next by Date: Re: Computer history problem
- Previous by thread: Re: Telnet and shares
- Next by thread: Re: Telnet and shares
- Index(es):
Relevant Pages
|
Loading