Buffalo Forums

   

Since installing Windows 7 64bit, I find that windows loses connection with the LS often.  Lets say I want to navigate to \media\software\cars\vag

 

When I click media, it loads quickly as normal, but as soon as I select software, it just sits there for a few minutes, sometimes it pops up saying the connection to the drive was lost.  It works 50% of the time or less.

 

Any ideas?

 

Jeff

How are you accessing it?

   

via it's ip address.

 

I map it like: //192.168.20.108\media

 

I should probably look into my firewall.  I havn't changed any settings, and it should either work or not, but I will see if there is anything odd going on with it.

Your mapping in wrong.  its \\ipaddress.  no host name and make sure that your using these>\\       not these>//

   Why no host name? I'm mapping it the same way I did when we used Vista 32 and it worked just fine. But I will certainly try removing the host name and see what happens. I appreciate the help Jeff

Not too sure why it happened but it has to be something with the Name Resolution possibly when mapping my host name.

   

Didn't work, I have to add \media or \share or \info or \backup or whatever otherwise I get the error seen in the screen shot.

 

So if I map it by typing \\192.168.20.108   if fails

If I type \\192.168.20.108\share  it works, but only 50% of the time it will connect.

 

A surprising observation is if I map it by it's name \\LS-XHL\Media it works, and it works well.  Will have to see if it stays that way.

 

screen shot

Try setting the LS on a static IP.

   

It is.  :(

 

Acutally all my devices have static ip addresses.  I just find it easier to deal with when I know which device is which.

 

So far with it mapped by it's name ie. \\ls-xhl\media it is working well, and faster than before, which is just strange, but I am please it is working well again.

 

I should be more specific, I have my router set to assign specific ip addresses to a specific device, but the LS was set to DHCP although the router always assigns it 192.168.20.108.  I changed it to static and will see if that makes a difference.  I still can't map to the root of the drive ie: \\192.168.20.108 but I can map like I used to with \\192.168.20.108\media

 

Will test for a few days and check back.

if you can access via \\IP\share then just \\IP should work just fine.  How are you trying to map?

   

See the screen shot above. 

 

I open windows explorer, select network, right mouse button click, select map network drive, then type in \\192.168.20.108  and that fails with the message you see in the screen shot.  If I type \\192.168.20.108\media or info or share, it works, but has not reliably since putting 7-64bit on.

 

 

I should add what I was trying to describe about using static address's in my router while using dhcp on the comptuers is known as DHCP Reservations if that matters at all.

"I should add what I was trying to describe about using static address's in my router while using dhcp on the comptuers is known as DHCP Reservations if that matters at all."

 

I know what you mean, I have the same thing set up at home.

 

"I open windows explorer, select network, right mouse button click, select map network drive, then type in \\192.168.20.108  and that fails with the message you see in the screen shot.  If I type \\192.168.20.108\media or info or share, it works, but has not reliably since putting 7-64bit on."

 

Try just going into your run command (windows key + R), and type in "\\IP".  This should pull up all of your share folders.  Just right click on any of them and go to map network drive.  See if this method is any different.

   

That does work.  Maybe I am confusing everyone.  On the root of my LS are 4 shares (folders)  Media, Share, Backup and Info. 

 

If I map the drive using \\192.168.20.108\media it works, but not reliably.

 

I was told by Josh maybe to map it by typing \\192.168.20.108 but that fails with the message in the screen shot.

 

If I type in the run command \\192.168.20.108 if opens a window displaying the 4 folders listed above, if I then map one of them, lets say media, the default map address is \\192.168.20.108\media, which will work, but not reliably.

 

 

Right, you say it disconnects/hangs at times?  That wouldn't make any sense if you did it the way that I stated unless it is changing IP addresses somehow (or you have an unstable wireless connection or something).  Is it still happening after mapping the way I asked?

   

The mapping suggestion you gave me is the way I have been mapping it since the beginning.

 

What happens when it fails is, lets say I want to navigate to /media/software/cars/audi/vag/3

 

z: = //192.168.20.108/media

 

So I start clicking, first on

 

z:

software

cars

 

but here is where the problem occurs, 50% or more of the time, it just sits there, after a minute or so, it either does nothing, or windows displays an error saying it could not connect to the drive.  But if I immediatly click on z: again or even software, it loads right up.

 

If I map the drives by using their names, the problem does not appear to happen.  But I have only been mapping it by name for a day or so.

I've just not heard of this before.  Give me a moment to see what I can find.

   

Hey, just wanted to update you.

 

Since changing the network settings in the LS to static, the issue has not returned.

 

Thanks for your time.

 

Jeff