We are running Samba 2.05 on Solaris and have run into the following issue. We can connect to the shares on the box from any box when using the short name (ie \\Bob), but not the long name (\\bob.domain.com) or the ip address (\\172.17.19.104). When using Windows 2000, the default method of access is to use DNS to resolve the name, so even using a short name somehow results in the long name being sent. We have verified that the issue is with the long name by removing our domain name from the client and connections work fine. Is there a reason why the server would reject the long name and the IP address, but allow the short (netbios) name. This doesn't really make sense, as we can access other features on the box (telnet, ssh, etc) using the fully qualified DNS name. Additional information: Everything worked last week, even from Windows 2000 boxes. Something probably changed, but we did not make a deliberate change to the Samba configuration, except in troubleshooting this problem. Matt Dobbertien NT Administrator nistevo mdobbertien@nistevo.com
MCCALL,DON (HP-USA,ex1)
2001-Apr-19 17:28 UTC
Problems with Win2K and IP Address or Long Name
Hi Matt, could you have a true dns name resolution issue? Using the short name, you would get resolution of 'bob' from netbios broadcasts first. Using the long name, dns would be invoked to do this first.... On your win2k machine, can you go to the command prompt and do a ping bob.domain.com??? Probably too simple, but worth a shot... don -----Original Message----- From: Matt Dobbertien [mailto:MDobbertien@Nistevo.com] Sent: Thursday, April 19, 2001 10:35 AM To: 'samba@lists.samba.org' Subject: Problems with Win2K and IP Address or Long Name We are running Samba 2.05 on Solaris and have run into the following issue. We can connect to the shares on the box from any box when using the short name (ie \\Bob), but not the long name (\\bob.domain.com) or the ip address (\\172.17.19.104). When using Windows 2000, the default method of access is to use DNS to resolve the name, so even using a short name somehow results in the long name being sent. We have verified that the issue is with the long name by removing our domain name from the client and connections work fine. Is there a reason why the server would reject the long name and the IP address, but allow the short (netbios) name. This doesn't really make sense, as we can access other features on the box (telnet, ssh, etc) using the fully qualified DNS name. Additional information: Everything worked last week, even from Windows 2000 boxes. Something probably changed, but we did not make a deliberate change to the Samba configuration, except in troubleshooting this problem. Matt Dobbertien NT Administrator nistevo mdobbertien@nistevo.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
MCCALL,DON (HP-USA,ex1)
2001-Apr-19 17:30 UTC
Problems with Win2K and IP Address or Long Name
Oh, and also visa versa - ie, can you use nmlookup on your solaris box with both bob.domain.com and with the ip address, and have it come back with a name to ip/ip to name resolution that makes sense? And do the same for the fqdn of the win2k pc that is trying to reach you? Just a thought, don -----Original Message----- From: Matt Dobbertien [mailto:MDobbertien@Nistevo.com] Sent: Thursday, April 19, 2001 10:35 AM To: 'samba@lists.samba.org' Subject: Problems with Win2K and IP Address or Long Name We are running Samba 2.05 on Solaris and have run into the following issue. We can connect to the shares on the box from any box when using the short name (ie \\Bob), but not the long name (\\bob.domain.com) or the ip address (\\172.17.19.104). When using Windows 2000, the default method of access is to use DNS to resolve the name, so even using a short name somehow results in the long name being sent. We have verified that the issue is with the long name by removing our domain name from the client and connections work fine. Is there a reason why the server would reject the long name and the IP address, but allow the short (netbios) name. This doesn't really make sense, as we can access other features on the box (telnet, ssh, etc) using the fully qualified DNS name. Additional information: Everything worked last week, even from Windows 2000 boxes. Something probably changed, but we did not make a deliberate change to the Samba configuration, except in troubleshooting this problem. Matt Dobbertien NT Administrator nistevo mdobbertien@nistevo.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba