Jim, the network trace doesn't show any AAAA DNS record lookups while
this occurs. However, I was surprised to find empty log files that look
like "log.__ffff_192.168.0.48". What causes this?
Chris, you are onto something here (mentioning the NIC). I haven't gone
back to prove this 100%, but the multiple 20 second delay problem has
gone away. It went away when I connected the ethernet cable to a
temporarily unused NIC. Specifically, I have 3 ethernet cards. The
PC's having the 20x delay were on eth1. The NIC eth0 wasn't used for
Samba at all. NIC eth2 didn't have a cat5 connected, but was configured
with a static IP. It appears the 20x delay went away when I connected
an ethernet cable to eth2.
This doesn't make any sense to me, however, as samba wasn't configured
to use eth2 at all.
Make any sense?
... Altan
www.aaarpinball.com
On 8/10/2009 5:13 AM, Jim McDonough wrote:
On Sat, Aug 8, 2009 at 4:14 AM, Altan (aol.com)<[email protected]> wrote:
Thanks Jeremy. No Ipv6 enabled. This problem even occurs if I use
"\\192.168.0.254" (IP of my samba server) rather than a netbios name. I'm
not running a local DNS server.
You don't necessarily have to have IPv6 enabled to have your DNS doing
AAAA lookups. I would check the traffic to be sure.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
