I have two laptops with Fedora 20 installed (1 32bit an old Acer Aspire and 1 Acer Aspire I5 64bit). Both are fully up to date.
Now the problem only exists on the older laptop. My lan has a mixture of F20 and W2K on the various PCs plus a NAS. On this older laptop if I am connected via its wireless connection I can see all the PC names but not the IP addresses only some. If I connect via its cable to my switch I can always see all the PCs and all of the IP addresses. Usually I can see the older laptop itself and my desktop IPs and not the W2K and NAS IPs.
Also from my F20 Desktop I can see everything just fine except I cannot see the IP address of this older laptop if it is connected via wireless but I can see (and mount its share) OK if it connected via cable.
The new Acer laptop behaves exactly like the desktop whether it is connected by wireless or by cable.
It makes no difference if I restart the nmb and smb services on the older laptop when connected by wireless. Both laptops connect via the same access point and their wireless IP addresses are in the same range and are fixed.
The smb.conf on both laptops is the same (apart from share definitions).
Anyone have any ideas please as to how to progress this problem?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for answering late, I'm quite busy at the moment, so it sometimes takes some time until I'm able to respond.
This issue is quite strange, but not critical as I understand. Anyway, is the Samba installation identical on the 32bit and the 64bit system? Or is the package selection different?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No problem Alexander, also I've just been away for a few days which is why this reply is late - sorry. I believe it is the same but I'll check later today.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I fired up my desktop today after being away for a week and there were about 140 updates including some Samba stuff so I let it update. I also fired up the laptop I was having problems with and let it update as well as there were the same Samba updates. The net result is that it all seems to be working at present following the updates. No way to be sure that this is what fixed it but will keep an eye on things over the next few days and see what happens.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well it happened again yesterday with the old laptop, while on wireless I could not see all of the devices IP addresses but could see my own IP and that of the desktop PC. On the desktop PC I could not see the IP of the laptop. Once on wired lan all seemed to be fine again. If I tried to access a device from the laptop (which did not show IP in SMB4K) using the smb://dotted.ip.address in Dolphin it worked and displayed the folder contents just fine.
Are there any commands I should issue or anything else I should try to get more info if/when it happens again?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am now seeing this strange behaviour again. Running Fedora 20 desktop and trying to see shares on a Windows 8.1 laptop. If I connect the laptop to the wired lan it sees the computer name and ip address OK and I can mount the shares. However if I connect it wirelessly I can only see the computer name and it does not find the ip address so cannot browse the shares. If I use the smb://ip.address in Dolphin it works OK and can browse the shares, however if I use smbclient -L ip.address it fails with session setup failed: NT_STATUS_LOGON_FAILURE
Any ideas please?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not have any ideas at the moment, but an observation: I've got a FritzBox router. Smb4K - more precisely: nmblookup - is not able to detect the IP address. In the upcoming version of Smb4K I've implemented the optional usage of the net command for IP address detection. Using net instead of nmblookup retrieves the IP address correctly.
So, what I suggest that you could try is to execute the following two commands and see what the result is:
$ nmblookup -- <server_name>
$ net lookup host <server_name>
If the latter returns the IP address, I can offer you to prepare a tarball of the latest development snapshot so you can try out the newest version of Smb4K with the above mentioned feature.
Alexander
Last edit: Alexander Reinholdt 2014-08-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well neither of those commands find my W8.1 laptop however if I do
nmblookup -A 192.168.0.21
Looking up status of 192.168.0.21
JANIESLAPTOP <00> - B <ACTIVE>
JANIESLAPTOP <20> - B <ACTIVE>
DISORGANISATION <00> - <GROUP> B <ACTIVE>
DISORGANISATION <1e> - <GROUP> B <ACTIVE>
MAC Address = 68-94-23-28-89-D7
as you can see it finds it.
In case it matters the laptop connects via a wireless access point not my router. As I have a second wireless ap I thought I'd try to connect the laptop via that and I then found that SMB4K does find the laptops IP address and both your commands work fine returning the IP. I guess this complicates what is going on. Could it be the first ap which is causing the problem? The one which fails is actually the remote end of a homeplug downstairs in the house, and the one which works is connected directly upstairs to my gigabit switch. Both these ap's are made by TPLink! The laptop normally connects to the downstairs ap.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two laptops with Fedora 20 installed (1 32bit an old Acer Aspire and 1 Acer Aspire I5 64bit). Both are fully up to date.
Now the problem only exists on the older laptop. My lan has a mixture of F20 and W2K on the various PCs plus a NAS. On this older laptop if I am connected via its wireless connection I can see all the PC names but not the IP addresses only some. If I connect via its cable to my switch I can always see all the PCs and all of the IP addresses. Usually I can see the older laptop itself and my desktop IPs and not the W2K and NAS IPs.
Also from my F20 Desktop I can see everything just fine except I cannot see the IP address of this older laptop if it is connected via wireless but I can see (and mount its share) OK if it connected via cable.
The new Acer laptop behaves exactly like the desktop whether it is connected by wireless or by cable.
It makes no difference if I restart the nmb and smb services on the older laptop when connected by wireless. Both laptops connect via the same access point and their wireless IP addresses are in the same range and are fixed.
The smb.conf on both laptops is the same (apart from share definitions).
Anyone have any ideas please as to how to progress this problem?
Stuart
Sorry for answering late, I'm quite busy at the moment, so it sometimes takes some time until I'm able to respond.
This issue is quite strange, but not critical as I understand. Anyway, is the Samba installation identical on the 32bit and the 64bit system? Or is the package selection different?
No problem Alexander, also I've just been away for a few days which is why this reply is late - sorry. I believe it is the same but I'll check later today.
Stuart
I fired up my desktop today after being away for a week and there were about 140 updates including some Samba stuff so I let it update. I also fired up the laptop I was having problems with and let it update as well as there were the same Samba updates. The net result is that it all seems to be working at present following the updates. No way to be sure that this is what fixed it but will keep an eye on things over the next few days and see what happens.
Stuart
OK. It would be nice if you could keep me informed.
Well it happened again yesterday with the old laptop, while on wireless I could not see all of the devices IP addresses but could see my own IP and that of the desktop PC. On the desktop PC I could not see the IP of the laptop. Once on wired lan all seemed to be fine again. If I tried to access a device from the laptop (which did not show IP in SMB4K) using the smb://dotted.ip.address in Dolphin it worked and displayed the folder contents just fine.
Are there any commands I should issue or anything else I should try to get more info if/when it happens again?
Stuart
I am now seeing this strange behaviour again. Running Fedora 20 desktop and trying to see shares on a Windows 8.1 laptop. If I connect the laptop to the wired lan it sees the computer name and ip address OK and I can mount the shares. However if I connect it wirelessly I can only see the computer name and it does not find the ip address so cannot browse the shares. If I use the smb://ip.address in Dolphin it works OK and can browse the shares, however if I use smbclient -L ip.address it fails with session setup failed: NT_STATUS_LOGON_FAILURE
Any ideas please?
Stuart
Hello Stuart!
I do not have any ideas at the moment, but an observation: I've got a FritzBox router. Smb4K - more precisely: nmblookup - is not able to detect the IP address. In the upcoming version of Smb4K I've implemented the optional usage of the net command for IP address detection. Using net instead of nmblookup retrieves the IP address correctly.
So, what I suggest that you could try is to execute the following two commands and see what the result is:
If the latter returns the IP address, I can offer you to prepare a tarball of the latest development snapshot so you can try out the newest version of Smb4K with the above mentioned feature.
Alexander
Last edit: Alexander Reinholdt 2014-08-17
Well neither of those commands find my W8.1 laptop however if I do
nmblookup -A 192.168.0.21
Looking up status of 192.168.0.21
JANIESLAPTOP <00> - B <ACTIVE>
JANIESLAPTOP <20> - B <ACTIVE>
DISORGANISATION <00> - <GROUP> B <ACTIVE>
DISORGANISATION <1e> - <GROUP> B <ACTIVE>
MAC Address = 68-94-23-28-89-D7
as you can see it finds it.
In case it matters the laptop connects via a wireless access point not my router. As I have a second wireless ap I thought I'd try to connect the laptop via that and I then found that SMB4K does find the laptops IP address and both your commands work fine returning the IP. I guess this complicates what is going on. Could it be the first ap which is causing the problem? The one which fails is actually the remote end of a homeplug downstairs in the house, and the one which works is connected directly upstairs to my gigabit switch. Both these ap's are made by TPLink! The laptop normally connects to the downstairs ap.
Stuart