Anyone doing this?
I have a server about 4 hops away from the machine I want to connect with.
Its using windows 98. I tried net use x: \\IPADDRESS\share and that didn't
work (nor does the domain).
I'm using a netgear RT314
I should note that I can connect if I use a straight through connection and
not a NAT. Ideally I'd like to be able to connect using all the machines
behind the NAT. Is that even possible?
Jim
> -----Original Message-----
> From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On
> Behalf Of Crest
> Sent: Monday, January 21, 2002 12:57 PM
> To: Samba Mailing List
> Subject: extending path
>
>
> Hi,
>
> caused by the complete crash of my former Gateway (including
> SAMBA) I had to
> install a completely new system.
> I decided NOT to install the (old) Samba 2.2.1 which comes with my
> distribution (SuSE 7.3), but to download and install the new 2.2.2 as this
> one is needed for Domain-Logons from W2k-clients.
> Everything worked fine, I wrote my smb.conf and checked with testparm,
> everything okay.
> Well, using testparm was a little bit difficult, *cause I'm not
> used to have
> to change my current path or to start a script using the complete path to
> the script.
> During the installation of Samba 2.2.2 the path to the binaries
> (usr/local/samba/lib) seems to NOT have been included in the PATH.
> Simple question from someone who is used to have a completely running and
> full configured system: How do I include "/usr/local/samba/bin/"
> to my PATH
> ? One workaround coming to my mind is to make symbolic links to the
> samba-binaries in /usr/bin or /usr/sbin, but there must be a better way.
>
> Thanks in advance for your assistance.
>
> Stephan
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>