I will describe this problem as follows:
SMB was working fine a couple days after set up but now when I go to transfer files it will transfer a couple files then completely stall out at zero bytes per second waiting for it to fully time out I get this error
I also get a network error when trying to use file explorer on ZimaOS
And I can reproduce the problem like this:
Grab a file you want to transfer to ZimaOS then try to transfer it over SMB or File explorer on the ZimaOS control panel
And I remember I did this to my machine before the problem showed up:
I don’t remember doing anything particular that could cause this besides using it normally
And I have tried these operations to fix it:
Powering off and powering back on both ZimaOS and Windows
Removing the USB HDD
[If you used CLI, then you did this by]
N/A
And here are the specs of my machine:
4 GB of ram
500 GB HDD boot drive
2 TB USB HDD
13th Generation Intel Core i3-13100
I’m so sorry it turns out I needed to turn off tailscale my network doesn’t support NAT hairpinning. I should have tried that first but it wasn’t causing an issue until now so I don’t know what changed with tailscale
PC > Tailscale > Direct connection using the public ip > Router > ZimaOS
Since my network doesn’t know how to handle nat hairpinning it was basically dropping but also sort of working? It was really weird. I don’t use the client since I already have a remote access network setup that doesn’t require port forwarding
I should clarify that the router is also running tailscale and is exposing my whole entire network subnet to my tailscale internal network. Which pretty much means any device connected to my account can access any device in my home network
You must master some advanced skills. And still, I suggest you try to shut down the tailscale and use Zima Client for some time, and give us your thoughts. Look forward to your feedback.
I tried the client like you said I should. It’s good and works fine but can’t be used with tailscale on the same PC. My home lab network relies too much on tailscale for it to be fully taken down especially for private internal communications between my home lab and some of my servers in a DC. changing tailscale from starting up automatically on windows boot seems to make sure it doesn’t break communications with Zima. When I’m outside of the network I can use tailscale in place of zima client to access my network shares and the control panel. If I didn’t have a need for a private network between my home lab and my other devices I would be able to exclusively use zima client. My opinion of the client is that it’s pretty good and the polished like ZimaOS is but it just doesn’t meet what my home lab requires
Glad to hear that you work with Tailscale well for your home needs. Would you tell us what happened specifically when you used both ts and Zima Client?
What I think was going on was there was routing clashing. Please correct me if I’m wrong but if Zima client does routing table updates for windows that would interfere with tailscale since that also does routing table updates. Tailscale uses the IP range 100.64.0.0/10
