Re: [Samba] Samba 4 - problems with name resolution on Windows 7 clients

2013-04-14 Thread X-Dimension

Am 10.04.2013 19:15, schrieb Matthieu Patou:

On 04/10/2013 09:48 AM, X-Dimension wrote:
We have a strange name resolution problem on Windows 7 clients. 
(Windows XP clients are working fine!)
If a Windows 7 client is connected more than 7 or 8 hours to our 
Samba 4 active directory server, we can't
do ping servername anymore, but ping servername.domainname works 
fine.

After logout and login again to the Windows 7 clients everything works!
Can you check what is the ipconfig /all output on windows 7 clients ? 
also you should do a tcpdump/wireshark trace on your client to see 
which DNS request it is doing.
The main problem is, that all Windows clients access the samba shares 
by \\servername\sharename
and not \\servername.domainname\sharename and after 7 or 8 hours our 
users can't access the files

or programs on these shares.
What goes wrong here and what is the best way to fix this? I can 
change some GPOs and set all
shares to \\servername.domainname\sharename, but if there is a better 
solution i would prefer this.

Thx for help! :)


Matthieu.


Here is the output of ipconfig /all:

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Client1
   Primäres DNS-Suffix . . . . . . . : mydomain.local
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : mydomain.local

Ethernet-Adapter LAN-Verbindung:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : vmxnet3 Ethernet Adapter
   Physikalische Adresse . . . . . . : xx-xx-xx-xx-xx-xx
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : :::::%xx(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.1.235(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.1.5
   DNS-Server  . . . . . . . . . . . : 192.168.1.200
   NetBIOS über TCP/IP . . . . . . . : Aktiviert



--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] Samba 4 - problems with name resolution on Windows 7 clients

2013-04-10 Thread X-Dimension
We have a strange name resolution problem on Windows 7 clients. (Windows 
XP clients are working fine!)
If a Windows 7 client is connected more than 7 or 8 hours to our Samba 4 
active directory server, we can't

do ping servername anymore, but ping servername.domainname works fine.
After logout and login again to the Windows 7 clients everything works!
The main problem is, that all Windows clients access the samba shares by 
\\servername\sharename
and not \\servername.domainname\sharename and after 7 or 8 hours our 
users can't access the files

or programs on these shares.
What goes wrong here and what is the best way to fix this? I can change 
some GPOs and set all
shares to \\servername.domainname\sharename, but if there is a better 
solution i would prefer this.

Thx for help! :)
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] Samba 4 - problems with name resolution on Windows 7 clients

2013-04-10 Thread Matthieu Patou

On 04/10/2013 09:48 AM, X-Dimension wrote:
We have a strange name resolution problem on Windows 7 clients. 
(Windows XP clients are working fine!)
If a Windows 7 client is connected more than 7 or 8 hours to our Samba 
4 active directory server, we can't
do ping servername anymore, but ping servername.domainname works 
fine.

After logout and login again to the Windows 7 clients everything works!
Can you check what is the ipconfig /all output on windows 7 clients ? 
also you should do a tcpdump/wireshark trace on your client to see which 
DNS request it is doing.
The main problem is, that all Windows clients access the samba shares 
by \\servername\sharename
and not \\servername.domainname\sharename and after 7 or 8 hours our 
users can't access the files

or programs on these shares.
What goes wrong here and what is the best way to fix this? I can 
change some GPOs and set all
shares to \\servername.domainname\sharename, but if there is a better 
solution i would prefer this.

Thx for help! :)


Matthieu.

--
Matthieu Patou
Samba Team
http://samba.org

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba