All right. We found the answer by doing a packet sniff and following the trail. It turns out that Windows 2000 uses port 445 to connect to an SMB server. This is a change from NT which only used 139. We had a web server running on port 445 for testing which would reply to the packets. When this server was turned off, the problem went away. When using the short name, we were using netbios to resolve the name, so Windows 2000 negotiated with the server in the older style (port 139) and worked correctly. Thanks for your suggestions. Matt Dobbertien NT Administrator nistevo 952-294-1955 mdobbertien@nistevo.com -----Original Message----- From: MCCALL,DON (HP-USA,ex1) [mailto:don_mccall@hp.com] Sent: Thursday, April 19, 2001 12:30 PM To: 'Matt Dobbertien'; 'samba@lists.samba.org' Subject: RE: 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