[ previous ] [ next ] [ threads ]
 From:  "Sean Waite" <swaite at sbn dash services dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  RE: [m0n0wall] windows share on vpn
 Date:  Fri, 10 Feb 2006 11:07:17 -0600
Just a little tip, add whatever machines to your hosts file. Then you can navigate to whatever
machine quicker by its name without
relying on WINS. Actually, you should find that it is easier to rely on the hosts file than WINS. If
the machines though on the other
end are doing DHCP, then it would be better to run WINS/DNS locally and have them replicate with the
WINS/DNS on the other end.

Sean Waite

-----Original Message-----
From: "Jason Brunk" <jbrunk at wthosting dot com>
To: "'Jared Cebada'" <JCebada at smwc dot edu>, <m0n0wall at lists dot m0n0 dot ch>
Date: Fri, 10 Feb 2006 11:18:06 -0500
Subject: RE: [m0n0wall] windows share on vpn

>  I spent a long time trying to figure this out.  The only thing I was able
> to come up with is to run a wins server on 1 or the other network, have both
> networks pass out the wins server address with dhcp, then you can access all
> machines on both networks using \\machinename\share  
> The one thing I did notice is I was unable to see both networks machines in
> the network neighbor hood, they existed, but they did not appear in the net
> hood.
> Jason
> -----Original Message-----
> From: Jared Cebada [mailto:JCebada at smwc dot edu] 
> Sent: Friday, February 10, 2006 11:07 AM
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] windows share on vpn
> Alright I have a vpn pptp connection, to I have a windows xp
> share in that I would like to access.
> I know this comes down to I not in the same subnet mask as the share, does
> monowall or any one have a way of getting arround this.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch