Telnet and shares

  • Thread starter Thread starter Jack Gostl
  • Start date Start date
J

Jack Gostl

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 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.
Click to expand...

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.


--
The ULTIMATE Windoze Fanboy:

http://video.google.com/videoplay?docid=-2370205018226686613

View Some Common Linux Desktops ...
http://linclips.crocusplains.com/index.php
 
NoStop said:
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.
Click to expand...


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.

Machine C (Unix) logs into machine B. the "S:" drive isn't there. Doing a
"net use" from inside the telnet session shows the shares correctly, but
shows them as unavailable.

Does that clarify it?
 
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.

Machine C (Unix) logs into machine B. the "S:" drive isn't there. Doing a
"net use" from inside the telnet session shows the shares correctly, but
shows them as unavailable.

Does that clarify it?
Click to expand...

Yes, that clarifies what you are trying to do. I don't have an answer for
your problem, as I've never tried doing what you are trying to do. Taking a
complete stab in the dark, maybe the problem is related to how telnet
connects? It sends a clear password (quite insecure actually) to login. So
maybe with that type of login share access through encrypted passwords
aren't permitted? I really have no idea how a Windoze telnet server works.

I can use Rdesktop to access a Windoze box and can see shares on that box
when remotely logged in like this. But that sends an encrypted password for
logins.



--
The ULTIMATE Windoze Fanboy:

http://video.google.com/videoplay?docid=-2370205018226686613

View Some Common Linux Desktops ...
http://linclips.crocusplains.com/index.php
 
Jack Gostl said:
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.
Click to expand...

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.
Click to expand...

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.
Click to expand...

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.
 
Tim said:
The "S:" designation is local to machine B. Another machine may access
the same share and call it "Q:".


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.


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.
Click to expand...
Exactly. Maybe if the OP told us what his end goal is we could give
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
 
The "S:" designation is local to machine B. Another machine may access
the same share and call it "Q:".


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.


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.
Click to expand...
Tim,

You're misunderstanding what he's trying to do. That's easy to do, as I did
the same until he qualified it. Please re-read what he's posted. As you'll
see by my reply to him, I don't have an answer. But I'm curious about what
is happening and you being a MVP, should be more equipped to answer him
than I am.


--
The ULTIMATE Windoze Fanboy:

http://video.google.com/videoplay?docid=-2370205018226686613

View Some Common Linux Desktops ...
http://linclips.crocusplains.com/index.php
 
Tim,

You're misunderstanding what he's trying to do.
Click to expand...

You're right, I misread it. He's telnetting to machine B which has
drive S: defined and mapped to a network share. He says he can't see
S:. I don't know why.
 
Back
Top