LinkStation Live (L-CH500L) - Can't connect from Windows Server 2003

[nuberfin]

   

I have 2 versions of XP and 1 version of VISTA on my network that are able to successfully connect to the NAS.  However, the 2 Windows Server 2003 servers on my network are unable to attached and browse the NAS.

 

From the command line on the 2003 server(s), I can ping and see the NAS on the network.  I can also reach the web admin just fine. 

 

When I try to map to the drive from one of the 2003 servers ( start>Run> \\BUFFALO\Share ) I get an error saying windows can't find the location.

 

Using NASNavigator, it shows up and reflects all of the information specific to it, but when I try to map a drive via NASNavigat I get the error "Failed Mapping. Remote Default Share is missing."  If I right-click on the NAS in NASNavigator and click "Browse Shares", it seems as though it's trying to do something but never does.

 

All computers run through the same router, which rules out a routing issue.  The 2003 servers have their Windows Firewall turned completely off.  I tried setting up the local security policy settings  on the 2003 servers the same as the policies are set up on the XP boxes.

 

So 8 hours later, I'm giving up and asking for someone to help. 

 

Anyone?

[Jason]

   It sounds like your share is no longer there. Try accessing the web interface of the linkstation and checking under the shared folder tab and see if the share share is still there.

[spwilliams13]

   I have had exactly the same issue. My laptop is running Vista and can access shares fine, my PS3 can access via the media servier. My desktop however can only access via the web. I recieve the same error message"Could not open shared folder, confirm drive status". I have updated the flash and the version of Nas navigator. The share is still there for the laptop but not for the pc!

[nuberfin]

   

Share is still there and I'm able to access it from the other PC's (non-Windows Server 2003 operating systems).  So it appears to be something specific to this particular operating system.  I suspect it has something to do with security policy, although I've gone through about every policy and made sure they matched the policies on the XP and Vista boxes.

 

So I'm hoping for someone to come along with the magic bullet.

[Jason]

   Try using it's IP instead of hostname in your unc path.

[yaziats]

   

I'm still having the same problem.  Using IP in the unc didn't help.  Keeps complaining:

 

"\\Ls-wtgl09b is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

 

An unexpected network error occurred."

 

 

... but I'm admin, and non-admin users in the AD can map and fully-use the NAS.  Can't map the NAS directly to the SBS2003.  Please help!

 

 

Yazi

[Dustrega]

If it's showing the \\[Hostname_of_NAS] as part of the error then the IP address is not being used.

[Pillerking]

   

open regedit, go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

 

change:

restrictanonymous to 0

restart server.

 

(if this alone doesnt do the trick, change the NoLmHash from 0 to 1 or vice versa

and/or change the LMcompatibilityLevel to 3)

 

info:

http://technet.microsoft.com/en-us/library/cc783167%28WS.10%29.aspx

http://technet.microsoft.com/en-us/library/cc960646.aspx

http://technet.microsoft.com/en-us/library/cc736342%28WS.10%29.aspx

 

hope i could help !

 

 

 

 

Message Edited by Pillerking on 09-07-2009 08:04 AM

[JoshC]

      

Does your domain controller requireDigitally Signed SMB Packets? On Windows 2003 Server these policiesare enabled by default.  They need to be set to 'Disable', not'Enable', or 'Not Defined'.  If not I would initialize the unitand set it back up.  Make sure the settings are correct:

 

I think is might be your problem!  Look above.

 

 

Configuring the Buffalo Nas forActive Directory:

• A computer account with the name   of the Buffalo NAS needs to be created on the domain. It needs to be   configured so that a pre-2000 machine can use this account.    

• In "IP Address Properties"   under "Network", the DNS server address needs to be set to   the Domain Controller's address.    

• The clock on the Buffalo needs   to be set to the same timezone as the Domain Controller and the   times need to be with in 5 minutes of each other.    

• The "Workgroup/Domain"   page under "Network" needs to be set to the following   settings - If ever a field is too short to enter the full   information (particularly the Domain Name and the Domain Controller   fields) they need to be filled in as much as possible:    

Workgroup and Domain Properties:

• Network Type: "Active Directory"    

     

• Active Directory Domain Name (NetBIOS Name): NETBIOS Legacy   Domain name, ex. "DOMAIN"    

     

• Active Directory Domain Name (DNS/Realm Name): Full Domain   name, ex. "domain.com"    

     

• Active Directory Domain controller Name: Domain Controller   name, ex. "server"    

     

• AD Administrator Name & AD Administrator Password: The   user name and password of an account with administration privileges   so the Buffalo can properly be added to the network. This   information will not be stored.    

     

• WINS Server IP Address: IP   address of the WINS server (if not using WINS, enter domain   controller's IP address)