file sharing in the 21st century
-
Also, what are people's must have NC apps?
-
@Donahue said in file sharing in the 21st century:
Also, what are people's must have NC apps?
I use Notes and Talk constantly.
-
Is there a way to point devices on the LAN to the LAN address instead of the external address?
-
@Donahue Internal DNS records are your friend
-
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
That's where overloading DNS comes in, or configuring the router to hairpin.
-
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
-
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
Sorry, I see this as a slightly different thing. I do have external access now, and I would like users who may be out of the office to prefer internal when available. This is probably not a big deal though, no need to get your panties in a bunch
-
well, I managed to lock my self out of NC, playing around with 2fa. I am unsure how to proceed, and may resort to just starting over.
-
@Donahue said in file sharing in the 21st century:
well, I managed to lock my self out of NC, playing around with 2fa. I am unsure how to proceed, and may resort to just starting over.
Already tried disabling 2fa plugin via CLI?
-
@black3dynamite said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
well, I managed to lock my self out of NC, playing around with 2fa. I am unsure how to proceed, and may resort to just starting over.
Already tried disabling 2fa plugin via CLI?
yes. Apparently I did a backup code, and I cannot disable that.
-
I can't generate a new one because the app to do that from CLI wont enable because of DB issues.
-
@Donahue said in file sharing in the 21st century:
I can't generate a new one because the app to do that from CLI wont enable because of DB issues.
You've got the worst of luck with Nextcloud. Since its not in production, I'll start all over with just the basic setup and then go from there.
-
JB has a post about redirecting or linking the home folders under user profiles to the NC folder . This would then sync to the NC server.
The hassle- you have to do it on the PC after the user logs in.
-
I think so. I think one of my biggest problems is that I can generally intuitively understand stuff and can glean a lot. This usually allows me to understand things really quickly, but there are times when I jump the gun and it bites me. This is one of those times.
-
@Donahue said in file sharing in the 21st century:
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
Sorry, I see this as a slightly different thing. I do have external access now, and I would like users who may be out of the office to prefer internal when available. This is probably not a big deal though, no need to get your panties in a bunch
The only way to get internal clients to use different DNS than public clients is to have an internal DNS Zone that is the same name as your external public DNS name. But doing it that way means you need to copy over all public DNS records to your internal DNS zone now except now you will point hosts names to internal IP addresses for those you want
-
ok, I blew it away and created it again. It only took like 20-30 minutes this time.
-
@Obsolesce said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
Sorry, I see this as a slightly different thing. I do have external access now, and I would like users who may be out of the office to prefer internal when available. This is probably not a big deal though, no need to get your panties in a bunch
The only way to get internal clients to use different DNS than public clients is to have an internal DNS Zone that is the same name as your external public DNS name. But doing it that way means you need to copy over all public DNS records to your internal DNS zone now except now you will point hosts names to internal IP addresses for those you want
yeah, if that is the case, I will keep it simple and just run external full time.
-
@Donahue said in file sharing in the 21st century:
@Obsolesce said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
Sorry, I see this as a slightly different thing. I do have external access now, and I would like users who may be out of the office to prefer internal when available. This is probably not a big deal though, no need to get your panties in a bunch
The only way to get internal clients to use different DNS than public clients is to have an internal DNS Zone that is the same name as your external public DNS name. But doing it that way means you need to copy over all public DNS records to your internal DNS zone now except now you will point hosts names to internal IP addresses for those you want
yeah, if that is the case, I will keep it simple and just run external full time.
That’s not how that works
-
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
@Obsolesce said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
Sorry, I see this as a slightly different thing. I do have external access now, and I would like users who may be out of the office to prefer internal when available. This is probably not a big deal though, no need to get your panties in a bunch
The only way to get internal clients to use different DNS than public clients is to have an internal DNS Zone that is the same name as your external public DNS name. But doing it that way means you need to copy over all public DNS records to your internal DNS zone now except now you will point hosts names to internal IP addresses for those you want
yeah, if that is the case, I will keep it simple and just run external full time.
That’s not how that works
I am not sure what you are saying. If I do nothing, then users are going to be looking at the external domain and can access it that way as the default. I dont have to point it to the internal name.
-
@Donahue said in file sharing in the 21st century:
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
@Obsolesce said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
@JaredBusch said in file sharing in the 21st century:
@Donahue said in file sharing in the 21st century:
Is there a way to point devices on the LAN to the LAN address instead of the external address?
FFS, we just had this conversation in your other thread.
You use an internal based DNS name. for clients that are only ever in the office.
This prevernt you from having to add your public domain to your internal DNS.
Sorry, I see this as a slightly different thing. I do have external access now, and I would like users who may be out of the office to prefer internal when available. This is probably not a big deal though, no need to get your panties in a bunch
The only way to get internal clients to use different DNS than public clients is to have an internal DNS Zone that is the same name as your external public DNS name. But doing it that way means you need to copy over all public DNS records to your internal DNS zone now except now you will point hosts names to internal IP addresses for those you want
yeah, if that is the case, I will keep it simple and just run external full time.
That’s not how that works
I am not sure what you are saying. If I do nothing, then users are going to be looking at the external domain and can access it that way as the default. I dont have to point it to the internal name.
