Debugging CIFS / samba on Windows

From:	graphitone	19 Jun 2016 20:29
To:	patch Peter (BOUGHTONP)	37 of 52

41764.37 In reply to 41764.29
Yeah, as I said somewhere above, the 169.254.X.X range is the automatic private IP addressing, usually only used by default when a client machine can't connect anywhere and gives itself an address. I can imagine PB using it for his network address though. :C Making sure everything's on the same subnet should be the first thing to check, unless PB's got a huge amount of hosts or some weird routing somewhere, it should only need a /24 range, looking at the ipconfig, he's got a /16 on the windows box. PB - what're the IP settings on the NAS? Drawings n' that

0/0

Reply Quote

More

From:	ANT_THOMAS	19 Jun 2016 20:37
To:	Peter (BOUGHTONP)	38 of 52

41764.38 In reply to 41764.35
Get a proper router and use that as your DHCP server. Don't arse about with other devices. Do it a more conventional way and it'll no doubt work properly. A

0/0

Reply Quote

More

From:	Peter (BOUGHTONP)	19 Jun 2016 20:39
To:	graphitone	39 of 52

41764.39 In reply to 41764.36
The router is my mobile, using wifi tethering. The NAS and Pi are on ethernet only, connected via a dumb switch. `3.1415P265E589T932E846R64338`

0/0

Reply Quote

More

From:	Peter (BOUGHTONP)	19 Jun 2016 20:40
To:	graphitone	40 of 52

41764.40 In reply to 41764.37
The NAS is 169.254.184.206 and matching 255.255.0.0 subnet (again, this was working fine for six months). You'll be delighted to know that when I setup DHCP I'm gonna use class A. :> `3.1415P265E589T932E846R64338`

0/0

Reply Quote

More

From:	ANT_THOMAS	19 Jun 2016 20:43
To:	Peter (BOUGHTONP)	41 of 52

41764.41 In reply to 41764.35
I've actually done what you're doing years ago and I was able to use a more conventional network setup. Probably easier using static IPs. I had a small access point in client mode attached to the network via a cable and then wireless to the phone. This meant whenever the tethering was enabled the network got Internet access. Meant only a single wifi connection to the phone to get everything online. A

0/0

Reply Quote

More

From:	graphitone	19 Jun 2016 21:32
To:	Peter (BOUGHTONP)	42 of 52

41764.42 In reply to 41764.40
:-O :-O~~~ Drawings n' that

0/0

Reply Quote

More

From:	patch	20 Jun 2016 05:36
To:	graphitone	43 of 52

41764.43 In reply to 41764.37
APIPA uses a /16 mask by default, so that's no biggy. If you can ping and ssh, then you know the connectivity is there, so it's either something in the PCs network adapter, or the NAS itself. Perhaps try deleting the NIC from the PC and then adding it again after a reboot. That might (might!) set it up with the default settings.

0/0

Reply Quote

More

From:	graphitone	20 Jun 2016 09:35
To:	patch Peter (BOUGHTONP)	44 of 52

41764.44 In reply to 41764.43
Aye, it's usable o' course, just unusual to see it - it always makes me think that the host has lost connectivity, but if PB's NAS is on the same range then all's ok. Does the PC just have the one NIC? Drawings n' that

0/0

Reply Quote

More

From:	Peter (BOUGHTONP)	20 Jun 2016 18:47
To:	patch	45 of 52

41764.45 In reply to 41764.43
"try deleting the NIC" Do you mean go into Device Manager, Network adapters, and uninstall the relevant option - or something else? `3.1415P265E589T932E846R64338`

0/0

Reply Quote

More

From:	patch	21 Jun 2016 05:21
To:	Peter (BOUGHTONP)	46 of 52

41764.46 In reply to 41764.45
That's the one. No idea whether it will work, but it's worth a shot. The worst that happens is a full re-install, and it's probably about time you did that anyway.

0/0

Reply Quote

More

From:	Peter (BOUGHTONP)	21 Jun 2016 20:45
To:	patch	47 of 52

41764.47 In reply to 41764.46

A full re-install may happen if hell freezes over, but not before.

I did it without re-starting yesterday and got a new 169 IP address, but no luck with the shares.

At some point I might have a go at inspecting packets with Wireshark to see what's actually going on, but for the time being I'll make do with FTP. :(

3.1415P265E589T932E846R64338

0/0

Reply Quote

More

From:	ANT_THOMAS	21 Jun 2016 21:15
To:	Peter (BOUGHTONP)	48 of 52

41764.48 In reply to 41764.47
NFS? A

0/0

Reply Quote

More

From:	graphitone	21 Jun 2016 21:30
To:	Peter (BOUGHTONP)	49 of 52

41764.49 In reply to 41764.47
<pointing out the bleedin' obvious> Are you sure the Windows box hasn't been assigned the same IP as the NAS? Drawings n' that

0/0

Reply Quote

More

From:	Peter (BOUGHTONP)	21 Jun 2016 22:33
To:	ANT_THOMAS	50 of 52

41764.50 In reply to 41764.48
That requires me to determine why my "Turn Windows features on or off" list is blank, of which there's a variety of possible causes/solutions and it's not the common ones. :( (Or locate a third-party client, but a quick check of the options didn't uncover anything acceptable; everyone recommends the Microsoft one.) `3.1415P265E589T932E846R64338`

0/0

Reply Quote

More

From:	ANT_THOMAS	21 Jun 2016 22:44
To:	Peter (BOUGHTONP)	51 of 52

41764.51 In reply to 41764.50
Sounds like hell has just frozen over. A

0/0

Reply Quote

More

From:	Ken (SHIELDSIT)	3 Jul 2016 18:07
To:	Peter (BOUGHTONP)	52 of 52

41764.52
Doesn't Windows assign a 169 address when it can't actually get a "good" address from DHCP? I think you really need to use a different IP range. Another thing, did you say you're using a wireless adapter for internet and a wired adapter to only access the NAS? If that's the case, I've had times where the adapters come up in the wrong order and one doesn't work. I would disable the wireless adapter and try to access the NAS. What happens is Windows looks for the NAS over the wireless adapter and of course it won't find it there. ------------------------------------------------------------------------ "If you don't like donut, then leave it alone. Nobody force you to eat it."

0/0

Reply Quote

More