Unable to map network drive

Hello, my first time here, and I'm looking for help.

I'm running Vista Ultimate, 32bit, with a home network and internet. Recently I bought, and installed, the "Argosy Mobile Video HDD Pro," model #HV359T (it's essentially an external 1.5TB drive housed in a small case that lets you store and play media -- movies, music, pictures, etc. Nifty thing.) I set it up and it works just fine, and downloaded some movies on my home TV system via USB. BUT, I just can't map it to a drive on Vista on my home network. The error I get is simple: "Windows cannot access 192.168.1.103" (The IP addr of the box). I can ping it, the supplied utilities can see it, but Vista just can't when I try to map it. I have no further diagnostic info, just that Windows can't access it; not too helpful. I suspect it's a security issue, but that's just a wild guess.

Anyone have such an experience or thoughts? Or more hopefully, a fix for the problem?

Thanks,

Dean

Do you get a similar error if you simply browse to \\192.168.1.103 ?

Does the box have a shared folder to map to? You can't map a drive to just 192.168.1.103, you need a folder that's shared so in essence you would map to "\\192.168.1.103\share"

Do you need to supply any credentials to access the box?

If the above is all correct then it could be a security issue as you suspect, although I'd be surprised since the product states compatibility with Vista. Anyway try:
Start > Run > secpol.msc
Drill down to Local Policies\Security Options
In the right hand pane scroll down to Network Security: LAN Manager Authentication Level
Double click this item
From the new window that opens click the drop down box and change the setting from "Send NTLMv2 response only" to "Send LM & NTLM - use NTLMv2 session security if negotiated"
Click OK and close secpol.msc

To ensure the setting has taken effect open a cmd prompt and run "gpupdate /force"

Now try and map the drive again.

I had to do this to access my NAS but that was out before Vista hit the scene so as I say I'd be surprised if this is still an issue on more modern devices.

Thank you "DC" (those are my real initials, BTW). I can map the drive using Windows explorer (\\192.168.1.103) and it works just fine. I didn't think about adding the shared directory, so let me give that a shot and I'll let you know. Good advice from you, thanks.

I didn't answer all of your questions (cooking dinner, got distracted). If I browse to the IP addr of the box it opens up just fine. The box doesn't need authorization (as far as I can tell, while it's great HW, the utilities and docs are... minimal). I was an engineer for 30 yrs, build my own computers, etc., and I was pretty good. But I'm good enough to know I stink at networking. What just is "Send NTLMv2 response only" to "Send LM & NTLM - use NTLMv2 session security if negotiated"?

You don't need to worry about the NTLM bit since you can successfully browse the box by UNC path (\\192.168.1.103), you'd only need to change it if you were prompted for a username and password and said details not being accepted.

For clarification NTLM is an authentication mechanism, by setting it to "Send LM & NTLM - use NTLMv2 session security if negotiated" you're effectively setting it to the same level Windows XP used.

I think all you need to do is create a folder on the box and then share it, now not knowing how you manage the box I don't know how you do this but I'll take a wild guess that it's done via a web interface (browse to http://192.168.1.103)

DC, "you da man!" I only had to add "public" to the map (\\192.168.1.103\public") and it mapped perfectly. Thank you so much... "you da man..."

Glad to hear that worked, feel free to add rep by clicking my scales :P

Done (I guess, I'm a "newbie," remember?) I think I boosted your status a bit, and you deserve it pal.