search for: 2001ms

...rriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. #> ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms #> nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network...

...607:f678::1) 56 data bytes 64 bytes from 2607:f678::1: icmp_seq=0 ttl=64 time=1.34 ms 64 bytes from 2607:f678::1: icmp_seq=1 ttl=64 time=0.894 ms 64 bytes from 2607:f678::1: icmp_seq=2 ttl=64 time=0.871 ms --- 2607:f678::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.871/1.035/1.342/0.219 ms, pipe 2 <ns6.peak.org> [104] # ping6 ipv6.google.com PING ipv6.google.com(pz-in-x67.1e100.net) 56 data bytes 64 bytes from pz-in-x67.1e100.net: icmp_seq=0 ttl=52 time=14.1 ms 64 bytes from pz-in-x67.1e100.net: icmp_seq=1 ttl=52 time=14.3 ms 64...

....8 PING 5.6.7.8 (5.6.7.8) 56(84) bytes of data. 64 bytes from 5.6.7.8: icmp_seq=1 ttl=51 time=458 ms 64 bytes from 5.6.7.8: icmp_seq=2 ttl=51 time=24.9 ms 64 bytes from 5.6.7.8: icmp_seq=3 ttl=51 time=25.3 ms ^C --- 5.6.7.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 24.936/169.512/458.272/204.184 ms Immediately replying remote host on second try. $ ping 5.6.7.8 PING 5.6.7.8 (5.6.7.8) 56(84) bytes of data. 64 bytes from 5.6.7.8: icmp_seq=1 ttl=51 time=24.6 ms 64 bytes from 5.6.7.8: icmp_seq=2 ttl=51 time=25.3 ms 64 bytes from 5.6.7.8: i...

...2.178) 56(84) bytes of data. 64 bytes from 24.89.92.178: icmp_seq=1 ttl=50 time=92.2 ms 64 bytes from 24.89.92.178: icmp_seq=2 ttl=50 time=96.2 ms 64 bytes from 24.89.92.178: icmp_seq=3 ttl=50 time=91.0 ms --- 24.89.92.178 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 91.023/93.193/96.263/2.245 ms [frankcox at mutt ~]$ ping 24.89.92.180 PING 24.89.92.180 (24.89.92.180) 56(84) bytes of data. --- 24.89.92.180 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 5000ms Incidentally, it is my current understanding th...

...4) bytes of data. >From 99.10.11.1 icmp_seq=1 Destination Host Unreachable >From 99.10.11.1 icmp_seq=2 Destination Host Unreachable >From 99.10.11.1 icmp_seq=3 Destination Host Unreachable --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2001ms , pipe 3 I was puzzled by this behaviour, so I traced network traffic with tcpdump, and the output is the following: # tcpdump -n -i eth2 src or dst 8.8.8.8 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth2, link-type EN10MB (Ethernet), capture size 96 b...

...2.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.63 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.40 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.34 ms --- 192.168.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 2.343/2.462/2.637/0.132 ms ------------------------------------------------------------------------------ i8600:~# ping -I eth0 192.168.0.1 PING 192.168.0.1 (192.168.0.1) from 192.168.0.238 eth0: 56(84) bytes of data. --- 192.168.0.1 ping statistics --- 5 packets transmitted...

Hi. HELP! I read: :-) http://www.samba.org/samba/docs/man/domain-member.html#domain-member-server (Which notes, "This is a rough guide to setting up Samba-3 with Kerberos authentication against a Windows 200x KDC. A familiarity with Kerberos is assumed." Is there "A guide to familiarity with Kerberos as a primer for Samba configuration" somewhere?) :-) This thread

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel