NAS Share issue: NFS or SMB
-
@gjacobse said in NAS Share issue: NFS or SMB:
@scottalanmiller said in NAS Share issue: NFS or SMB:
You say NFS or SMB. Which are you using from Windows?
I have both running on the NAS.
Yes, but that doesn't assist in troubleshooting. Which are you using in the case that you are troubleshooting?
Also, both on one share tends to cause issues, they don't share characteristics so interact with each other poorly.
-
ARe you mapping more than 1 map drive, or do you have annother network shared folder, cause Windows is limited to only 1 credentail for mapping, other than that you need to make script to map to close and clear credentails then map and even close explorer.exe
-
Wasn't able to look at the shares earlier than now.. most are only SMB:
but that hasn't mattered.
-
Both PCs are the same OSver of Win10
-
Found this article from MS regarding SMB1 and SMB2
https://support.microsoft.com/en-nz/help/4034314/smbv1-is-not-installed-by-default-in-windows
Thus far,.. I'm connecting again. but via
\ipaddress\
which is fine with me.
-
what is servicing DNS for you?
If you ping the DNS name, does it resolve? -
@Dashrender said in NAS Share issue: NFS or SMB:
what is servicing DNS for you?
If you ping the DNS name, does it resolve?ERL router - DNS 1 is the router, DNS2 is 8.8.8.8
didn't help either.
-
@gjacobse said in NAS Share issue: NFS or SMB:
@Dashrender said in NAS Share issue: NFS or SMB:
what is servicing DNS for you?
If you ping the DNS name, does it resolve?ERL router - DNS 1 is the router, DNS2 is 8.8.8.8
didn't help either.
So no DNS for internal. The answer, in that case, would be "nothing". That's for external lookups, only.
-
@scottalanmiller said in NAS Share issue: NFS or SMB:
@gjacobse said in NAS Share issue: NFS or SMB:
@Dashrender said in NAS Share issue: NFS or SMB:
what is servicing DNS for you?
If you ping the DNS name, does it resolve?ERL router - DNS 1 is the router, DNS2 is 8.8.8.8
didn't help either.
So no DNS for internal. The answer, in that case, would be "nothing". That's for external lookups, only.
I think the ER-L can have local DNS entries, but not sure it can be a DDNS server like Windows or Linux distros.
-
You need to run a local DNS service for internal names resolution. Either Windows Server DNS or BIND would do the trick. Synology has a DNS (BIND-based) server app if you've got one of their NASes.
-
Here is an option for using the ERL as a DNS server
https://www.reddit.com/r/Ubiquiti/comments/5fqjea/my_experience_with_unbound_dns_on_erl/ -
you can set static entries in EdgeOS.
- Always set DHCP to give out the ERL for DNS.
set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 dns-server 10.254.103.1- Always set the ERL to look at itself for a DNS (127.0.0.1
set system name-server 127.0.0.1- Make sure that DNS is listening on your LAN ports.
set service dns forwarding listen-on eth1 set service dns forwarding listen-on eth1.2- Set DNS forward lookup to whatever.
set service dns forwarding name-server 10.254.103.4 # my Pi-Hole set service dns forwarding name-server 1.1.1.1- If oyu are on a domain, tell EdgeOS to forward those to the DC.
set service dns forwarding options server=/ad.domain.com/10.254.0.21 set service dns forwarding options server=/domain.local/10.254.0.21 set service dns forwarding options server=/domain/10.254.0.21- Set up your static DNS entries.
set system static-host-mapping host-name nas inet 10.254.103.7
