Link Station NAS on Server 2012 Foundation Domain

We moved Link Station LS-QL NAS  (device name: LS-QL56C ) to a new domain. The device can be seen in Windows Explorer and pinged by FQDN but can only be browsed with ip.

Example:
\\192.168.1.2 in Windows Explorer works
\\LS-QL56C doesn't work

Pinging ls-ql56c [192.168.1.2] with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Updated NAS with new domain & switched DNS to use Domain Controller. Restarted NAS & client PC.

Authentication Setup

Delegate Authority to External SMB Server - Is this correct for Windows Server?
Use Windows Domain Controller as Authentication Server
Automatic User Registration
LVL 30
Randy DownsOWNERAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Randy DownsOWNERAuthor Commented:
Found out that NAS was not listed in Active Directory computers. Should I list it manually?

Connecting client PC via ip works fine. So we have some DNS issues. One known issue is that DNS/DHCP is still turned on for the ISP router but client seems to have the correct DNS, gateway when I do ipconfig /all
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Did you try to use the FQDN with \\ ?
0
Randy DownsOWNERAuthor Commented:
Yes that's in my example mapping "\\LS-QL56C doesn't work"
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Nope, \\FQDN is \\LS-QL56C.domain.com
0
Randy DownsOWNERAuthor Commented:
It's not registered in Active Directory under computers so adding domain is probably not going to help.
0
Randy DownsOWNERAuthor Commented:
Windows cannot Access \\ls-ql56c.domain.local
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
So when saying "pinged by FQDN" in your question body you meant "by hostname", which is LS-QL56C? I now see the ping response is telling the same.

I assume a FQDN does not get resolved either (as with ping, for example).
Are you running a WINS server? If not, the issue is located at the NAS - it does not respond to its host name. If WINS is used, make sure the NAS has an entry (probably static, made by you).
0
Randy DownsOWNERAuthor Commented:
yes, I can ping by host name but I can't open a share with host name. I suppose the host is not trusted by the domain even though I can see security set to full for Everyone.

I also have a backup job in task manager that runs on the host and appears to finish in about an hour without any errors. Trouble is that there is no file dates changed on the backup so we assume it's not working. It's not a Windows backup but rather ASB3
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Which kind of failure do you get for \\LS-QL56C ? An authentication error, or destination not found, ...? Does it last long before you get the error?
It cannot be an authentication issue, as you can connect by IP - the credentials are checked against the domain the same as when using a host name.

The effect you describe is strange, so the best way to get a hint is probably to perform a network capture for the SMB traffic for both success and failure, so you can compare.
0
Randy DownsOWNERAuthor Commented:
It takes a while to time out & tells me I may not have permission. My thinking is that DNS is not resolving but then it does ping the host name correctly.

I'm not sure what I would look for in a network monitor.
0
Randy DownsOWNERAuthor Commented:
It may not have any relevance but the gateway router has DNS/DHCP enabled but both the NAS & the client PC seem to have the correct information (i.e., using DC for DNS). Likewise the automated backup is run from the DC which references itself for DNS.
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
In NetMon, you would restrict traffic to from/to LS-QL56C. Shouldn't be much anyway, but if necessary, ports 445, 135-139 UDP and TCP can be restricted to.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Randy DownsOWNERAuthor Commented:
Customer is OK with using ip so we won't troubleshoot it further. I appreciate your input & will try NetMon if he changes his mind.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.