Hi Guys
I got this samba server problem and I have been struggling for a month not being able to resolve.
The samba server is setup in home network with ip: 192.168.1.123 which is a Freebsd8, and all my windows clients can connect to the shares, I can also mount them when windows startup. Main problem here is that: From a macbook pro, no matter what I try, I can not connect to any share, nor I can even connect to the server and browse those shares.
I have checked the allowed ip addresses, permission, none of them should be problem. I am having some problems wih samba,but just not sure what the cause is or there is any connection to the mac problem. They are:
1. When I connect to samba SWAT admin from Lan, the web page opening is extreamly slow,it'll take 10~20 seconds to load a page. I can use both ip or a hostname(eg, dev:901, I setup the dev.abc as hostname in freebsd) to visit the SWAT. However if I visit the same SWAT from KDE in freebsd box itself, eg: localhost:901, the page loading is quick and immediately.
I suspect some settings related to hostname, or name binding in Freebsd is not properly,so that it'll always check hostname matching ip etc. But I am just not familar with all these naming issue. Any idea?
2. Similarly, with the name issue. I can visit share in windows by hostname but not ipaddress, eg: I can use: \\dev\share to mount in windows, but it will not work if I use ip, eg: \\192.168.1.123\share, this seems worked before I upgrade from freebsd7 to freebsd8 and also upgrade the samba server. In macbook pro, none of either way(ip or hostname) works.
3. I have done some tests in office and tested that the macbook pro can smoothly connect to other windows share drive with specifying: smb:\\ip, then choose what share to mount. So any idea what the really issue with my case?
Any help is much appreciated.
Cheers,
Stephen
I got this samba server problem and I have been struggling for a month not being able to resolve.
The samba server is setup in home network with ip: 192.168.1.123 which is a Freebsd8, and all my windows clients can connect to the shares, I can also mount them when windows startup. Main problem here is that: From a macbook pro, no matter what I try, I can not connect to any share, nor I can even connect to the server and browse those shares.
I have checked the allowed ip addresses, permission, none of them should be problem. I am having some problems wih samba,but just not sure what the cause is or there is any connection to the mac problem. They are:
1. When I connect to samba SWAT admin from Lan, the web page opening is extreamly slow,it'll take 10~20 seconds to load a page. I can use both ip or a hostname(eg, dev:901, I setup the dev.abc as hostname in freebsd) to visit the SWAT. However if I visit the same SWAT from KDE in freebsd box itself, eg: localhost:901, the page loading is quick and immediately.
I suspect some settings related to hostname, or name binding in Freebsd is not properly,so that it'll always check hostname matching ip etc. But I am just not familar with all these naming issue. Any idea?
2. Similarly, with the name issue. I can visit share in windows by hostname but not ipaddress, eg: I can use: \\dev\share to mount in windows, but it will not work if I use ip, eg: \\192.168.1.123\share, this seems worked before I upgrade from freebsd7 to freebsd8 and also upgrade the samba server. In macbook pro, none of either way(ip or hostname) works.
3. I have done some tests in office and tested that the macbook pro can smoothly connect to other windows share drive with specifying: smb:\\ip, then choose what share to mount. So any idea what the really issue with my case?
Any help is much appreciated.
Cheers,
Stephen