similar to: Working or not working depending on variable order in tinc.conf

Displaying 5 results from an estimated 5 matches similar to: "Working or not working depending on variable order in tinc.conf"

2008 Mar 27
6
Problems pinging PC on tunnel
Hello! I have set up tunnel between a FreeBSD machine and Windows Vista. Tunnel is established, but when I try to ping either end ping fails. I have temporarily switched off firewalls on both machines, no luck. Here is client tinc.conf on Vista: Name = lenovo_client ConnectTo = lenovo_server Interface = tinctap Subnet = 10.20.40.0/24 Sevrer tinc.conf on FreeBSD: Device=/dev/tap0
2008 Oct 02
2
SSH connection hangs on shell commands when used through tinc
Hello! I have 3 PCs - Windows, FreeBSD and Ubuntu. FreeBSD runs as a tinc server as it has a real IP. Ubuntu runs as a tinc client as it has a dynamically changing public IP. Windows has not tinc installed yet. Therefore I use Putty ssh client to ssh to FreeBSD machine (as it has real IP) and then from there I ssh to the Ubuntu box using its virtual IP. The connection establishes well, I can ping
2015 Nov 18
4
Permission Issues with GPO
Hai Mourik Jan/Victor. > MJ definitely understands the problem I'm facing.... Yes, and i do to but you wont listen... ALL My client pc's, windows and linux computers, dont have any uid/gid assigned. My client pc's do access the DCs and multiple member servers with shares. I do distribute settings and files with GPO and these files are on a member server. Yes also as
2017 Dec 21
0
WERR_DS_DRA_MISSING_PARENT while Joining Samba4 DC to Samba4 Domain
Perhaps I'm rooting around at a lower level than I should be, and somewhat beyond what I can understand, but here is a bit of info I dug up. It might be helpful? The GUID in the first search matches the one referred to in the error message. $ sudo ldbsearch -H /var/lib/samba/private/sam.ldb.d/DC\=DOMAINDNSZONES\,DC\=REDACTED\,DC\=DOMAIN\,DC\=LOCAL.ldb "(DC=DomainDnsZones)" # record
2017 Oct 26
2
not healing one file
Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp