Question A challenging Home Network/Work Laptop issue - - - are you up for it ?

[spacemanspiff2000]

I'm an experienced computer professional with a home networking-related problem that I simply don't know how to troubleshoot.
My core question is: Where/how do I begin to track this down? I've been living with it for months (and I hate it).

NOTE: For this one, I am intentionally withholding the very detailed information from this initial post because this is quite complex, and I don't know what components will be important here. In fact, though it probably doesn't show, I've put a lot of work into just choosing/crafting how to approach this description, to make it accessible to folks who aren't living with it. The main reason I've been living with this for months is because I cannot just "shoot off a quick cry for help" for this ... and the living of life has been quite busy.

In short, let's just say I have enough experience at this to expect that essentially no one would read a long wall of text containing every detail. But if you have ideas about the best places to look for the root cause of this, just ask and I'll provide the relevant details requested.

So, starting just with the symptoms and how they occur...

BEFORE / WORKING FINE (I'll call this "Config 0"):
-- Verizon FiOS router (old)
-- TP Link WiFi mesh (M9)
-- FreeBSD server running Samba & Plex Server
-- Win10/11 (mostly Enterprise) desktop PCs and laptops
-- one DELL work-provided, work-managed, Win10Ent laptop that I have admin rights to (but which my employer still loosely monitors, regularly patches/upgrades, etc.)

Under these conditions, every PC & laptop I have could map drives to the FreeBSD/Samba server, copy files, run Plex without incident, remote control to each other (via TightVNC), etc. A veritable paradise of computer functioning.

...until paradise was lost...

AFTER = SEMI-WORKING:
-- T-Mobile gateway [we moved; no VZ FiOS out here]
-- same TP Link WiFi mesh
-- same FreeBSD server running same OS version, same Samba, same Plex Server, etc.
-- same Win10/11 desktop PCs and laptops
-- same DELL work-provided, work-managed laptop
That's just one "AFTER" layout ... I'll call it "new Config A"), but...

ADDED LATER:
-- new Mikrotik Ethernet Gigabit Router (btwn gateway and mesh)
I'll call this setup with the new router "new Config B."


UNDER BOTH OF THESE "NEW" CONFIGURATIONS, the following occurs:

** WORST THING: DELL work-laptop simply refuses to map drives to FreeBSD server
(I have to TightVNC to a desktop in order to transfer files from work laptop to/from the server, barring physical measures of course)
----- mapping attempts to the static IP address and share name consistently return: "Error code 0x80070079
The semaphore timeout period has expired."
(which, of course, I have tried to track down, to no avail here)

I don't have any faith that the error message in isolation will be enough for this one. The error is just one "star" in a constellation of symptoms that I hope "comes together" for someone here.

** BUT ALSO (more of the constellation):
-- all other laptops in the house can still map drives to FreeBSD
-- connecting to FreeBSD over PuTTY does eventually connect and work, but now takes several noticeable beats longer than when under Config 0

-- In Plex, all of my libraries that are dependent upon the FreeBSD server initially show up with yellow exclamation points and, when clicked on, the message:

"The server "RAID" does not allow secure connections.
Its "Secure connections" setting may be set to disabled, or you may need to adjust some settings on your network. You can ...
The app is loaded insecurely. You can attempt to use an insecure connection now."

And there's a button saying "Allow insecure connections"

BUT if I just wait a good 20-30 seconds, the contents of that library shows up all on its own, and all of the libraries immediate drop the warning marker and go back to normal. Except there are sometimes other, similar library delays later in the session, but never playing any media.

ALSO INTERESTING...
Before the move, I got the T-Mobile gateway to test it at the old place.
If the gateway was my exit point, I had these problems (with the exact same wiring/connectivity there, which is obviously now different at the new place).
Switch back to old VZ FiOS router (Config 0), everything went back to working fine.
Switch back to TM Gateway, these same issues occurred.

NOTE: I have since had to return the VZ equipment, so I no longer have that to test with. I'm 100% on T-Mobile now, and so having these issues 100% of the time.

Finally, back to the original question: Where do I begin to look and try things to resolve this?
Thank you immensely for your time in just reading this.

 

[bill001g]

The main question would be why the router would matter at all. So first a assumption that will change everything if I am not correct. All your devices are talking to equipment that is inside your house and do not need internet to do the function. In the case you say worked if you were to unplug from the fiber node it would continue to function ?

The router in this designs only function is to provide IP addresses. If you used all static IP addresses you could use a simple switch. The lan port on consumer router act as a simple switch anyway. The traffic never passes into the router cpu/software when it goes lan/lan. It only actually enters the router when it is going to the wan.

I can't see how the device you are using as a router would matter.

Now when you say mesh I like to say put that crap in the trash but some people there is no other way. It also depends on how you implemented this. Are you actually running some kind of repeaters that talk to the tmobile/verizon gateway or do you have a mesh hub box between the router and the remote mesh units. Most times when you run actual mesh system that device is running as a router so you now have the double nat issue. Also depending on how you connected it you could have the worse problem of having 2 routers on the same lan that might use the same IP range.

I would try to simplify things adding one part at a time to see when the problem occurs. I would avoid using any kind of wifi connection unless you have no other option. You are going to get random issue because of random interference from neighbors.

 

[_Cosmin_]

So, you admit the problem is with what you call "gateway". It is fiber optic or LTE router or what ?
Now define what that "gateway" provide to your internal network.
Could be as simple as a firewall or some other misconfiguration in your gateway.
On "config B" - what does Mikrotik router provide to your internal network? DHCP and NAT for internal network? What is his role in network and ip range?
Did you ask t-mobile to put that "gateway" in "bridge mode" when you connect the Mikrotik router?
Since your server is in same network with clients plex / samba should run flawlessly without the router/gateway! Also make sure server has a fix ip address (via dhcp reservation or manual)!

 

[Ralston18]

@spacemanspiff2000

Question regarding "And there's a button saying "Allow insecure connections"

Could it be that the default response = "Allow...." and that the system is only waiting for some other possible response during the elapsed 20-30 seconds?

= = = =

Take another look at the existing network topology.

I would expect the network devices and connections to be similar to the following generic line diagram:

ISP === (coax, DSL, fiber) ===> Modem ---->[WAN Port] Router [LAN Port] ----> [LAN Port] Office Wifi Access Point ~~~~> Wireless network devices

With other Router LAN ports -----> Wired network devices.
Feel free to edit and correct my generic "network" diagram as necessary to represent your current network: Especially new config B.

However, identify each device by make and model, and indicate the device's IP address - especially if static.

How are the static IP addresses being assigned? Are you certain that all static IP addresses are reserved by decvice mac and that those static IP addresses are outside of the DHCP IP address range allowed to the router?

Where is that TP-Link mesh connected in? What about FreeNAS?

Also, run "ipconfig /all" (without quotes) on your main computer and post the results. You should be able to copy the results and paste the results here.

Then run "arp -a" and post those results as well.

There should only be one router providing DHCP IP addresses. Most likely the T-Mobile Gateway. With the Mikrotiki DHCP function being disabled.

Also: is the work laptop moved back forth between other networks?

I do believe that more details are necessary in order to track down the potential culprit.

 

[spacemanspiff2000]

Thanks for all of your input on my issue(s).

CURRENT TOPOLOGY LINE DIAGRAMS (Config-B):

ISP (T-Mobile Home Internet [TMHI]) ==> mobile phone tower/airwaves ==> T-Mobile Gateway [TMGW] (192.168.12.1, TM-assigned, cannot be changed) )))wifi/DHCP))) a few, random, irrelevant devices directly connected on .12.x, usually only when wanting to look into the Gateway itself ... or to robo-vacuum.

TMGW (following the wires now...) ==> [WAN Port] Mikrotik Router w/ NAT enabled (static: 192.168.12.250 | static: 192.168.1.1) [DHCP range: 192.168.1.75-110] [LAN Port] ==> TP-Link Deco M9 Plus mesh WiFi Device1 [central] (192.168.1.108; BTW was static x.1.6 under Config0) [mesh Operation Mode = Access Point ("Connects to a wired or WiFi router via an Ethernet cable and extends the wireless coverage of your existing network. Functions like NAT, etc. are not supported in this mode.")] )))wifi/DHCP))) whatever wireless devices are closest/in-range

NOTE1: There is no Mesh Hub ... just 3 "discs" that all operate the same. What I'm calling Mesh Device1 is simply the only one wired to the router.
NOTE2: The router is offering no WiFi services.

Mikrotik Router ==> Brother Laser Printer (static 192.168.1.5) [so that's 3 wires in the router]

)))mesh wifi))) TP-Link Deco M9 Plus wifi mesh Device2 [office] (192.168.1.87) ==> TP-Link TL-SG2008 Smart Switch (managed) ==> ...
==> static: 192.168.1.9 "RAID" FreeBSD server running Samba, Plex Media Server, etc.
[admittedly, the s/w versions of all of ^these^ are "behind" right now, BUT everything else EXCEPT the work laptop will connect drives under these versions]
==> static: 192.168.1.11 desktop running Win10 Enterprise v22H2
[NOTE: This week, just briefly, after a Windows Update (?to v22H2?), after the reboot, all the mapped drives from .11 to the server also semaphored out for a bit ... until they just "woke up" and started working again (which the work laptop never does).]
==> static: 192.168.1.10 my "main" desktop running Win11 Enterprise v22H2

Spoiler: ipconfig & arp data

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : QB3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d5f8:1530:8da0:b0e4%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 148421569
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-28-6A-95-D8-BB-C1-D8-8C-43
DNS Servers . . . . . . . . . . . : 192.168.1.1
68.237.161.12
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Surfshark Windows Adapter V9
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Unknown adapter OpenVPN Data Channel Offload for Surfshark:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : OpenVPN Data Channel Offload
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter vEthernet (Default Switch (Ethernet)):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9f7f:7437:e465:396b%25(Preferred)
IPv4 Address. . . . . . . . . . . : 172.31.176.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 419435869
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-28-6A-95-D8-BB-C1-D8-8C-43
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (Default Switch (Ethernet 3)):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9072:8296:e5cd:8e71%36(Preferred)
IPv4 Address. . . . . . . . . . . : 172.19.176.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 603985245
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-28-6A-95-D8-BB-C1-D8-8C-43
NetBIOS over Tcpip. . . . . . . . : Enabled

C:\>arp -a

Interface: 192.168.1.10 --- 0xa
Internet Address Physical Address Type
192.168.1.1 XX-XX-XX-XX-XX-XX dynamic
192.168.1.5 XX-XX-XX-XX-XX-XX dynamic
192.168.1.9 XX-XX-XX-XX-XX-XX dynamic
192.168.1.11 XX-XX-XX-XX-XX-XX dynamic
192.168.1.82 XX-XX-XX-XX-XX-XX dynamic
192.168.1.91 XX-XX-XX-XX-XX-XX dynamic
192.168.1.105 XX-XX-XX-XX-XX-XX dynamic
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
239.0.0.250 01-00-5e-00-00-fa static
239.255.250.250 01-00-5e-7f-fa-fa static
239.255.255.250 01-00-5e-7f-ff-fa static

Interface: 172.31.176.1 --- 0x19
Internet Address Physical Address Type
172.31.191.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
239.255.250.250 01-00-5e-7f-fa-fa static
239.255.255.250 01-00-5e-7f-ff-fa static

Interface: 172.19.176.1 --- 0x24
Internet Address Physical Address Type
172.19.178.174 00-15-5d-ed-3b-f3 dynamic
172.19.181.190 00-15-5d-ed-3b-51 dynamic
172.19.191.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
239.255.250.250 01-00-5e-7f-fa-fa static
239.255.255.250 01-00-5e-7f-ff-fa static

)))mesh wifi))) TP-Link Deco M9 Plus wifi mesh Device3 [TV/ent ctr] (192.168.1.106) ==> TrendNet TEG-S50g 5-port Switch (unmanaged) ==> Panasonic TV | Yamaha AVR | Xbox Series X | Roku Ultra LT
)))mesh wifi))) a Dell "gaming" laptop [works fine]
)))mesh wifi))) an old ASUS laptop [works fine]
)))mesh wifi))) kid's Chromebook, various Alexa, Google Home, smart outlet devices, etc.

)))mesh wifi))) work-laptop: 192.168.1.105, Dell Latitude 5520 running Win10 Enterprise v21H2, partially managed by my employer
This device is moved around the house to different floors and rooms, but only very very rarely brought into the office anymore.
It connects to the work network over my employer's VPN, of course.

Spoiler: ipconfig & arp data

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : XX-XXX-XXXXXX
Primary Dns Suffix . . . . . . . : win.ad.XXXX.XXX
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : win.ad.XXXX.XXX
home

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (13) I219-V
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1230:9ed9:7643:ed64%20(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.105(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, February 23, 2024 6:42:46 PM
Lease Expires . . . . . . . . . . : Saturday, February 24, 2024 2:21:20 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 191941901
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-E6-78-98-F4-EE-08-C9-56-2D
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\>arp -a
Interface: 192.168.1.105 --- 0x14
Internet Address Physical Address Type
192.168.1.1 XX-XX-XX-XX-XX-XX dynamic
192.168.1.5 XX-XX-XX-XX-XX-XX dynamic
192.168.1.9 XX-XX-XX-XX-XX-XX dynamic
192.168.1.10 XX-XX-XX-XX-XX-XX dynamic
192.168.1.11 XX-XX-XX-XX-XX-XX dynamic
192.168.1.75 XX-XX-XX-XX-XX-XX dynamic
192.168.1.77 XX-XX-XX-XX-XX-XX dynamic
192.168.1.86 XX-XX-XX-XX-XX-XX dynamic
192.168.1.88 XX-XX-XX-XX-XX-XX dynamic
192.168.1.95 XX-XX-XX-XX-XX-XX dynamic
192.168.1.104 XX-XX-XX-XX-XX-XX dynamic
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

NARRATIVE:
The TMHI-GW provides my internet lifeline to the rest of the world, but it is inflexible, essentially non-configurable, and I want it isolated from everything else. So, unless someone in my house connects their device's wifi directly to that network, the non-conflicting DHCP that the TMGW provides does not exist for all intents and purposes, right?

BTW: TMHI was basically the only option out here in the woods where no wires are run, but where a tower is visible. And I feel sufficiently far away from neighbors through those woods to discount interference as an issue.

Under Config-A, without the Mikrotik Router, the Mesh was configured in Router Mode to provide DHCP, etc. (Reminder: I was getting the same results as Config-B later.)

However, I wanted a router with more features (if I wanted to use them), plus I wanted to mimic Config0 as much as possible (where Mesh was just access points to a "real" router), and the TMGW just wasn't cutting it as the "real" router (I'd have to change my entire subnet to 12, for one thing). Also, this router was cheap and feature-rich.

Right now, I'm depending on mesh connections because I don't have wire across the whole house. The TMGW has to stay in the window that faces the tower. I see a (non-simple) way to get wire from the router/gateway area into the Office, but wire to the TV area will be a larger challenge.

All of my static IP addresses are assigned in the configuration within each device (not provided per MAC address centrally). If I didn't note that it's static, then it's DHCP (also apparent by being in the range).

When Plex really means its "Allow insecure connections" screen, it will sit there indefinitely until you press the button ... otherwise you don't move forward.

I'm willing to grant that there may be more than one thing going on here, e.g., the failed mapping of drives possibly separate from the slowness of Plex to "wake up" or the slight-but-noticeable delay in FreeBSD initially responding to PuTTY. It's just that these symptoms all started at the same time, and all oddly & mysteriously went away when switching back to Config0 (when I had that) ... and back again.

Sure, the router probably shouldn't be doing much internally, but these are still the facts as they happened. I can imagine that maybe the Verizon router was doing more than it should have (I wouldn't put it past them), and the absence of whatever that was allowed for what I'm seeing now.

The main issue I would love to overcome under this topology/configuration is the mapping of drives from the Dell Latitude 5520 to the FreeBSD/Samba server, like I used to have.

ALL THAT SAID...

What you're asking for here is directing my focus, which is what I wanted. I'm not an expert in ARP, but given the ARP responses above, I'm now figuring that maybe my core problem is that the work-laptop doesn't have the server in its ARP table. I tried to add it manually, but failed, apparently because I don't 100% manage the local machine:

C:\>arp -s 192.168.1.9 XX-XX-XX-XX-XX-XX The ARP entry addition failed: Access is denied.
[this was run under CMD as Administrator ... without Admin, it responds "requires elevation"]

So, if you agree that getting the server into my work-laptop's ARP config would probably solve my mapping problems, what are the other ways of getting that to happen without a direct add? I mean, the entries in there now got in there somehow, without someone manually adding them.

In any case, given these details, what does this tell you about my network and issues?

 

[lantis3]

Regarding your Plex server

Loading…

www.reddit.com

And as mentioned above, don't know why your router will matter. But since you have a FreeBSD server, why not not install Pi-Hole DNS (which comes with its own DHCP server) and disable all DHCP servers on all of your routers?

 

[_Cosmin_]

So you have something like this?

Everything should work even without internet connection in this case! Check mesh settings (i suspect there is your problem - try connect laptop to switch with wire to confirm server connection working correctly) and consider connecting switch to router with wire. Also i think is better to assign fixed ip via dhcp reservation on router. For faster samba connection in windows machine put server ip in host file.

 

[spacemanspiff2000]

Yes! Yes! I have something VERY MUCH like that graphic. Had I known how to do that graphic easily, and in a format this forum supports, I would have just posted that (vs. text). So, thanks for the graphic.

And thanks for all the assistance so far.

One slight change to the graphic -- though I think you just "shorted-handed" this detail on purpose b/c it probably doesn't matter -- there are actually 2 switches in separate locations ... the Server and PCs on Switch1, and the TV & Xbox on Switch2. But in both cases, the switches lead to a local mesh device, so they can get back to the router.
AND
There are 2 other Windows laptops, notable b/c they both work fine to the Server.

I tried putting my server's info in the local "hosts" file on the work laptop. I think that just helps resolve the IP address to a name. I still use the IP address when mapping anyway, so I'm not sure that helps. After a Just-In-Case-reboot, I still get the semaphore error when mapping, so that did not help by itself.

I also tried (again) wiring the laptop to the same switch as the server, making sure wifi was disabled on the laptop. No change to the semaphore issue.

I even tried that as a NET USE statement and got:
"System error 121 has occurred."
before the semaphore complaint. First time I've seen an error number, though I don't know that it helps here.

INTERESTING DEVELOPMENT:
If I haven't mentioned before, I do connect fine from the work laptop to the *nix server through PuTTY terminal (though with a delay at the start).

IN ADDITION: I had a need this week to move a file, I couldn't use my VNC to a working desktop at that moment, so I figured out how to "scp" the file from the laptop directly to FreeBSD without a go-between. And it worked!

What I think this tells me is that the connection between this laptop and server is fine, but the Samba-Windows connection is somehow the problem (though that doesn't explain the Plex issues, which could be separate).

Since there are multiple versions of Windows involved here, and one version of Samba, I'd be tempted to troubleshoot the Windows end. BUT, I cannot completely control this laptop, so now I'm thinking my business upgraded this laptop beyond that Samba's abilities (which was only exposed under network Configs A & B for some strange reason).

So I think my next step is to see if there's a Samba upgrade (most likely), invest the time in that, and see if that helps my main issue.

 

[gggplaya]

You can't bridge the T-Mobile router right?

I would probably switch to Starlink.

 

[_Cosmin_]

Smartdraw was used with network diagram template (i printscreen the result, save it to a image, post it on Postimages and reference it in forum post).
I use JellyFin instead of Plex (free and works perfectly for me - install server on nas and clients on pc/tv/phone, etc).
I was considering the network admin restriction on lap-top (since you have enterprise edition admin may block insecure guests via group policy or even regedit) but you said that with other provider worked so that is why i ask if you use static ip (in case firewall is set to block everything and something is changed on your new router). Did you try to disable temporary the firewall on that dell?

 

[spacemanspiff2000]

I have managed to resolve my issue. Thanks for everyone's assistance to that end.

Unfortunately, due to the many moving parts, I cannot pinpoint exactly what it was, but I can first relate the overview of what happened since my March 2nd post, where I had stated:

So I think my next step is to see if there's a Samba upgrade (most likely), invest the time in that, and see if that helps my main issue.

Where that quickly led to was discovering that Samba could not be upgraded as-is.

In fact, no apps/ports on the FreeBSD server could be upgraded because the NOS as a whole had fallen into an unsupported status over the time of my lengthy house-hunting/moving experience.

That led to my having to upgrade the version of FreeBSD. That first led to discovering there were security patches to the existing version, which I performed. However, I did not reboot the server and I did not test if that alone would have fixed this. I needed to upgrade the full version anyway.

That led to issues with the upgrade that are irrelevant here, except that it took me a while to finally successfully accomplish it.

Once the NOS was upgraded, the Samba server, Plex server, etc. was all upgraded along with it.

Once that dust settled, I could map drives to the Samba-based server from my work laptop! I also see no more issues with Plex, likely simply because the clients had been being upgraded well past the server version, which was unable to be upgraded once the OS went unsupported.

HOWEVER, simply "upgrading the NOS and its apps/ports" was not the entire solution here, just the final nail in it. (please see my next post for my overview)

 

[spacemanspiff2000]

With the nightmare finally over, looking back over the entirety, here's what I think happened... I'm going to focus on the in-house domain names...

In the past, I'd casually terminated my local machine names with a ".home" suffix. Meanwhile, the unchangeable work domain is "win.ad.ABC.COM" (obviously, substituting there).

And in the past, I'd found that sometimes I had to locally replace ".home" with simply ".win" to have some interconnectivity function between the work laptop and other Windows machines. That worked when I had a relevant situation, so I rolled with it. And I believe I had possibly set something in the Verizon router to have or use a ".win" suffix.

Never before this had it mattered that I had the FreeBSD server hostname set as "raid.home".

Fast-forward to setting up the new router, where I had used the ".home" suffix there, not even really thinking about it.

WHAT I THINK HAPPENED WHEN I WAS SWITCHING BACK AND FORTH IN THE OLD HOUSE:

Some combo of:
* the VZ router having ".win" and the new router having not-".win"
* the FreeBSD server apparently requiring a reboot to adjust to these topology switches, which I did not consider and was not doing
* time passing and many patches/upgrades to only the clients, perhaps such as SMBv1 no longer being supported (but some server functions only using SMB1)

Under those conditions, I can see how I could switch back and forth between the VZ router config and the new router config and have the former always work and the latter only ever partially work (failing on this work-laptop to server aspect).


Then, I moved. Obviously, the server was forced to reboot at that point. Since this all did not work upon coming back up in the new house, that reboot was not the fix.

Now relying on the new router, once I came to the point of experimenting with the ".win" name, I made sure I had it changed in the router. The router rebooted, but the server was not.

Then I changed the internal hostname of the server from ".home" to ".win" and I restarted the networking processes, but not the entire server. Plus, by now, the server software was considered "old."


THEREFORE, after the passage of time + changing the router to ".win" to match my work laptop's domain + changing the server to ".win" + regular laptop patches possibly enforcing the domain name more rigorously + upgrading the server OS & Samba and rebooting the server = the work laptop can now map to Samba from the server.