I have a NAS which I've re-installed with DEBAIN. Mostly its all working great but when I tell it to ping a NetBIOS name it takes 10 seconds per attempt rather than 1. Despite this it actually resolves the NetBIOS names very quickly (the first line from the ping including the IP address appears almost instantly) it just sits there for 10 secs every ping.
# ping -c3 qnap
PING qnap (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.175 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.167 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=0.158 ms
--- qnap ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 20036ms
rtt min/avg/max/mdev = 0.158/0.166/0.175/0.016 ms
#
# ping -c 3 [URL]
PING www.l.google.com (173.194.36.104) 56(84) bytes of data.
64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=1 ttl=49 time=40.3 ms
64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=2 ttl=49 time=25.4 ms
64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=3 ttl=49 time=25.7 ms
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2022ms
rtt min/avg/max/mdev = 25.491/30.518/40.313/6.926 ms
I'm really struggling to track down what may be causing this as it is strictly when resolving NetBIOS names yet it finds the IP immediately.
Just installed squeeze and noticing slow responses to ping. Ping with -n is fine, and as expected. Ping without -n is very slow to appear on the screen.
ben@WOPR:~$ ping google.com PING google.com (74.125.230.114) 56(84) bytes of data. 64 bytes from 74.125.230.114: icmp_req=1 ttl=54 time=26.2 ms 64 bytes from 74.125.230.114: icmp_req=2 ttl=54 time=25.9 ms 64 bytes from 74.125.230.114: icmp_req=3 ttl=54 time=29.3 ms 64 bytes from 74.125.230.114: icmp_req=4 ttl=54 time=25.5 ms ^C64 bytes from 74.125.230.114: icmp_req=5 ttl=54 time=25.8 ms
--- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 20199ms rtt min/avg/max/mdev = 25.514/26.569/29.308/1.399 ms ben@WOPR:~$ ping -n google.com PING google.com (74.125.230.115) 56(84) bytes of data. 64 bytes from 74.125.230.115: icmp_req=1 ttl=54 time=25.6 ms 64 bytes from 74.125.230.115: icmp_req=2 ttl=54 time=26.0 ms 64 bytes from 74.125.230.115: icmp_req=3 ttl=54 time=26.8 ms 64 bytes from 74.125.230.115: icmp_req=4 ttl=53 time=21.5 ms ^C --- google.com ping statistics --- 5 packets transmitted, 4 received, 20% packet loss, time 4006ms rtt min/avg/max/mdev = 21.540/25.042/26.859/2.064 ms
I've tried disabling ip6, disabling avahi and adding options single-request to my /etc/resolv.conf - problem remains. If it helps when installing Squeeze was prompted to install firmware-realtek, which I didn't have. So downloaded onto usb from another machine installed once setup was complete.
I just installed my first EVER bind DNS server. I am running bind9 on Ubuntu 10.04. Everything seems to be working great except one thing: If I ping a host that I have set up in bind by its HOSTNAME the pings take 5-6 seconds to reply/print to the screen between each echo response. If I ping by the host's IP address, they echo back very quickly.
I have read that IPv6 can cause this, but I have disabled it in /etc/sysctl.conf and the problem still exists.
I know everyone says this can't be a DNS issue, but this never was an issue with dnsmasq (which i was using prior), and it doesn't make sense that the ping are ONLY slow when pinging by hostname and not IP.
Configs below:
Ping by hostname - there is a 5-6 second delay between each one of the responses:
Code:
Ping by IP - the responses come VERY quickly one after the other:
I added my linux server to a windows AD using winbind / samba. Everything worked just fine. After changing the OS to Debian lenny x64 I get a "segmentation fault" when trying to change user passwords. I am using the exact same configuration, on my 32 bit Server everything works.
debian:~# passwd <user> sgmentation fault tail /var/log/syslog: kernel: [689689.005934] passwd[11209]: segfault at 0 ip b7b84418 sp bfc37fc0 error 4 in pam_winbind.so[b7b7e000+b000] Debian Lenny 5.0
I'm running a squid server on debian lenny with ntlm_auth.
Everything is working good after following those two tutorials : [url] and [url]
As all was working perfectly i decided to rebbot my server, and after reboot the ntlm-auth was not working anymore.
When i tried to run the command "wbinfo" with many options i had this error message "error looking up domain users" or"error looking up domain group" so i think that the problem deals with winbind module.
I know that proxy user needs rights and that after reboot the rights are reseted, so this problem doesn't come from here.
And when i try to open IE with a client i have this "cache accesss denied" because the ntlm_auth wasn't done.
I tried to restart all services (samba,winbind,squid) without any success, only the "kinit" command is still working...
What is going on with winbind when the server is rebooted ?
I have a debian server installed with a static ip. Now i am able to ping my ip, but when i try to configure a domain name with the nameserver as my ip, i am not able to ping the domain name
I am using an virtual machine. where I need to ping from one machine to another. earlier I was able to ping. But after going to google.com once, I cannot ping back to this machine.
But if I gave ping -I eth1 <IP> then I can ping.
I cannot install any package, so tell me solution which includes not installing any package.
I have a connection an its slow in both ff and chrome...however i can ping sites and get the same response time as my xp machine which runs fast. usually around the 40ms mark with no lost packets.
Also when i do installs eg. of chrome etc, i was getting up to 500kB/s download. I just cant seem to replicate this browsing, its loading up at a dial up pace. The last time I had an issue like this was setting up my mums work laptop on our home network where the work had specific proxy settings, so we turn the off and it works fine.
I do not know how to tinker this
INFO:::: broadcom 4306 chip have tried ndiswrapper and bcmxx fwcutter
So after some period of inactivity, my FC servers with infiniband cards in them seem to go to sleep or something. If I login to the machine and try to ping other machines with IB interfaces, the first request takes much longer than the others. This is not so over Ethernet.
compute-4-12 ~]# ping ib-s0-1 (this is a solaris machine) PING ib-s0-1.local (192.168.1.19) 56(84) bytes of data. 64 bytes from ib-s0-1.168.192.in-addr.arpa (192.168.1.19): icmp_req=1 ttl=255 time=3.64 ms 64 bytes from ib-s0-1.168.192.in-addr.arpa (192.168.1.19): icmp_req=2 ttl=255 time=0.131 ms 64 bytes from ib-s0-1.168.192.in-addr.arpa (192.168.1.19): icmp_req=3 ttl=255 time=0.222 ms
compute-4-08 ~]# ping c4-7 (identical neighboring FC machine) PING compute-4-07.local.local (10.255.255.187) 56(84) bytes of data. 64 bytes from compute-4-07.local.255.10.in-addr.arpa (10.255.255.187): icmp_req=1 ttl=64 time=1.28 ms 64 bytes from compute-4-07.local.255.10.in-addr.arpa (10.255.255.187): icmp_req=2 ttl=64 time=0.108 ms 64 bytes from compute-4-07.local.255.10.in-addr.arpa (10.255.255.187): icmp_req=3 ttl=64 time=0.115 ms 64 bytes from compute-4-07.local.255.10.in-addr.arpa (10.255.255.187): icmp_req=4 ttl=64 time=0.119 ms 64 bytes from compute-4-07.local.255.10.in-addr.arpa (10.255.255.187): icmp_req=5 ttl=64 time=0.180 ms
This issue does not only affect ping. I created a user that mounts his home directory over nfs over infiniband. ssh'ing in takes longer the first time as well. If I ssh with verbosity turned up all the way, I get a brief hang at "we sent a hostbased packet, wait for reply" (this is the primary symptom I'm trying to get rid of since we want home directories over nfs over IB (without the initial delay)).
I try to use the "ping -a" command for getting an audible ping. But there is just silence The command "beep" works fine, so everything should be ok with the speaker (in the konsole).
There are several DCs on our network, and winbind seems to use a win2008 one (found by wins maybe?), with which it has an incompatibility issue.
Can I specify somehow the ip address of the AD which winbind is allowed to use?
I have set "password server=<dc ip>" in smb.conf and it works now. I suspected that should be the right option to set, but the samba manual stating that option only takes effect with "security=ad" had misinformed me. Actually, it also takes effect with "security=domain".
I have a samba server I had manually configured pam to use winbind in 8.04 I'm pretty sure that when I did that I broke pam. I had not choice at the time but in 10.04 there is a winbind pam module.How can I rewrite the pam configuration to use the default pam winbind configuration?
for some reason the package winbind is misbehaving. A few upgrades ago I suddenly started getting this error message each time I try to upgrade or install winbind (or any other package).
I have a few Redhat 8 servers that I have shut the winbind service off, yet I see lots of message int he /var/log/messages log in regards to winbind. The message i am seeing are
pam_winbind[25640]: write to socket failed! pam_winbind[25640]: internal module error (retval = 3, us er = `root'
This applies to my 2 opensuse PC's, my Windows PC is fine.I can ping a hostname, say "PC1" but I can not ping PC1.domain.local (even the host PC can not ping it's own FQDN). When I ping just the hostname the ping stats even list the FQDN.Onto the next issue, since all my PC's, have the domain prefix domain.local, my Synology can not. I can ping it's IP and that is it. I can resolve it's name with nmblookup just fine tho and that is what is killing me. How is this not resolving.Even weirder, I can browse to "Synology" in Network Servers under places on the slab.
I have two machines on this network, one running Ubuntu and the other running Fedora.
When I'm using the Wireless network on the Ubuntu machine, I cannot ping the Fedora machine. Everything else works. I can browse the net fine.
If I switch over to the Wired Network then I can ping the other machine.
I don't understand why ping doesn't work only over the Wireless. I can ping the router so I'm guessing it's getting blocked by the router but I didn't block ICMP traffic.
I tried asking on IRC and they ran out of ideas too to find out where the problem is.
we are using LucidLynx Linux, 64-bit,with ActiveDirectory accounts via samba/winbind 64-bit.I have 2 separate 32-bit applications:IBM MQ Toolkit (32-bit java-based) and Acrobat Reader
I have an SSH server on my laptop, and I'm using the default configuration file, but I added "AllowUsers <myUserName>". I get lots of login attempts like the ones below in my /var/log/auth.log.From Google, I find that pam_winbind allows some kind of Windows authentication. This leaves me with 2 questions. What does winbind do when I have not configured any Windows/Samba accounts? How can I turn it off?
Code: Oct 23 20:01:49 muon sshd[24329]: User root from 201.116.17.163 not allowed because not listed in AllowUsers
I am trying to get a ubuntu machine (client) onto a windows active directory (domain) this i have done and you can login using winbind to the client desktop no problems however i dont want the domain users' home directories on the client machine so i have set up a ubuntu server (samba) to hold the home directories now so far i have been able to set up a share which both windows and linux can read and write to with no passwords needed, and if i have modified the /etc/fstab file on the client to mount the samba share on startup however if i login as a domain user it fails to create a home directory on the share with the following error:
"/mnt/home/admin2" does not exist
now the main question is this in fstab i have used a cred file stored in /usr/share/.smbcred which should be accessible by all users right? i know i can put the creds into the fstab file but i can't find how and it is just failing to mount when i try so if you know how i will try that, also does fstab run before or after the home directory is created as if it runs after then the cred file is working but the home directory is looking at a location which hasnt been mounted yet or if fstab runs before then the location is not mounting right (hoping for second one )
So, I have an Virtual Machine running CentOS 5.4. It sits behind a hardware firewall which also does NAT'ing. I've set up plenty of these, so I know for sure the firewall and NAT rules are set up correctly. From the host, I can ping anything in my subnet and the gateway. But I can't ping anything else beyond the gateway. I can perform DNS queries and when I try to ping, it finds the appropriate IP address.But from the outside, I can ping the PUBLIC address (It's a 1 public to 1 private address NAT, not 1 public to multiple private). I've tried it with IPTABLES on and off, with no change.
I have Mandriva One 2009.0 (192.168.1.100) on one box and Mandriva Free 2010.0 (192.168.1.118) on the other. I can ping router (192.168.1.1) from both of these boxes but I can't ping one box to the other and the other way around. What's going on?.
Do I have to change some settings in router?. Or is it firewall issue on those two machines?. Both of these boxes are connected by cable. Symbol of the router: TL-WR340G.
In short we are booting Centos 5.4 over PXE to a bunch of diskless clients. Once they are booted - we can login (as local root account) and RDP to windows machines using rdesktop as we require.
The next step of the project is to get user authentication to the Windows Domain controller working for the PXE image.
To do so - we continued with our physical install of Centos 5.4 (used to create the pxe image with rsync as per the wiki page for diskless clients) by following through this page. AD auth works perfect on this box (it has a local HDD install of centos obviously).
Once we rsync'd the changes over to the pxeboot location - and rebooted one of the diskless pxe clients - we get issues.
The issue is that winbind seems to start - however the file "/etc/samba/secrets.tdb" cant be read. We tried removing this file that the PXE clients use and recreating it using
How do I turn winbind authentication off or vsftpd. I keep getting these error messages in the /var/log/ secure:vsftpd: pam_winbind(vsftpd:auth): request failed: No such user, PAM error was User not known to the underlying authentication module (10), NT error was NT_STATUS_NO_SUCH_USER.I already tried remarking out different things in the config files. Is it safe to remark out the winbind stuff in /etc/pam.d/system-auth if we are using the smbclient to connect to a Windows share?Why would you want to to use AD to authenticate users for something simple like FTP is beyond me.I merely want it to authenticate against local system users.
Strange things are happening today to my pc with debian squeeze 2.6.32-3-amd64 kernel.
It can connect to internet via my wirelss rt2870 driver (Ralink, Belkin usb wireless). But I cannot ping any of my other computers in the home network (served by a Belkin N+ wireless router). Other computers can ping it.
I am also connected via ethernet directly to another desktop. Last night I can access the shared file (samba windows share) in this other computer, using ethernet (disabling wireless). Today I cannot. I cannot even ping it or any computer, or itself.
I am using network manager with this interface:
# The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp
i am running debian testing and the last few days i was trying to ssh to another pc on my network and i was getting an error like there was no machine with that ip! then i tried pinging to it with no luck! ARP was the only tool that returned the MAC address of the machine and that is strange i think. i realised then that i could only ping the gateway and localhost (127.0.0.1 not my ip). after editing my /etc/hosts, i could ping my ip as well. what is so wrong? here are some useful things:
my new /etc/hosts: jack@debian:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 debian.local debian
