OS 10.5 - 10.5 cannot connect to SMB share

Bigtwenty · Bigtwenty #1 (**permalink**)

08-26-2009, 12:13 PM

Ok, here is the story. We replaced a Linux server at a client site with a native windows one (details aren't important why). The environment is mostly windows PC's with about 10 macs. On Monday, Tuesday and Wednesday, everything was running fine. Thursday came around and all of a sudden, macs running Leopard cannot connect to the SMB shares on this server only by dns name only. The Tiger macs are unaffected and running fine.

Say if you run (SMB://IP address) it ask for credentials and connect you fine. But if you run (SMB://Windows Server name) it will tell you the server is not there and to check the connection and your INTERNET connection. But if you try to hit the share on the other server which is Linux by name, it is fine. Again, the tiger macs are unaffected. Also, if you try to browse the network, the server is listed, but not accessible. You can ping the server by dns name and it will resolve to the right ip and everything.

So, it seems to me that there is a difference in the SMB daemon between tiger and leopard. I was wondering if there was a recent update that updated the daemon or if anyone has ever experienced this before.

Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
automount error when mapping users home directory on smb share	pnm_uk	OS X - Operating System	0	05-14-2007 02:36 PM
OS X connect to NFS share with a space in directory name	icpeanuts	Internet, Networking, and Wireless	4	05-11-2007 12:35 PM
Problems with SMB and Windows 2000 Server	Hoppers	Internet, Networking, and Wireless	0	01-26-2005 07:02 AM
can't connect to an NTFS PC	zanoncello	OS X - Operating System	2	01-05-2005 02:53 AM
Can't connect to W2K server share "error 36" using SMB	fittecho	OS X - Operating System	7	07-18-2004 07:03 PM

OS 10.5 - 10.5 cannot connect to SMB share

Internet Services

Web Development

Digital Marketing

Consumer Tech

Bigtwenty #1 (permalink)
Member Since: Oct 02, 2008 Posts: 5	08-26-2009, 12:13 PM Ok, here is the story. We replaced a Linux server at a client site with a native windows one (details aren't important why). The environment is mostly windows PC's with about 10 macs. On Monday, Tuesday and Wednesday, everything was running fine. Thursday came around and all of a sudden, macs running Leopard cannot connect to the SMB shares on this server only by dns name only. The Tiger macs are unaffected and running fine. Say if you run (SMB://IP address) it ask for credentials and connect you fine. But if you run (SMB://Windows Server name) it will tell you the server is not there and to check the connection and your INTERNET connection. But if you try to hit the share on the other server which is Linux by name, it is fine. Again, the tiger macs are unaffected. Also, if you try to browse the network, the server is listed, but not accessible. You can ping the server by dns name and it will resolve to the right ip and everything. So, it seems to me that there is a difference in the SMB daemon between tiger and leopard. I was wondering if there was a recent update that updated the daemon or if anyone has ever experienced this before. Thanks
	QUOTE Thanks

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)