Samsung Slate tablet won't open NAS shared folders
Hi i just purchased a Samsung XE700T1A-A03AU Slate PC, windows 7 pro.
Had it connected to it's dock and accessed network shares via the data cable connected to the dock. everything no problem. Connected it to the domain no problem.
Outlook/echange working all ok.
BUT
Then I disconnected the Slate PC from the dock and setup the wireless then tried the network share and it gave me an error "network not found" error 0x0800700xxx something like that.
My network share is on a QNAP TS-259 Pro+ however the internet works, shares on the IBM server are accesable and I can ping the NAS from the Slate PC ok. Outlook works ok
Other computers can access the QNAP ok even on the wireless.
beats me!
Had it connected to it's dock and accessed network shares via the data cable connected to the dock. everything no problem. Connected it to the domain no problem.
Outlook/echange working all ok.
BUT
Then I disconnected the Slate PC from the dock and setup the wireless then tried the network share and it gave me an error "network not found" error 0x0800700xxx something like that.
My network share is on a QNAP TS-259 Pro+ however the internet works, shares on the IBM server are accesable and I can ping the NAS from the Slate PC ok. Outlook works ok
Other computers can access the QNAP ok even on the wireless.
beats me!
In Samsung XE700T1A-A03AU Slate PC, open Local Security Policy with elevated administrator privilege. Under Local Policies, goto Security Options and look for "Network security: LAN Manager authentication level" and change the Security Setting to "Send LM & NTLM responses".
Description of this local policy is as follows:-
Network security: LAN Manager authentication level
This security setting determines which challenge/response authentication protocol is used for network logons. This choice affects the level of authentication protocol used by clients, the level of session security negotiated, and the level of authentication accepted by servers as follows:
Send LM & NTLM responses: Clients use LM and NTLM authentication and never use NTLMv2 session security; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send LM & NTLM - use NTLMv2 session security if negotiated: Clients use LM and NTLM authentication and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send NTLM response only: Clients use NTLM authentication only and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send NTLMv2 response only: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send NTLMv2 response only\refuse LM: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers refuse LM (accept only NTLM and NTLMv2 authentication).
Send NTLMv2 response only\refuse LM & NTLM: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers refuse LM and NTLM (accept only NTLMv2 authentication).
Important
This setting can affect the ability of computers running Windows 2000 Server, Windows 2000 Professional, Windows XP Professional, and the Windows Server 2003 family to communicate with computers running Windows NT 4.0 and earlier over the network. For example, at the time of this writing, computers running Windows NT 4.0 SP4 and earlier did not support NTLMv2. Computers running Windows 95 and Windows 98 did not support NTLM.
Default:
Windows 2000 and windows XP: send LM & NTLM responses
Windows Server 2003: Send NTLM response only
Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2: Send NTLMv2 response only
Description of this local policy is as follows:-
Network security: LAN Manager authentication level
This security setting determines which challenge/response authentication protocol is used for network logons. This choice affects the level of authentication protocol used by clients, the level of session security negotiated, and the level of authentication accepted by servers as follows:
Send LM & NTLM responses: Clients use LM and NTLM authentication and never use NTLMv2 session security; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send LM & NTLM - use NTLMv2 session security if negotiated: Clients use LM and NTLM authentication and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send NTLM response only: Clients use NTLM authentication only and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send NTLMv2 response only: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
Send NTLMv2 response only\refuse LM: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers refuse LM (accept only NTLM and NTLMv2 authentication).
Send NTLMv2 response only\refuse LM & NTLM: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers refuse LM and NTLM (accept only NTLMv2 authentication).
Important
This setting can affect the ability of computers running Windows 2000 Server, Windows 2000 Professional, Windows XP Professional, and the Windows Server 2003 family to communicate with computers running Windows NT 4.0 and earlier over the network. For example, at the time of this writing, computers running Windows NT 4.0 SP4 and earlier did not support NTLMv2. Computers running Windows 95 and Windows 98 did not support NTLM.
Default:
Windows 2000 and windows XP: send LM & NTLM responses
Windows Server 2003: Send NTLM response only
Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2: Send NTLMv2 response only
ASKER
Ok i will try this on Monday.
Just clearing up something... the tablets can access the shares on the SBS 2003 via the wireless ok.
It is only accessing the Qnap 269 pro (with the latest firmware upgrades) via the wireless (Netgear WNR2000-100AUS access point) is there a problem.
I thought there maybe a setting in the Qnap NAS or the wireless unit?
Just clearing up something... the tablets can access the shares on the SBS 2003 via the wireless ok.
It is only accessing the Qnap 269 pro (with the latest firmware upgrades) via the wireless (Netgear WNR2000-100AUS access point) is there a problem.
I thought there maybe a setting in the Qnap NAS or the wireless unit?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'd suggest a reboot. If failing, clear the wireless network from list of networks and reconnect creating a fresh profile again.
Ravi.