Thanks for answering !
I think my masquerading scheme is working pretty well.
And I was thinking as you said.
But it doesn't work. I think that some specific samba request must be set
somehow. The pb is : if I give the IP of M@ to M3 at request time, it works.
Name resolution doesn't work
>smbclient -L M2_name
fails
> smbclient -L M2_name -I M2_Ip
works
I would like to know if there is a way to set M1 to be a name server for
M3
Philippe
"Eric Cifreo" <[EMAIL PROTECTED]> writes:
> >
> > I have an interesting pb here :
> >
> > a machine M1 runs as a router between network A and B. network A is
> public. B is private and M1 masquerades it to the outworld.
> >
> > I setup M1 as a samba server with 2 interfaces : one on network A and one
> on network B. M1 can serve files pefectly on both network.
> >
> > Now the question : can I (and if yes, how) setup the thing so a machine M2
> on network A can access files on machine M3 on network B and vice-versa ??
> >
> > Thanks
> >
> > Philippe
> >
>
> If M1 is masquerading properly, then M3 should already be able to access
> files on M2. However, getting the machine on the public network (M2) to get
> files off a masqueraded machine (M3) will most likely require some
> port-forwarding on the part of M1: meaning all requests to the NETBIOS
> ports on M1 would have to be forwarded to M2. If this works, it also means
> that M2 could be your only file server on the private network (going to the
> outside world).....
>
> Eric Cifreo
> Austin, TX
>
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
