On Mon, May 03, 2010 at 05:04:53PM -0700, Kevin Keane wrote:
It may also be network discovery, and/or an IPv6 issue. Windows 7 tries to
default to IPv6. There is no NETBIOS or WINS in IPv6, so DNS is pretty much
mandatory (there also is Network Discovery, which is basically UPnP renamed).
] On Behalf Of smba...@gmx.com
Sent: Monday, May 03, 2010 3:52 PM
To: samba@lists.samba.org; michele.petra...@unipex.it
Subject: Re: [Samba] Long Delay on Fresh Windows 7 Clients
Thank you very much Michele. Because it's not trivial for me to
introduce DNS for the local Samba server, I just tried
Hi!
Jeremy is correct. Disabling IPv6 on Windows 7 is a very bad idea (since
the stack is an IPv6 dual stack and some features require IPv6). The
problem is most likely to be name resolution.
Your could test connectivity using literal IPv6 address on Windows 7
rather than a name, thereby
smba...@gmx.com wrote:
When I type \\sambahost\sharename, a prompt for the username and
password will eventually appear (and let me authenticate
successfully) but it takes almost forever (i.e. 1-5 minutes) until
that prompt dialog box appears.
Last week week my customer call me for the same
Thank you very much Michele. Because it's not trivial for me to introduce DNS
for the local Samba server, I just tried accessing the share by typing its
static IP address: \\192.168.0.13\sharename.
I still get the same delay.
Perhaps it's not DNS resolution that's causing that?
Thanks,
-
boun...@lists.samba.org] On Behalf Of smba...@gmx.com
Sent: Monday, May 03, 2010 3:52 PM
To: samba@lists.samba.org; michele.petra...@unipex.it
Subject: Re: [Samba] Long Delay on Fresh Windows 7 Clients
Thank you very much Michele. Because it's not trivial for me to
introduce DNS for the local
For testing purposes, I am running Windows 7 on a VM (VMWare), reverting to
fresh install Windows 7 frequently. This Windows 7 client, needs to access a
share on a local Samba server (Samba 3.0.23a-1 running on Fedora Core 4).
When I type \\sambahost\sharename, a prompt for the username and
