Hi all, I've 3 machines : one with w* XP, another with SuSE 10.1 and another with SuSE 9.2. The machine with SuSE 9.2 is, also, a samba server. Everything was working fine : all machines could see, read and write in my w* XP machine and SuSE 9.2 and, today, I have already done some transfers from w* to SuSe 10.1. Suddenly none of my Linux machines can see, read or write on my w* XP machine, but the w* XP can do it in my SuSE 9.2 with the samba server. Any ideas? -- Regards, Lívio Cipriano
On Tuesday 24 October 2006 23:56, Lívio Cipriano wrote:
Hi all,
I've 3 machines : one with w* XP, another with SuSE 10.1 and another with SuSE 9.2. The machine with SuSE 9.2 is, also, a samba server.
Everything was working fine : all machines could see, read and write in my w* XP machine and SuSE 9.2 and, today, I have already done some transfers from w* to SuSe 10.1.
Suddenly none of my Linux machines can see, read or write on my w* XP machine, but the w* XP can do it in my SuSE 9.2 with the samba server.
Hi Livio, Here's how I'd troubleshoot it: 1. Make sure that there's no firewall blocking the samba connection. Some antivirus program can be blocking it too. 2. Try accessing the winxp using IP address. HTH, -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 12:06am up 1:00, 2.6.16.13-4-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
-------- On 24 October 2006 18:08, Fajar Priyanto wrote: --------
2. Try accessing the winxp using IP address.
Well... it worked. None of the other options verified. The mystery, now, is why doesn't the w* XP machine is broadcasting is name? Might be a conflict with my SuSE 9.2 samba server? But the never happen... -- Regards, Lívio Cipriano
On Wednesday 25 October 2006 00:19, Lívio Cipriano wrote:
-------- On 24 October 2006 18:08, Fajar Priyanto wrote: --------
2. Try accessing the winxp using IP address.
Well... it worked. None of the other options verified.
The mystery, now, is why doesn't the w* XP machine is broadcasting is name? Might be a conflict with my SuSE 9.2 samba server? But the never happen...
If the XP has just been rebooted, usually it takes a couple of minutes (up to 5 minutes) for the other machines on the network to recognize it. Unless there's a WINS server serving the network. -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 12:52am up 1:47, 2.6.16.13-4-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
-------- On 24 October 2006 18:54, Fajar Priyanto wrote: --------
If the XP has just been rebooted, usually it takes a couple of minutes (up to 5 minutes) for the other machines on the network to recognize it
That it's true, but seams that my linux machines are unable to translate the netbios names into IP addresses or the xp machine stoped broadcasting is netbios name. -- Regards, Lívio Cipriano
On Tuesday 24 October 2006 16:26, Lívio Cipriano wrote:
-------- On 24 October 2006 18:54, Fajar Priyanto wrote: --------
If the XP has just been rebooted, usually it takes a couple of minutes (up to 5 minutes) for the other machines on the network to recognize it
That it's true, but seams that my linux machines are unable to translate the netbios names into IP addresses or the xp machine stoped broadcasting is netbios name.
run (as root) rcnmb restart on the samba server. Occasionally Samba on 9.3 and earlier, will get its nmb in such a state that it fails to work properly, and/or it gets de-throned as the browse-master. Set you samba to have a higher os version than any of the others (say something like 64) so it always wins brows-master elections. -- _____________________________________ John Andersen
On Wednesday 25 October 2006 07:26, Lívio Cipriano wrote:
-------- On 24 October 2006 18:54, Fajar Priyanto wrote: --------
If the XP has just been rebooted, usually it takes a couple of minutes (up to 5 minutes) for the other machines on the network to recognize it
That it's true, but seams that my linux machines are unable to translate the netbios names into IP addresses or the xp machine stoped broadcasting is netbios name.
In that case, make sure that nmb is started. Or better yet, let's set and restarted it: chkconfig smb on chkconfig nmb on service smb restart service nmb restart -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 11:00am up 0:24, 2.6.16.13-4-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
On Tuesday 24 October 2006 20:02, Fajar Priyanto wrote:
On Wednesday 25 October 2006 07:26, Lívio Cipriano wrote:
-------- On 24 October 2006 18:54, Fajar Priyanto wrote: --------
If the XP has just been rebooted, usually it takes a couple of minutes (up to 5 minutes) for the other machines on the network to recognize it
That it's true, but seams that my linux machines are unable to translate the netbios names into IP addresses or the xp machine stoped broadcasting is netbios name.
In that case, make sure that nmb is started. Or better yet, let's set and restarted it: chkconfig smb on chkconfig nmb on service smb restart service nmb restart
Why wouldn't you do that the Suse way: rcnmb restart Lots easier. -- _____________________________________ John Andersen
Maybe is a wrong strategy, but I named my internal network as belonging to a arcadia.pt domain. The sun.arcadia.pt is the xp machine. Apparently, yesterday, the arcadia.pt domains and sun.arcadia.pt were activated; as you can check. So, when a linux machine wanted to resolve the sun.arcadia.pt name, because I hadn't this name in my host list, queried the dns server of my isp and it returned the ip of this "new" sun.arcadia.pt host. -- Regards, Lívio Cipriano
participants (3)
-
Fajar Priyanto -
John Andersen -
Lívio Cipriano