Author Topic: LAN detection almost completely dead (Read 1377 times)

paul1149 · « **on:** July 17, 2012, 07:28:31 AM »

Hi,

I've got a new PCLos install on an older machine, and I'm trying to set up local sharing. In the Control Center I ran through the Samba wizard, using plain vanilla settings.

On a Win7 machine the linux machine doesn't show up at all in Explorer.
On the linux machine, the WORKGROUP shows up in dolphin, but it times out without showing any machines.
In the PCLinux Control Center the Win7 machine shows up, but shows no shares.

It's basically dead in the water, and I don't even understand why the Control Center and Dolphin are not behaving the same.

Thanks.

T6 · « **Reply #1 on:** July 17, 2012, 08:17:33 AM »

did you set a static ip?

did you shared any resource?

paul1149 · « **Reply #2 on:** July 17, 2012, 08:19:43 AM »

No, I left the IP DHCP. I created a share on my desktop on the pclinux box.

T6 · « **Reply #3 on:** July 17, 2012, 08:21:41 AM »

nothing shared on windows?

did you set a firewall in linux? maybe you are blocking this service

paul1149 · « **Reply #4 on:** July 17, 2012, 08:23:27 AM »

I have several Windows shares. And no firewall in linux. I'm also using User authentication in Samba, but haven't gotten so far as to use it.

menotu · « **Reply #5 on:** July 17, 2012, 09:19:50 AM »

Quote from: paul1149 on July 17, 2012, 08:23:27 AM

I have several Windows shares. And no firewall in linux. I'm also using User authentication in Samba, but haven't gotten so far as to use it.

Just a thought - is samba-winbind installed?

And might be useful checking if all necessary "services" are running by checking in:

PCC > System > Manage System Services by enabling them or disabling them

paul1149 · « **Reply #6 on:** July 17, 2012, 09:56:35 AM »

Thank you. That cleared up some of the problem.

Yes, I had checked early on through Synaptic that samba-winbind is installed. But when I went looking for where to configure samba, and found the PCC samba wizard, I assumed that it would flag me if anything were lacking regarding the samba setup. It didn't.

Under the Manage System Services, both services were Stopped. I enabled them on boot, started samba, but it would not allow me to start winbind until it was "configured" in smb.conf. That apparently means to uncomment all the winbind options, which I did, despite not knowing what most of them do.

I restarted samba and then was able to start winbind.

Now I can see the share folder I created in linux. But I can also see my entire Home directory structure. What's more, no password query ever arose.

At the same time, linux now cannot see even the workgroup on the lan.

I then went into samba and removes the Homes entry, because I could not get the "Public" options to give it any security. When I did that, now Win7 doesn't see the linux box at all again. I did not touch the individual share folder I had created.

None of this makes sense to me, and I'm sorry to say that I'm getting frustrated at this point.

muungwana · « **Reply #7 on:** July 17, 2012, 10:01:10 AM »

go to your windows 7 computer's firewall and make sure the firewall is configured to allow traffic on port 138,139 and 445.

restart samba on linux and then try to see if the shares show up.

paul1149 · « **Reply #8 on:** July 17, 2012, 10:23:52 AM »

I just dropped the Win firewall completely, and restarted Samba. Still can't see the windows machine, but now windows saw my linux share again. Then I reenabled the Win firewall, and still could see the linux share.

BTW, I have had this win box sharing with other boxes, win and linux (ubuntu, mostly), even up till yesterday. I don't think the problem lies there.

Thanks.

muungwana · « **Reply #9 on:** July 17, 2012, 10:33:33 AM »

you should keep the firewall off while you are trying to solve the problem.

how many computers do you have on your network?

run this command and post its output

smbtree -N -d2

paul1149 · « **Reply #10 on:** July 17, 2012, 07:32:03 PM »

There will be anywhere from one to five machines on the LAN. Here is that command. MPCCLIENT is the pclinux box. The others are Win7 and XP:

smbtree -N -d2
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface eth0 ip=fe80::20c:f1ff:fe7f:7975%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.1.188 bcast=192.168.1.255 netmask=255.255.255.0
tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied
Got a positive name query response from 192.168.1.136 ( 192.168.1.136 )
Got a positive name query response from 192.168.1.136 ( 192.168.1.136 )
Got a positive name query response from 192.168.1.136 ( 192.168.1.136 )
WORKGROUP
Got a positive name query response from 192.168.1.136 ( 192.168.1.136 )
\\UNNA Unna
Error connecting to 67.215.65.132 (Success)
cli_start_connection: failed to connect to UNNA<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
\\PRECISION
Error connecting to 67.215.65.132 (Success)
cli_start_connection: failed to connect to PRECISION<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
\\MPCCLIENT localhost
Error connecting to 67.215.65.132 (Success)
cli_start_connection: failed to connect to MPCCLIENT<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL

muungwana · « **Reply #11 on:** July 17, 2012, 07:45:45 PM »

A computer on your network with an IP address of "192.168.1.136" is the one that runs what is called "local master server".

Go this computer and configure its firewall to allow traffic on port 138,139 and 445.

restart samba on your linux box and rerun the command and give its output.

any reason why samba is trying to connect to a publicly addressable IP address?

paul1149 · « **Reply #12 on:** July 17, 2012, 08:28:48 PM »

That is an old xp box that may or may not be on at any given time. Is there any way to configure this so nothing depends on it?

muungwana · « **Reply #13 on:** July 17, 2012, 09:25:58 PM »

I am working under an assumption that a local master server is behind a firewall and that is what is causing the problem.

A local master server is a computer on the network that is responsible for managing other computer's list of network resources.

having 5 computers that may or may not be master servers and may or may not be behind a firewall introduces too many variables.

you can try shutting down all firewalls or disconnect other computers and see if you can get things to work first.

paul1149 · « **Reply #14 on:** July 18, 2012, 07:24:28 AM »

I would have to arrange access to that xp box, so instead this morning I ran the test again while it was offline. Only the Win7 box and PCLINUX were online, and it looks like Win7 had been assigned master server status - which makes sense since it was the first machine online.

I first ran the smbtree command, and this time the response was extremely verbose. Then I dropped the Win7 firewall, and it was more compact. But still, neither machine saw the other.

Then I went into smb.conf and commented out:
hosts allow = 192.168.1. 192.168.2. 127.

Immediately Win7 could see and access the pcl share - without a password. Both machines use the same user credentials, but they still should require a login. PCL still could not see Win7.

Here is the second attempt, after the Win7 FW was dropped:

smbtree -N -d2
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface eth0 ip=fe80::20c:f1ff:fe7f:7975%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.1.188 bcast=192.168.1.255 netmask=255.255.255.0
tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied
Got a positive name query response from 192.168.1.3 ( 192.168.1.3 )
Got a positive name query response from 192.168.1.3 ( 192.168.1.3 )
Got a positive name query response from 192.168.1.3 ( 192.168.1.3 )
WORKGROUP
Got a positive name query response from 192.168.1.3 ( 192.168.1.3 )
\\PRECISION
Error connecting to 67.215.65.132 (Success)
cli_start_connection: failed to connect to PRECISION<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
\\MPCCLIENT localhost
Error connecting to 67.215.65.132 (No route to host)
cli_start_connection: failed to connect to MPCCLIENT<20> (0.0.0.0). Error NT_STATUS_HOST_UNREACHABLE

I'll skip the first attempt, when the Win 7 fw was up, as it's very long and i don't see the utility of it.

The mystery is why samba is trying to access an external IP address. Something seems very wrong with that. The address seems to be on my ISP's network, but it is not my own.

Thanks.

PCLinuxOS-Forums

News: