samba - Jan 1998 - access to NT/Win95 network from Linux ' dial-in | internet '

Hi,

  This may not be strictly a samba question, since some Linux OS tricks
may have to be utilized (like IP Masquerading, NAT and aliased eth
interface), but I'm posing it here since samba may be part of the solution
too, and since it's most likely the people on this list that would have
most experience with these issues. 

  4 questions follow at the bottom :

 description of setup :
   The Linux box has 2 modems, through which win95 boxes connect.
   Linux is connected on one LAN with an NT box and with a bunch of win95
boxes.
  This gives us 3 "access groups" that can utilize the services of the
NT,
Linux and LAN Win95 boxes :
     - "inernet access group" -- machines that can connect to
          Linux through internet dynamic IP dialup modem
     - "dial-in access group" -- dedicated dial-in (pppd) modem
 and - "LAN access group"     -- the machines sitting on the LAN


   Question 1 :

    What types of access are *not* possible from the two non-LAN groups ?
    In other words, what is the list of services on the NT (or LAN 95
boxes) that are not available to either of the two "remote" access
groups ?
 (these are the "inernet" and "dial-in" access groups)


  I assume that that the second (dedicated dial-in) access group has all
the same capabilities as the LAN access group, since the machine that
dials-in can get an IP on the LAN.

 Question 2:
  Am I wrong on this assumption ?

 Question 3:
  Is there a way any of the NT / Win95 boxes can see a modem on Linux as a
"modem" ? I.e. it can call dial-out from it (data modemming), perhaps
even
faxing ? ( and I wouldn't dream of voice capabilities).

 Question 4:
  I also have a scanner. I can attach it to any machine. Is there a way to
"share" it ? Can it be attached to the Linux box and share it from
there ?


       Thanx,

            Jan

 -- Gospel of Jesus is the saving power of God for all who believe --
Jan Vicherek ## To some, nothing is impossible. ##  www.ied.com/~honza
    >>>    Free Software Union President  ...  www.fslu.org   
<<<
Interactive Electronic Design Inc.    -#-    PGP: finger honza@ied.com

In article <Pine.LNX.3.96.980121115458.497K-100000@ann.ied.com>,
	Jan Vicherek <honza@ied.com> writes:
> Question 3:
>  Is there a way any of the NT / Win95 boxes can see a modem on Linux as a
>"modem" ? I.e. it can call dial-out from it (data modemming),
perhaps even
>faxing ? ( and I wouldn't dream of voice capabilities).
IIRR, there's a modem-sharing-howto somewhere in comp.os.linux.answers,
which
should give you an idea.
just for faxing, you can try ESEMfax (http://www.esem.com/software/esemfax.html)
> Question 4:
>  I also have a scanner. I can attach it to any machine. Is there a way to
>"share" it ? Can it be attached to the Linux box and share it from
there ?
if you can use hpscanpbm, i once wrote a tiny client/server-thingy (nothing
fancy) which i can send you if you want.
>       Thanx,
>            Jan
  -- oly
-- 
Oliver Nittka              | nittka@esem.com
ESEM Gruenau GmbH & Co. KG | http://www.esem.com
Riedheimer Str.6           | phone: +49 7544 9583-25
88677 Markdorf / Germany   | fax:   +49 7544 9583-60

Jan Vicherek writes:
 > 
 >   Hi,
 > 
 >   This may not be strictly a samba question, since some Linux OS tricks
 > may have to be utilized (like IP Masquerading, NAT and aliased eth
 > interface), but I'm posing it here since samba may be part of the
solution
 > too, and since it's most likely the people on this list that would
have
 > most experience with these issues. 
 > 
 >   4 questions follow at the bottom :
 > 
 >  description of setup :
 >    The Linux box has 2 modems, through which win95 boxes connect.
 >    Linux is connected on one LAN with an NT box and with a bunch of win95
 > boxes.
 >   This gives us 3 "access groups" that can utilize the services
of the NT,
 > Linux and LAN Win95 boxes :
 >      - "inernet access group" -- machines that can connect to
 >           Linux through internet dynamic IP dialup modem
 >      - "dial-in access group" -- dedicated dial-in (pppd) modem
 >  and - "LAN access group"     -- the machines sitting on the LAN
 > 
 > 
 >    Question 1 :
 > 
 >     What types of access are *not* possible from the two non-LAN groups ?
 >     In other words, what is the list of services on the NT (or LAN 95
 > boxes) that are not available to either of the two "remote"
access groups ?
 >  (these are the "inernet" and "dial-in" access groups)

Nothing from the internet should be able to access any services on
either of the other two groups.  That's what you have the firewall
for after all.

Depends upon how you set up the forwarding as to what the modem group
can get to.  I set up the modem with proxy-ARP, giving it a local ethernet
IP number so that it appears to be on the local net.  In this case the
modem user can access everything local, and the internet as well.

 >   I assume that that the second (dedicated dial-in) access group has all
 > the same capabilities as the LAN access group, since the machine that
 > dials-in can get an IP on the LAN.

Dialins may have a problem with samba browsing and any other protocol that
requires multicasts.

 > 
 >  Question 2:
 >   Am I wrong on this assumption ?
 > 
 >  Question 3:
 >   Is there a way any of the NT / Win95 boxes can see a modem on Linux as a
 > "modem" ? I.e. it can call dial-out from it (data modemming),
perhaps even
 > faxing ? ( and I wouldn't dream of voice capabilities).

There is a program (Can't remember it's name) that emulates a bios modem
on the PC box, while connecting to a socket an the unix box. At the unix
end you have a program to transfer bytes between the socket and /dev/modem