Debugging CIFS / samba on Windows

From: graphitone19 Jun 2016 07:29
To: Peter (BOUGHTONP) 16 of 52
You've got an apipa on the Ethernet connection and a class b subnet, I take it you're using the wireless to connect from the windows machine to the network, it shouldn't make a difference but have you tried disabling the Ethernet adapter?
From: Peter (BOUGHTONP)19 Jun 2016 12:31
To: graphitone 17 of 52
Nope, the wireless connection goes to the Internet.

The NAS is connected via Ethernet to the same switch as the Windows machine. (The NAS doesn't connect to wifi.)

From: CHYRON (DSMITHHFX)19 Jun 2016 14:47
To: Peter (BOUGHTONP) 18 of 52
Can you restore from backup to when it was working?
From: Peter (BOUGHTONP)19 Jun 2016 15:00
To: CHYRON (DSMITHHFX) 19 of 52
Only if you can supply me with a time machine so I can go back and create a restore point...
From: ANT_THOMAS19 Jun 2016 15:21
To: Peter (BOUGHTONP) 20 of 52
Turned off system restore?

Definitely don't have access to another windows system just to try?
From: CHYRON (DSMITHHFX)19 Jun 2016 16:02
To: Peter (BOUGHTONP) 21 of 52
Pretty sure Ant can build you one with a rasberry pi.
From: Peter (BOUGHTONP)19 Jun 2016 16:57
To: ANT_THOMAS 22 of 52
Nope, but there's only one restore point - created automatically on Friday evening - so that doesn't help. (Ticked the "Show more" checkbox and nothing else appears. Damned thing.)

I have no other active Windows boxes, and I'm not faffing around finding and swapping the harddrive I took out of my netbook since I'm approximately 5000% certain the NAS is correctly configured and the issue is with this Windows instance.

From: patch19 Jun 2016 18:23
To: Peter (BOUGHTONP) 23 of 52
Does the network interface use DHCP or a static address? Either way, you shouldn't be getting a 169.254 address on the interface, so either check that DHCP is still working, or assign a new address to the interface.
From: Peter (BOUGHTONP)19 Jun 2016 18:56
To: patch 24 of 52
No DHCP server, afaik. I did originally intend to setup DHCP+DNS on my Pi but didn't have time initially and then everything was working with 169.254 so I just left it.
From: ANT_THOMAS19 Jun 2016 19:27
To: Peter (BOUGHTONP) 25 of 52
Do you still not have a phone line?
From: graphitone19 Jun 2016 19:43
To: patch 26 of 52
Aye, s'what I was thinking.
From: koswix19 Jun 2016 19:43
To: Peter (BOUGHTONP) 27 of 52
Can you connect to anything else on the Ethernet adapter? Config looks a bit... nonstandard.
From: ANT_THOMAS19 Jun 2016 19:46
To: koswix 28 of 52
Don't be shocked.
From: patch19 Jun 2016 19:54
To: graphitone 29 of 52
The network engineer in me thinks that 169.254 should never be used so that it's obvious when they crop up that something is wrong. But then there's at least one example of paid work that I've done which uses them for the wireless access points VLAN. Such a cowboy.
From: Chris (CHRISSS)19 Jun 2016 19:55
To: Peter (BOUGHTONP) 30 of 52
Give it a proper IP address and see if that helps.
From: ANT_THOMAS19 Jun 2016 20:05
To: patch 31 of 52
Definitely some totally unconventional setup going on here, which is no surprise.
From: Peter (BOUGHTONP)19 Jun 2016 21:18
To: koswix 32 of 52
I can SSH to the Pi via it - at present only the three devices are connected.
From: Peter (BOUGHTONP)19 Jun 2016 21:18
To: ANT_THOMAS 33 of 52
Hey, I'm still celebrating finally having a device that does 4G. :C
From: Peter (BOUGHTONP)19 Jun 2016 21:19
To: Chris (CHRISSS) 34 of 52
Yep, gonna have a go at setting up the Pi as a DHCP server, but probably tomorrow when I'm (hopefully) less tired.
From: Peter (BOUGHTONP)19 Jun 2016 21:19
To: ANT_THOMAS 35 of 52
There's nothing deliberately unconventional - it really was just get the NAS connected enough to shunt files around and make space on the main machine and I'll set things up properly later, then it's always just been oh it's working good enough for now.

I fecking hate "good enough for now". :@