[SOLVED] Can't mount Hetzner Storage Box CIFS

[Ramalama]

i have one more idea.

what happens if you telnet to the smb port to the storagebox?
telnet u3XXXXX.your-storagebox.de 445

does it tells you then, that you can escape with ctrl+] or does it times out?

 

[murda]

i have one more idea.

what happens if you telnet to the smb port to the storagebox?
telnet u3XXXXX.your-storagebox.de 445

does it tells you then, that you can escape with ctrl+] or does it times out?

I let it run for 1m30s and nothing happens.

It works on another machine though, but I must note that this other machine is on another network than Proxmox.

I'll see if I can get ahold of someone at home to try it on their own device, to single out if it's a network issue outside of Proxmox.

telnet u******.your-storagebox.de 445
Trying 78.46.14.173...
^C

 

[Ramalama]

I let it run for 1m30s and nothing happens.

It works on another machine though, but I must note that this other machine is on another network than Proxmox.

I'll see if I can get ahold of someone at home to try it on their own device, to single out if it's a network issue outside of Proxmox.

telnet u******.your-storagebox.de 445
Trying 78.46.14.173...
^C

Thats the issue, here it works, no matter if i try from home or from a hetzner server directly.

Your outgoing port 445 is blocked somewhere, i think probably your home modem or something that has a firewall?
But that mystery is solved, you have just to find out what blocks your port.

Cheers

 

[murda]

Thats the issue, here it works, no matter if i try from home or from a hetzner server directly.

Your outgoing port 445 is blocked somewhere, i think probably your home modem or something that has a firewall?
But that mystery is solved, you have just to find out what blocks your port.

Cheers

I just tried it on my dad's pc and it indeed can't connect either.

I then Googled "<my isp> blocks", and low and behold before I could finish my query the top result was "<my isp> blocks port 445"!

Thankfully we're changing ISP's soon!!

 

[emunt6]

Hi!

You can use "sshfs" mount, just enable SSH access in your storagebox.

 

[murda]

Hi!

You can use "sshfs" mount, just enable SSH access in your storagebox.

Thanks I will try this

 

[G0ldmember]

I would also recommend not to use cifs/smb over the internet but rely on SSH instead. You can SSH-mount the storage as well (sshfs).

 

[murda]

I would also recommend not to use cifs/smb over the internet but rely on SSH instead. You can SSH-mount the storage as well (sshfs).

I wanted to use the `seal` mount option to encrypt the traffic, but I will use sshfs instead now

 

[mainjj67]

Hi Murda,
do you use a Fritzbox? I had the same problem. But this and that solved it for me.

 

[G0ldmember]

@mainjj67 there is a good reason why the Fritz!Box is blocking that by default
I wouldn't use SMB over internet. It's not only insecure (even if there is the "seal" option), it's also slow and not reliable for non-local networks IMHO.

 

[murda]

@mainjj67 there is a good reason why the Fritz!Box is blocking that by default
I wouldn't use SMB over internet. It's not only insecure (even if there is the "seal" option), it's also slow and not reliable for non-local networks IMHO.

Why is the `seal` option insecure as well?

 

[G0ldmember]

Why is the `seal` option insecure as well?

Well this is just a workaround/addon in my opinion to make a insecure protocol more secure. Still SMB wasn't designed to exchange data over the internet, there are better ways to do that. From my experience, even SMB over VPN doesn't really work very smoothly so I don't use it. But that's just my 2 cents, everyone can do this as needed of course.

 

[pvps1]

I just tried it on my dad's pc and it indeed can't connect either.

I then Googled "<my isp> blocks", and low and behold before I could finish my query the top result was "<my isp> blocks port 445"!

Thankfully we're changing ISP's soon!!

it is a good default to block cifs for home users.
cifs is not meant to be a "remote" protocol

 

[UdoB]

it is a good default to block cifs for home users.
cifs is not meant to be a "remote" protocol

Agreed!

Which is just funny because (from https://cifs.com/):
"
What is CIFS?
The Common Internet File System (CIFS) is ...
"

If you need to use a remote CIFS resource build a tunnel (e.g. WireGuard) first and make sure that CIFS goes through that connection...

 

[Disciplus]

i have the same problem. i think starlink or heztner block the port 445 from starlink.