I access a NAS that is administered by someone else. Recently, due to QLockcer, the admin changed the HTTP port from 8080 to another port number (14xxx)
As a result, I can't seem to get Win 10, even with SMB enabled, to directly find the NAS. QFinder SEES it, but won't let me even SEE any of the shares.
Any ideas? (BTW, this is a TS-569 Pro running 4.3.4.1652.
Mapping a drive to a NAS when the HTTP port is changed
-
- Starting out
- Posts: 10
- Joined: Wed May 27, 2015 6:22 pm
- dolbyman
- Guru
- Posts: 35272
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: Mapping a drive to a NAS when the HTTP port is changed
First off all, foget changing the ports, DO NOT EXPOSE YOUR NAS TO WAN .... changing ports will do nothing to prevent fingerprinting via portscans and services that sell info like that (e.g. shodan)
Secure administration from WAN is to be done via VPN access, nothing else.
Then, changing the external http port via port forwarding should have absolutely no influence on local ports and even less so on SMB file protocol.
So please elaborate exactly what was done here.
Secure administration from WAN is to be done via VPN access, nothing else.
Then, changing the external http port via port forwarding should have absolutely no influence on local ports and even less so on SMB file protocol.
So please elaborate exactly what was done here.
-
- Starting out
- Posts: 10
- Joined: Wed May 27, 2015 6:22 pm
Re: Mapping a drive to a NAS when the HTTP port is changed
Yeah, that's part of the problem. I don't administer this unit, and only have limited access to it, so the schmuck who DOES administer it doesn't exactly keep me fully informed of what he's doing. I didn't think Windows used HTTP or HTTPS even for mapping, but thought I'd check. These QNAP boxes are a real unto their own. I'll have to check with the admin.