Jump to content

Recommended Posts

Posted

We have an odd issue here with a few Windows 7 machines. Hopefully someone can help.

 

We have a Buffalo drive on the network and have given it an ip address. On the drive are 3 shared folders - all standard stuff. Now some machines can see the drive via IP address but some cannot.

 

My machine - I enter the IP \\10.180.8.18\ and expect three directories to be listed (I am domain admin) - but my machine cannot even see the drive.

 

Any help appreciated. We thought it could be a GPO but then this would affect every machine.

 

Gareth

Posted
Can you ping the IP address?

 

Yip. Tried that. Pings fine. IN addition other machines are seeing the drive. We have a GPO that maps certain directories to certain drives. For example one GPO maps our Media drive to Z:\ for every member of staff and admin.

 

It's a weird issue. We thought maybe one of the other GPOs was cutting it off - but I cannot even browse to the drive through the Start Menu and \\

 

GJE

Posted
is sync enabled on the ones that cant see it as ive had issue with that before where even as admin i cant see shares that a pc has 1/2 heartedly cached clear cache or disable sync it then worked fine
Posted

Sync? Sorry - don't get you.

 

This was a freshly build 32 bit Windows7 Ent machine. Re-build two weeks ago. Weirdly enough when I was testing 64bit Windows on my machine it could seen the IP.

 

Tell me more about sync? Am I being a bit thick here?

 

Gareth

Posted
The problem is with the bufallo drives, not the stations. There's a known bug/feature with most of the linkstations/terastations that means some machines can only access via IP and some only via netbios name, rather randomly.
Posted
The problem is with the bufallo drives, not the stations. There's a known bug/feature with most of the linkstations/terastations that means some machines can only access via IP and some only via netbios name, rather randomly.

 

Interesting. I'll check to see if there is a firmware update.

 

I can browse to the Buffalo webserver/admin panel through my browser.

 

Gareth

Posted
I have exactly same issue with the Buffalo LinkStation. The strange thing is when I install Windows 7 using DVD, the machine pick up shares and no problems with the shares, but when I build a machine using MDT I face exactly same problem. I can ping, web browse and FTP but can't map the drive etc.
  • Thanks 1
Posted
I have exactly same issue with the Buffalo LinkStation. The strange thing is when I install Windows 7 using DVD, the machine pick up shares and no problems with the shares, but when I build a machine using MDT I face exactly same problem. I can ping, web browse and FTP but can't map the drive etc.

 

That is interesting. We too use an image from MDT which I build in July. Yet 64 bit DVD works fine. However - some machines get the drive without any issue.

 

Gareth

Posted
It is a very strange error that we are seeing occur here, some of the PCs when rebuild with MDT can see it no problem here, it appears to be fairly random in occurance for us and all machines on site bar a few broadcoms, have Intel Network Cards of a same standard.
  • Thanks 1
Posted
I am on 1.63 Firmware and the drive is joined to the domain.

 

We haven't joined it to the domain. Don't really need to from what I can tell.

 

1.64 nearly downloaded. I'll let you know how it goes.

 

Gareth

  • Thanks 1
Posted
Any update...

 

Morning,

 

I updated the firmware and noticed no change on my desktop admin machine. I had to go and teach for the rest of the day. I'll start again later today.

 

Cheers

 

Gareth

  • Thanks 1
Posted
It is a very strange problem we are seeing, I have referred it back to buffalo support, because I cannot see how its an issue with how we have the network, we use the same build, only have 3 types of PC on site, have everything turned off firewall wise internally on our network, all machines are using the same image, it just plainly works and maps fine for some staff and refuses to for others.
  • 3 weeks later...
Posted

Well guys we manage to resolve this problem by disabling the Security Signature in registry. It was enabled by default when deploying image through MDT. Here is the complete path to the registry key to set the value to 0.

HKEY_LOCAL_MACHINE>System>CurrentControlSet>Services>Lanmanserver>Parameters>enablesecuritysignature=0

 

...another mystery is now history.

  • Thanks 1
Posted

HI

 

Is the fxed ip address on the drive set correctly.

 

Are you using different subnets.

 

Is there a limited number of connects for your nas drive?

 

What happens if you do a \\ nasname\sharename?

 

Richard

Posted (edited)
I had the same problem with QNAP TS-410. I was not able to access with \\172.18.184.42. It is about username and password. I have created a user name similar to a domain username. It works now. Domain authentication does not work. From Windows XP machine it always works. Windows 7 is the problem. It is a known issue. If you logon to a domain machine with a username and password and create an identical username and password in QNAP then it will allow to map network drive. It is about authentication problem. It is more to do with Windows 7. Windows 2003 server also faces no problem. Windows 7 and Windows 2008 Server struggles to map network drive. QNAP says domain authentication works but it does not. So, my finding is, it is an authentication issue. Edited by sultan966
Posted

ours is now solved, there were four registry entries that we had to set with GPP now and the device is visible properly and maps without issue.

 

Subnets were always fine with us, the Linkstation was always visible even on machines it refused to map, it could be pinged fine, just point blank refused to map.

 

fixdrive.png

 

Those are the settings for those wondering that have solved it for us.

Posted (edited)
ours is now solved, there were four registry entries that we had to set with GPP now and the device is visible properly and maps without issue.

 

Subnets were always fine with us, the Linkstation was always visible even on machines it refused to map, it could be pinged fine, just point blank refused to map.

 

[ATTACH=CONFIG]17403[/ATTACH]

 

Those are the settings for those wondering that have solved it for us.

 

Aren't those settings to do with SMB Signing ( either version 1 or 2.0 ) ??

 

http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

 

http://blogs.technet.com/b/josebda/archive/2010/12/01/the-basics-of-smb-signing-covering-both-smb1-and-smb2.aspx

Edited by mac_shinobi

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...