Network File Explorer

Hi,
I have created a file explorer like windows explorer.
I want to specify some machine on the network (by it name or IP address)& I want the file explorer to get the directory contents in that machine.
How can this be done?
Any pointers/links will be appreciated.
Thanks
Rudra

This may help:
http://jcifs.samba.org/
They have Java packages that allow for connecting to other computers, listing files and transferring files.

Similar Messages

Can't Access One of My Network Computers via Windows (File) Explorer

I've just installed a new router (Linksys EA3500 Dual Band) to replace my old (Linksys WRT100), but can't imagine how that could cause this trouble, except that prior to installing the new router, all worked properly. I have three Workgroup computers
on my network, one running Win 7 Ultimate 64bit (call it Tower-755, an older laptop upstairs running Win 7 Pro 32bit (call it MommaDell), and a super laptop running Win 7 Pro 64bit (Call it M6600). On Tower-755 I have a mirrored Raid1 drive - call
it Z: - that I share over the net (i.e. Everyone = Read/Write).
Since installing the new router, when I open File Explorer on M6600 or MommaDell, I can see - in the search pane (under Network) - all three computers, and when I click on MommaDell, its shared folder is accessible, but when I click on Tower-755
I get an error saying, "Windows cannot access
\\Tower-755, yet I can ping it successfully from a command prompt.
However, when I open File Explorer on Tower-755, although I can see all three computers in the search pane (under Network), I can't access any of the three (including Tower-755 itself); I get the same error message, although I CAN ping them from a command
prompt.
Also, and I'm not sure if this related, in the search pane under HomeGroup on all three computers, I can only see MommaDell.
I've checked and double checked all my router settings, including the IP Address range (192.168.1.2 - 51). I also have a Domain Controller server with two joined workstations on the net, so I have a static IP in order to be able to access the server
and/or workstations remotely when we travel.
That's my story and I'm stuck with it, but I'd sure be grateful for any help with this mess.
Capt. Dinosaur

Hi Capt,
In order to help you analyze your issue, we need confirm some situations.
1. Did these 3 computers all join the same HomeGroup or Workgroup?
Yes
2. Domain Controller server with two joined workstations you mentioned, did it mean two of these 3 computer joined the domain environment?
No. Those are separate computers in their own domain, just using the same network.
3. Did you ping via IP address or computer name?
Both, but this morning something is different.
a. MommaDell and M6600 can ping each other both by IP and Name, but can't ping Tower-755 either way.
b. Tower CAN ping both MommaDell and M6600 both ways.
According to your description,
Tower cannot ping MommaDell and M6600.
No, Tower CAN ping both MommaDell AND M6600 both by ip and name.
MommaDell can ping Tower.
M6600 can ping Tower.
Both of the above was true yesterday, but not this morning.
Please check if MommaDell and M6600 could ping each other.
Yes they can
And make sure all of them turn on the network discovery and turn off the firewall temporarily for test:
Network Discovery is ON in all three machines, and Windows firewall is always off because I have ZoneAlarm on all three machines.
Enable or disable network discovery
Which?
http://windows.microsoft.com/en-in/windows/enable-disable-network-discovery#1TC=windows-7
If it doesn't resolve, please post every computer's ipconfig /all output here for analysis.
it's 7:30 and I have to be out until 2:30. I'll do the posting then, and thanks for the help.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Capt. Dinosaur

Offline Files - Where is the "Work Online" Button in File Explorer (when connected to company network)?

I have windows 8.1 Pro. I connected a network drive and was able to set up some of the contents as available offline. When I connect to the VPN, however, and go into file explorer - for that drive, it indicates the state as "Offline (background
sync)" and will not allow me to make other folders/files under the mapped drive as available offline or to open any of these. How can I change this state so I am working online? (Also, sync is not running). Thank you for your help.

Hello Liz Braden,
Do you mean that when you use VPN and can’t sync offline folder?
If yes, please take a look at the following thread similar to this issue.
https://social.technet.microsoft.com/Forums/windows/en-US/21042eeb-434b-4864-afbc-22948d4d02e1/offline-file-sync-over-a-vpn?forum=w7itpronetworking
Try to disable the "Configure slow-link mode" for Offline Files:
Computer Configuration\Administrative Templates\Network\Offline Files\Configure slow-link mode
Best regards,
Fangzhou CHEN
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Bridge(CS3) conflict with Windows file explorer

Bridge will crash on me at least twice a day. I use Bridge and Windows file explorer simultaneously copying and moving files across a network. When Bridge quits I sometimes lose my network connection and have a lot of trouble re-connecting.
I have done the usual delete preference, trash cache etc., nothing seems to be working.

Not sure what is going on there, but have a suggestion. You are increasing your odds of Bridge crashing, and trashing the cache, if you move too fast. When in Bridge wait for the spinning arrow in lower left corner to stop (it is building the thumbs) before changing folders.
Don't see any correlation between network connection and Bridge crashing. Perhaps if you have a slow computer you are overloading it with tasks and it can not keep up. Minimize programs running at same time.
Also, run task manager and see what the processor is doing. If CPU useage goes up markedly that will confirm the problem.

Error: "We're having a problem opening this location on file explorer. Add this website to your trusted sites list and try again"

Hello,
When i try to open document library from SharePoint Production portal then it throws the specified error. However, when i open document library from SharePoint Development portal then it opens it in file explorer quite easily.
Production portal is on https whereas development portal is on http. Also, UAG has been configured on production portal.
Any idea where it's getting stuck up? Surely, this is not a browser issue on Windows 7 as it's opening the development portal's document library on the same machine.
I've also done following things:
- Configured Desktop Experience on production environment
- Installed the hotfix for Windows 7
Regards,
Sohaib
Sohaib Khan

Hello Sohaib.
Here is the list of causes defined here.Hope it helps you
The cause and the resolution methods are the following:
Cause: There is a missing Root site collection...
Resolution: Check and ensure, that the “Managed Paths” are not changed in the web Application’s page, there is a (root) explicit for
this web application and there is a working Root site collection.
If for any reason this is not the case in your environment, you may try the following:
- Apply (if not already) the following Hotfix to one of those clients:
Error when you open a SharePoint Document Library in Windows Explorer or map a network drive to the library after you install Internet Explorer 10 in Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/2846960
Then, try to delete the cache of the IE browser before reproducing the issue. Check the result..
- Try to temporarily disable the Antivirus and test again.
- Check if you have installed the Desktop Experience feature on the SPS13 server.
- Check if you face this behavior with all users, Or only with some specific ones, Or with all different client OSes..
Otherwise you will need to collect the logs to further analyze...
http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/sps13-quot-open-with-explorer-quot-random-error-quot-we-re-having-a-problem-opening-this-location-in-file-explorer-add-this-web-site-to-your-trusted-sites-list-and-try-again-quot.aspx
Please remember to click 'Mark as Answer' on the answer if it helps you

File Explorer uses Bing to search. - Not live search

Windows is creating searches for words typed into the file explorer path box.
I accidentally typed two words into the windows file explorer address bar instead of a network address. Windows then opened a new tab in my browser and searched for those words with Bing.
Typing "Pictures" without quotes takes me to the users Pictures folder. Typing "Pic tures" does a Bing search for those two words.
Is there any option to change or remove this?
I have turned off Bing Smart Search "Get search suggestions and web results from Bing"

Hi,
How’s everything going?
If you could update us at your convenience that would be wonderful.
Yolanda Zhu
TechNet Community Support

LabVIEW built-in file I/O VIs have poor performance on network file I/O operation?

Hi,
I use LabVIEW built-in VIs to save a big 2-D array data into a ascii file (with the "write character to file" vi). When I write it on the local hard drive, it takes about 5 seconds to complete the task. But when I write the file on the network, it takes more than 5 minutes. A typical output file is 5MB big.
If I write the file on the hard drive, and use the built-in File MOVE vi, it takes about 30 seconds to complete the MOVE operation. But if I use Windows File Explorer to move the same file, it takes less than 1 second.
Both the PC and server are connected on a full-duplex 100BaseT network. I tried different file I/O operations (including MOVE, create new file and LIST)
with LabVIEW VIs and compared the speed with windows file explorer. It turned out LabVIEW VIs performance is always A LOT slower than Windows File Explorer. I tried the same test on many different PCs, with windows 98, NT, 2000, and the results are the same.
Is there anyway to improve the file IO performance or is there any other workaround on this issue, such as calling Windows File Explorer to perform the same task via ActiveX maybe?
Your imputs will be very much appreciated. Thanks!
Dan

Hi,
Do the ASCII files have a .txt extention? I've noticed the same behaviour
once, with .txt files. Renaming them (to e.g. .txq) fixed the problem.
I'm clueless why this happend. If you extentions are not .txt, I don't have
a clue...
What if you copy the file, and then delete the original?
Regards,
Wiebe.
"dikrn" wrote in message
news:506500000008000000EA7C0000-1042324653000@exchange.ni.com...
> Hi,
>
> I use LabVIEW built-in VIs to save a big 2-D array data into a ascii
> file (with the "write character to file" vi). When I write it on the
> local hard drive, it takes about 5 seconds to complete the task. But
> when I write the file on the network, it takes more than 5 minutes. A
> typical output file is 5MB big.
>
> If I write the file
on the hard drive, and use the built-in File MOVE
> vi, it takes about 30 seconds to complete the MOVE operation. But if I
> use Windows File Explorer to move the same file, it takes less than 1
> second.
>
> Both the PC and server are connected on a full-duplex 100BaseT
> network. I tried different file I/O operations (including MOVE,
> create new file and LIST) with LabVIEW VIs and compared the speed with
> windows file explorer. It turned out LabVIEW VIs performance is
> always A LOT slower than Windows File Explorer. I tried the same test
> on many different PCs, with windows 98, NT, 2000, and the results are
> the same.
>
> Is there anyway to improve the file IO performance or is there any
> other workaround on this issue, such as calling Windows File Explorer
> to perform the same task via ActiveX maybe?
>
> Your imputs will be very much appreciated. Thanks!
>
> Dan

Network file sharing in Lion

I have some folders shared in Mac OS that was easily available to my other computers in network and guest OSs installed on virtual machine on Mac OS host but since I've upgraded to Lion sharing stoped to work "normally". I still can see my mac machine in network group but it no longer allow to connect as a "Guest", so I can only explore my shared folders having entered my Mac OS user login and password but doing that I get an access not only to shared folders but to the entire mac drive and all subfolders... How can I fix that and is it possible to use network file sharing in Lion as it was in SL and previously?

Hi Prashanth,
There are multiple ways to move content from fileShares to SharePoint.
Step 1: Create the SharePoint Information Architecture - create a site collection preferably chose a document center template, create document libraries and folders as per the network folder structure in your organization.
Step 2: Map your File Share as Network drive in your client machine, and same way map your SharePoint website document library as network drive too. Drag and drop files.
Note there are 2 issues for this approach,
1) your document metadata will be lost, the last modified by will change to the account with which you have logged into SharePoint while copying, and the last modified time will be changed.
2) Its a tedious manual approach if you have lots of files.
Now for retaining the metadata you will need to depend upon a 3rd party tools ( or this codeplex solution: http://f2sp.codeplex.com/ (I havent verified that this works with Sp 2013 or not).
Using 3rd party tools has the advantage of retaining metadata and any issues with file naming conventions will also be taken care of most of the prominent tools which otherwise needs to be taken care by administrator manually. - Note SharePoint has file
naming conventions - https://support2.microsoft.com/kb/905231?wa=wsignin1.0.
Also In order to reduce the effort in second step you can also create content organizer rules and map your drop off library as the drag and drop location.
finally do read this awesome blog post by Sean Earp and Andre Kieft before starting of with the project. http://blogs.technet.com/b/ptsblog/archive/2013/11/04/migrating-file-shares-to-sharepoint-online.aspx
Hope that helps.

Can't access NAS through Windows 8.1 file explorer anymore

This used to word perfectly, but since I reinstalled my Windows 8.1 setup I can't access my NAS through Windows Explorer anymore.
The weird thing is: I can still access it by logging in into the admin console via "http://ix4-300d/manage/manage.html" in IE.
From here I can access and edit my shares, download stuff, etc.
But for some reason my PC can't find my NAS anymore using file explorer -> Network -> \\ix4-300d\.
This sucks, cause now I can't copy anything to the NAS anymore (which used to work perfectly).
I guess it must be some network setting in Windows, but I can't find it.
Anyone knows what could be the problem?
Both the PC and the NAS are in workgroup "WORKGROUP" btw.
Thanks!! http://i.imgur.com/TMJtjzS.jpg

Hello ExReey,
First thing to do is make sure that you have the correct IP address (you can find this on the ix4 display) and try the procedure using the IP address instead of the device name>
I would also try manually mapping the Shares:
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=windows%208%20map%20network%20drive
Also, I cant open any Imgur links here, is that an error you are trying to show me?

How to hide items on Windows 8 File Explorer Ribbon

Scenario
This article describes how to hide items on the file explorer ribbon in Windows 8 and Windows 8.1.
Method
We can implement it via customizing the permission of the related registry keys.
Note: Before you make changes to a registry key or subkey, we recommend that you export, or make a backup copy, of the key or subkey.
Before you make changes to a registry key or subkey, we recommend that you
export, or make a backup copy, of the key or subkey.
Step 1:
Open
Registry Editor and locate to following registry key under which you can find the corresponding keys of the items on the File Explorer Ribbon.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\CommandStore\shell\
In the following figure, it shows the Add a network location item on the file explorer ribbon, and the corresponding
registry key in Registry Editor.
Step 2:
Take ownership of the registry key
Note: You can take ownership
of a registry key if you are logged on as an administrator or if you have been specifically assigned the permission to take ownership of the registry key by the current owner.
Right-click on the registry key which you want to take ownership of,
and then select
Permissions... option.
Click on
Advanced button to grant special permissions in the key.
At the top to the right of the current
Owner, click on the Change link.
Enter
Administrator in the Enter the object name to select
box, and then click on Check Names.
Click on
OK twice to apply.
Step 3:
Change the permission of the registry key.
On
Permissions for the key name display dialog, click
Administrators in the Group or user names window, and then select the
Allow check box for
Full Control
option.
Click
Users in the Group or user names window, and then select the
Deny
check box for
Full Control
option.
Step 4:
Click on
Apply and OK to save the changes and the following figure shows the modified permissions and owner.
Step 5:
When you open File Explorer, the item you would like to hide disappears. For your information, the following is an example:
Item: Add a network location
Corresponding Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\CommandStore\shell\Windows.AddNetworkLocation
For advanced users
You can also deploy script with Set-Acl which is a PowerShell command to take ownership and change permissions
of the keys. For your information, please refer to the following articles to learn more about this command:
Set-Aclhttp://technet.microsoft.com/en-us/library/hh849810.aspx
SET-ACL on registry key
http://blogs.technet.com/b/brad_rutkowski/archive/2008/09/29/set-acl-on-registry-key.aspx
Apply to
Windows 8
Windows 8.1
Welcome to your feedbacks.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

The reason they gave was it is possible for the file to stay open when done with the file. (not properly closing) As the driver would be accessing the file to retrieve the thumbnail.
The thing is a driver is nothing more than a program it self. Therefore it is capable of opening and closing a file and placing the thumbnail into the database for that folder. It then would be capable to verify if the thumbnail exists in that database. Since the driver only has to run when explorer is open in that folder's view, it really is not running that often.
The catch I can see it when both Illustrator and explorer are running at the same time. Which one should close the file? The solution would be a small app that verifies that both programs are running and has control of clean up when both have closed. The driver and Illustrator could also in theory check and see if the other is running, if it is do nothing if not then close the file.
So it really boils down to having the driver and Illustrator talking to each other.

[Forum FAQ] Troubleshooting Network File Copy Slowness

1. Introduction
The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common
Internet File System (CIFS) Protocol is a dialect of SMB. Both SMB and CIFS are also available on VMS, several versions of Unix, and other operating systems.
Microsoft SMB Protocol and CIFS Protocol Overview
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365233(v=vs.85).aspx
Server Message Block overview
http://technet.microsoft.com/en-us/library/hh831795.aspx
1.1
SMB Versions and Negotiated Versions
- Thanks for the
Jose Barreto's Blog
There are several different versions of SMB used by Windows operating systems:
CIFS – The ancient version of SMB that was part of Microsoft Windows NT 4.0 in 1996. SMB1 supersedes this version.
SMB 1.0 (or SMB1) – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2
SMB 2.0 (technically SMB2 version 2.002) – The version used in Windows Vista (SP1 or later) and Windows Server 2008 (or any SP)
SMB 2.1 ((technically SMB2 version 2.1) – The version used in Windows 7 (or any SP) and Windows Server 2008 R2 (or any SP)
SMB 3.0 (or SMB3) – The version used in Windows 8 and Windows Server 2012
SMB 3.02 (or SMB3) – The version used in Windows 8.1 and Windows Server 2012 R2
Windows NT is no longer supported, so CIFS is definitely out. Windows Server 2003 R2 with a current service pack is under Extended Support, so SMB1 is still around for a little while. SMB 2.x in Windows Server 2008 and Windows Server 2008
R2 are under Mainstream Support until 2015. You can find the most current information on the
support lifecycle page for Windows Server. The information is subject to the
Microsoft Policy Disclaimer and Change Notice. You can use the support pages to also find support policy information for Windows
XP, Windows Vista, Windows 7 and Windows 8.
In Windows 8.1 and Windows Server 2012 R2, we introduced the option to completely disable CIFS/SMB1 support, including the actual removal of the related binaries. While this is not the default configuration, we recommend disabling this older
version of the protocol in scenarios where it’s not useful, like Hyper-V over SMB. You can find details about this new option in item 7 of this blog post:
What’s new in SMB PowerShell in Windows Server 2012 R2.
Negotiated Versions
Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server:
OS
Windows 8.1 WS 2012 R2
Windows 8 WS 2012
Windows 7 WS 2008 R2
Windows Vista WS 2008
Previous versions
Windows 8.1 WS 2012 R2
SMB 3.02
SMB 3.0
SMB 2.1
SMB 2.0
SMB 1.0
Windows 8 WS 2012
SMB 3.0
SMB 3.0
SMB 2.1
SMB 2.0
SMB 1.0
Windows 7 WS 2008 R2
SMB 2.1
SMB 2.1
SMB 2.1
SMB 2.0
SMB 1.0
Windows Vista WS 2008
SMB 2.0
SMB 2.0
SMB 2.0
SMB 2.0
SMB 1.0
Previous versions
SMB 1.0
SMB 1.0
SMB 1.0
SMB 1.0
SMB 1.0
* WS = Windows Server
1.2 Check, Enable and Disable SMB Versions in Windows operating systems
In Windows 8 or Windows Server 2012 and later, there is a new PowerShell cmdlet that can easily tell you what version of SMB the client has negotiated with the File Server. You simply access a remote file server (or create a new mapping to it) and use Get-SmbConnection.
To enable and disable SMBv1, SMBv2, and SMBv3 in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012, please follow the steps in the article below.
Warning: We do not recommend that you disable SMBv2 or SMBv3. Disable SMBv2 or SMBv3 only as a temporary troubleshooting measure. Do not leave SMBv2 or SMBv3 disabled.
http://support.microsoft.com/kb/2696547
1.3 Features and Capabilities
- Thanks for the
Jose Barreto's Blog
Here’s a very short summary of what changed with each version of SMB:
From SMB 1.0 to SMB 2.0 - The first major redesign of SMB
Increased file sharing scalability
Improved performance
Request compounding
Asynchronous operations
Larger reads/writes
More secure and robust
Small command set
Signing now uses HMAC SHA-256 instead of MD5
SMB2 durability
From SMB 2.0 to SMB 2.1
File leasing improvements
Large MTU support
BranchCache
From SMB 2.1 to SMB 3.0
Availability
SMB Transparent Failover
SMB Witness
SMB Multichannel
Performance
SMB Scale-Out
SMB Direct (SMB 3.0 over RDMA)
SMB Multichannel
Directory Leasing
BranchCache V2
Backup
VSS for Remote File Shares
Security
SMB Encryption using AES-CCM (Optional)
Signing now uses AES-CMAC
Management
SMB PowerShell
Improved Performance Counters
Improved Eventing
From SMB 3.0 to SMB 3.02
Automatic rebalancing of Scale-Out File Server clients
Improved performance of SMB Direct (SMB over RDMA)
Support for multiple SMB instances on a Scale-Out File Server
You can get additional details on the SMB 2.0 improvements listed above at
http://blogs.technet.com/b/josebda/archive/2008/12/09/smb2-a-complete-redesign-of-the-main-remote-file-protocol-for-windows.aspx
You can get additional details on the SMB 3.0 improvements listed above at
http://blogs.technet.com/b/josebda/archive/2012/05/03/updated-links-on-windows-server-2012-file-server-and-smb-3-0.aspx
You can get additional details on the SMB 3.02 improvements in Windows Server 2012 R2 at
http://technet.microsoft.com/en-us/library/hh831474.aspx
1.4 Related Registry Keys
HKLM\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters\
DeferredOpensEnabled – Indicates whether the Redirector can defer opens for certain cases where the file does not really need to be opened, such as for certain delete requests and adjusting file attributes.
This defaults to true and is stored in the Redirector variable MRxSmbDeferredOpensEnabled.
OplocksDisabled – Whether the Redirector should not request oplocks, this defaults to false (the Redirector will request oplocks) and is stored in the variable MrxSmbOplocksDisabled.
CscEnabled – Whether Client Side Caching is enabled. This value defaults to true and stored in MRxSmbIsCscEnabled. It is used to determine whether to execute CSC operations when called. If CSC is enabled,
several other parameters controlling CSC behavior are checked, such as CscEnabledDCON, CscEnableTransitionByDefault, and CscEnableAutoDial. CSC will be discussed in depth in its own module, so will be only mentioned in this module when it is necessary to understanding
the operation of the Redirector.
DisableShadowLoopback – Whether to disable the behavior of the Redirector getting a handle to loopback opens (opens on the same machine) so that it can shortcut the network path to the resource and
just access local files locally. Shadow opens are enabled by default, and this registry value can be used to turn them off. It is stored in the global Redirector variable RxSmbDisableShadowLoopback.
IgnoreBindingOrder – Controls whether the Redirector should use the binding order specified in the registry and controlled by the Network Connections UI, or ignore this order when choosing a transport
provider to provide a connection to the server. By default the Redirector will ignore the binding order and can use any transport. The results of this setting are stored in the variable MRxSmbObeyBindingOrder.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Security Signature settings – The RequireSecuritySignature setting is stored in MRxSmbSecuritySignaturesRequired, EnableSecuritySignature in MRxSmbSecuritySignaturesEnabled, RequireExtendedSignature
in MRxSmbExtendedSignaturesRequired, and EnableExtendedSignature in MRxSmbExtendedSignaturesEnabled. Note that the Extended Security Signatures assume the regular security signatures are enabled, so those settings are adjusted if necessary based on the extended
settings. If extended signatures are required, regular signatures have to be required.
EnablePlainTextPassword – Support for using plain text passwords can be turned on using this key. They are disabled by default.
OffLineFileTimeoutIntervalInSeconds – Used to set the expiration time for timing out an Exchange (discussed later) when the exchange is accessing an offline file. This value defaults to 1000 seconds,
but can be changed in the registry and is stored in the global Redirector variable OffLineFileTimeoutInterval
SessTimeout – This is the amount of time the client waits for the server to respond to an outstanding request. The default value is 60 seconds (Windows Vista). When the client does not receive the
response to a request before the Request Expiration Timer expires, it will reset the connection because the operation is considered blocked. In Windows 8, the request expiration timer for the SMB 2 Negotiate is set to a smaller value, typically under 20 seconds,
so that if a node of a continuously available (CA) cluster server is not responding, the SMB 3.0 client can expedite failover to the other node.
ExtendedSessTimeout – Stored in the ExtendedSessTimeoutInterval variable, this value is used to extend the timeout on exchanges for servers that require an extended session timeout as listed in the
ServersWithExtendedSessTimeout key. These are third party servers that handle SMB sessions with different processes and vary dramatically on the time required to process SMB requests. The default value is 1000 seconds. If the client is running at least Windows
7 and ExtendedSessTimeout is not configured (By Default), the timeout is extended to four times the value of SessTimeout (4 * SessTimeout).
MaxNumOfExchangesForPipelineReadWrite – This value is used to determine the maximum number of write exchanges that can be pipelined to a server. The default is 8 and the value is stored in the variable
MaxNumOfExchangesForPipelineReadWrite.
Win9xSessionRestriction – This value defaults to false, but is used to impose a restriction on Windows 9x clients that they can only have one active non-NULL session with the server at a time. Also,
existing session based connections (VNETROOTS) are scavenged immediately, without a timeout to allow them to be reused.
EnableCachingOnWriteOnlyOpens – This value can cause the Redirector to attempt to open a file that is being opened for write only access in a manner that will enable the Redirector to cache the file
data. If the open fails, the request will revert back to the original requested access. The value of this parameter defaults to false and is stored in the MRxSmbEnableCachingOnWriteOnlyOpens variable.
DisableByteRangeLockingOnReadOnlyFiles – This parameter defaults to false, but if set to true will cause level II oplocks to automatically be upgraded to batch oplocks on read-only files opened for
read only access. It is stored in the variable DisableByteRangeLockingOnReadOnlyFiles.
EnableDownLevelLogOff – False by default, this value controls whether a Logoff SMB will be sent to down-level servers when a session is being closed. If this is false, and the server has not negotiated
to the NT SMB dialect or does not support NT Status codes, the logoff will not be sent because we aren’t sure that server will understand the request. The value is stored in MrxSmbEnableDownLevelLogOff.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\
ResilientTimeout – This timer is started when the transport connection associated with a resilient handle is lost. It controls the amount of time the server keeps a resilient handle active after the
transport connection to the client is lost. The default value is 300 seconds (Windows 7, Server 2008 R2, 8, Server 2012).
DurableHandleV2TimeoutInSecond – This timer is started when the transport connection associated with a durable handle is lost. It controls the amount of time the server keeps a durable handle active
after the transport connection to the client is lost. The default value is 60 seconds (Windows 8, Windows Server 2012). The maximum value is 300 seconds.
HKLM\SYSTEM\CurrentControlSet\Services\SMBWitness\Parameters\
KeepAliveInterval – This functionality was introduced for SMB 3.0 in Windows 8 and Windows Server 2012. The witness protocol is used to explicitly notify a client of resource changes that have occurred
on a highly available cluster server. This enables faster recovery from unplanned failures, so that the client does not need to wait for TCP timeouts. The default value is 20 minutes (Windows 8, Windows Server 2012).
HKLM\System\CurrentControlSet\Services\SmbDirect\Parameters\
ConnectTimeoutInMs – Establish a connection and complete negotiation. ConnectTimeoutInMs is the deadline for the remote peer to accept the connection request and complete SMB Direct negotiation. Default
is 120 seconds (Windows 8).
AcceptTimeoutInMs – Accept negotiation: The SMB Direct Negotiate request should be received before AcceptTimeoutInMs expires. The servers starts this timer as soon as it accepted the connection. Default
is 5 seconds (Windows 8).
IdleConnectionTimeoutInMs – This timer is per-connection. It is the amount of time the connection can be idle without receiving a message from the remote peer. Before the local peer terminates the
connection, it sends a keep alive request to the remote peer and applies a keep alive timer. Default is Default: 120 seconds (Windows 8).
KeepaliveResponseTimeoutInMs – This attribute is per-connection. It defines the timeout to wait for the peer response for a keep-alive message on an idle RDMA connection. Default is 5 seconds (Windows
8).
CreditGrantTimeoutInMs – This timer is per-connection. It regulates the amount of time that the local peer waits for the remote peer to grant Send credits before disconnecting the connection.
This timer is started when the local peer runs out of Send credits. Default is 5 seconds (Windows 8).
References:
[MS-SMB]: Server Message Block (SMB) Protocol
http://msdn.microsoft.com/en-us/library/cc246231.aspx
[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3
http://msdn.microsoft.com/en-us/library/cc246482.aspx
SMB 2.x and SMB 3.0 Timeouts in Windows
http://blogs.msdn.com/b/openspecification/archive/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows.aspx

3. How to Troubleshoot
3.1 Troubleshooting Decision Tree
1
Is the slowness occurring in browsing a network shared folder or copying a file, or both?
Browsing, go to 1.1.
Copying, go to 1.2.
Both, go to 1.3.
1.1
Is the target a DFS path or not?
Yes, go to 1.1.1.
No, go to 1.1.2.
1.1.1
Is the client visiting the nearest DFS root server and file server?
Yes, go to 1.1.1.1.
No, go to 1.1.1.2.
1.1.1.1
Browse the corresponding (Non-DFS) UNC path directly. Do you still experience the slowness?
Yes, go to 1.1.1.1.1.
No,
go to 1.1.1.1.2.
1.1.1.1.1
Issue is the particular file server responds to the share folder enumeration requests slowly. Most probably it’s
unrelated to DFS. Follow 1.1.2.
1.1.1.1.2
Issue is that client experiences delay when browsing the DFS path, but no delay is visiting the target file server
directly. Capture Network Monitor trace from the client and study if the DFS path is cracked down.
1.1.1.2
Use dfsutil.exe to clear local domain and referral cache. Then visit the DFS path again and capture Network Monitor
trace from the client to study why the client goes to a wrong file server or DFS root server.
1.1.2
Not a DFS issue. Issue is the particular file server responds to the share folder enumeration requests slowly. “Dir”
the same share folder from Command Prompt. Is it slow?
Yes, go to 1.1.2.1
No, go to 1.1.2.2
1.1.2.1
Check the number of subfolders and files in that share folder. Is the number large?
Yes, go to 1.1.2.1.1
No, go to 1.1.2.1.2
1.1.2.1.1
Try to “dir” a different share folder on the same file server, but with less items. Is it still slow or not?
Yes, go to 1.1.2.1.1.1
No, go to 1.1.2.1.1.2
1.1.2.1.1.1
Probably to be performance issue of the file server. Capture Network Monitor trace from both sides, plus Performance
Monitor on the file server.
1.1.2.1.1.2
Probably to be performance issue of the file server, particularly, of the disk. Capture Network Monitor trace from
both sides, plus Performance Monitor on the file server.
1.1.2.1.2
Same as 1.1.2.1.1.1. Probably to be performance issue of the file server. Capture Network Monitor trace from both
sides, plus Performance Monitor on the file server.
1.1.2.2
Explorer.exe browses the share folder slowly while “dir” does fast. The issue should lie in the particular SMB traffic
incurred by explorer.exe. It's a Shell issue.
1.2
Is the target a DFS path or not?
Yes, go to 1.2.1
No, go to 1.2.2
1.2.1
Is the client downloading/uploading against the nearest file server?
Yes, go to 1.2.1.1
No, go to 1.2.1.2
1.2.1.1
Try to download/upload against that file server using the Non-DFS share path. Still slow?
Yes, go to 1.2.1.1.1
No, go to 1.2.1.1.2
1.2.1.1.1
Not a DFS issue. Capture Network Monitor trace from both sides to identify the pattern of the slowness.
1.2.1.1.2
This is unlikely to occur because the conclusion is contradictory to itself. Start from the beginning to double
check.
1.2.1.2
Same situation as 1.1.1.2. Use dfsutil.exe to clear local domain and referral cache. Then visit the DFS path again
and capture Network Monitor trace from the client to study why the client goes to a wrong file server or DFS root server.
1.2.2
Same as 1.2.1.1.1. It's not a DFS issue. Capture Network Monitor trace from both sides to identify the pattern of
the slowness.
1.3
Follow 1.1 and then 1.2.
3.2 Troubleshooting Tools
Network Monitor or Message Analyzer
Download
http://www.microsoft.com/en-us/download/details.aspx?id=40308
Blog
http://blogs.technet.com/b/messageanalyzer/
Microsoft Message Analyzer Operating Guide
http://technet.microsoft.com/en-us/library/jj649776.aspx
Performance Monitor
http://technet.microsoft.com/en-us/library/cc749249.aspx
DiskMon
http://technet.microsoft.com/en-us/sysinternals/bb896646.aspx
Process Monitor
http://technet.microsoft.com/en-us/sysinternals/bb896645

Drive C showing in File Explorer under This PC and as a root namespace

For me Drive C, which I have named C - W10EVM, shows twice in File Explorer's navigation column. I only have the one volume on this VM (C:). I start the window with the command (in a desktop shortcut):
C:\Windows\explorer.exe /expand,C:\
This is what I see:
Anyone know what can be done to hide one or the other of them?
I guess, assuming other drives will show up as root namespaces, that I'd probably prefer to hide This PC. Ideally then I'd only have drive letters and Network in the Navigation pane.
Thanks.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Thanks for trying to help, Tony, but no, things are simple and basic on this system... Nothing special with regard to cloning/mirroring.
Are you saying that if you open File Explorer you do not see duplication of drive C:? Please show a screen grab of your Navigation pane, as I have done.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Offline Files (Background) Sync makes File Explorer and other programs responding slow

Hi TechNet,
I have a problem with Offline Files and
especially with VPN users.
For VPN users, the slow-link
policy is activated with a background
sync interval of one hour. But, when Offline Files is syncing, their File Explorer is hanging (not responding) by creating new files/folders, deleting files/folder, or rename files/folders. This happens only in their (redirected)UserData
folder or with other DFS shares which are cached locally. In other programs (Outlook or Office 2010) when they save data in the UserData folder exactly the same things happens (not responding).
This problem occurs in both the
internal network and via VPN, so bandwidth is
not the problem. When the sync is finished, everything is working fine again.
I've tested:
- Offline mode with scheduled background sync: problem occurs
- Online mode with manual sync: problem occurs
- Rebuild offline cache database: no effect
- Tested with fresh Windows 8(.1) installations and user profiles: problem occurs
- Monitoring SMB traffic with WireShark: no result
- Montoring Windows 8(.1) clients with procmon: no result
- Tested with full DFS paths: problem occurs
- Disable IPv6: problem occurs
- Disable Windows Search: problem occurs
- Browsing in the Offline Files folder (Sync Center -> Manage Offline Files -> View Offline Files) is very slow (with +- 200 files). This occurs also when Offline Files is not syncing.
Does anyone have an idea how I can solve this problem?
Thanks,
Bas
(Sorry for my bad English)

Hello,
May I know if there is any update there?
Please let me know if I can help you more, thanks.
BR,
Steven Song
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hello Steven,
First, sorry for the late response, I have tested a few things for you:
Offline mode with background sync over a VPN connection: During scheduled sync File Explorer hangs. When bypass the cache by using a UNC path (State: Online) there is also a delay, but this is caused by bandwidth.
Online Mode with Manual Sync over a LAN connection: During sync File Explorer hangs in (redirected)UserData Folders (They are always available offline, maybe this is a problem?). With UNC paths, there is no delay…
The first folder/file is created slowly, but the second is fast.
It's like csc
still
must initialize
the cache…or something…
I m I made some
print screens, but I can not upload them because my account is not verified.......
trT Thanks,
Bas

Remove address bar from file explorer (using regsitry)

This used to be possible in 2008, but I haven't been able to figure out how it's done in 2012 R2. The old method was to add a key under IE, and it would also remove the address bar from windows explorer - but this method
no longer works. So is anybody aware of what key needs to be changed or modified in order to make this happen. Further, ideally this change would happen in HKCU.
Thanks

Hi,
>>That would seem to remove run from start menu, not the address bar from file explorer.
Yes, this setting will disable Run.exe. However, this setting will also prevent users from accessing local or network resources by typing the accessing paths in the address bar of File Explorer.
I am not completely sure why you want to remove the address bar in File Explorer. However, if our target is to restrict users from accessing network resources by UNC path, in my opinion, enabling this setting a better way to go.
In addition, regarding this topic, the following thread can also be referred to for more information.
Hide Windows Explorer Address Bar
http://social.technet.microsoft.com/Forums/en-US/987305c6-bd48-4107-bcf5-84d4fff4097d/hide-windows-explorer-address-bar?forum=winserverGP
Best regards,
Frank Shen

IE 11 Will not allow ftp to open in File Explorer

I have 'just 1' machine so far with this problem so i am fairly certain it is a setting or registry entry but can not for the life of me figure this one out.
Windows 7 Pro 64 bit - IE 11 - all current updates.
When i open Windows Explorer (file explorer) and I enter an FTP site address, IE 11 opens and takes me to the address.
This would be all fine and dandy except for uploads yeah?
I used to be able to, in IE, go VIEW -> OPEN WITH FILE EXPLORER but now when I do that there is 0 response from the computer.
I have checked the boxes for Allow FTP view outside of IE and I have checked the box for Use Passive Mode.
Oh, Behavior is the same whether the fire wall is active or not.
What am i missing.
Thanks,
James
dogdaynoon

I just don't know exactly what I am looking for.
If you only have one trace it helps to have a hypothesis to test. Otherwise if you have two which are essentially the same except for one significant difference, as I mentioned you should be able to filter coarsely, spot a divergence and then investigate
the cause of it. In a general scenario I imagine you would only have Process & Thread as a coarse filter, e.g. see the dispatching of tasks and threads and the loading of their modules. However, for your case, it may be sufficient to compare
Network events, spot a divergence in that sequence and then dive in to see what more differences there were which caused it.
Good luck
Robert Aldwinckle

Network File Explorer

Similar Messages

Maybe you are looking for