On Mon, May 16, 2011 at 8:37 AM, Vincent Malien wrote:
> this morning, I added entries to the files lmhosts.sam
FYI, the "sam" in "lmhosts.sam" stands for sample - you need to put
the valid data in a file named "lmhosts" (no .sam, .txt, etc.) or it
isn't being used at all.
Chris
--
To unsubscr
this morning, I added entries to the files lmhosts.sam and hosts for
this server and access is allowed now.
thanks for your help.
Le 13/05/2011 17:04, Vincent Malien a écrit :
it's a site-to-site VPN
Sorry, my colleague on the other site just shut-down & gone. I'll test
monday, but I think y
it's a site-to-site VPN
Sorry, my colleague on the other site just shut-down & gone. I'll test
monday, but I think you mean "net view \\IP_ADDRESS_OF_SERVER".
Le 13/05/2011 16:33, Gaiseric Vandal a écrit :
Is this a client-to-site or site-to-site VPN?
Does "new view \\IP_ADDRESS_OF_SERVER" wo
Is this a client-to-site or site-to-site VPN?
Does "new view \\IP_ADDRESS_OF_SERVER" work?
I have one samba server (compiled from source) where Windows VPN clients
can't access it by name UNLESS using either WINS ior an lmhosts file is
configured. packet sniffing showed the client connecting
Hi,
I have a problem of Access denied to samba server from win7 64bit behind
a VPN.
the samba server is 3.2.5-4 release on a debian lenny (I will upgrade it
soon), member of a win2K AD domain.
the win7 PCs are on the same AD domain, they can access to an other
samba server witch is very simil
