Link to network file

Alright, i am gonna be as brief and clear as i can be with this one:
We have a file on a windoze server (the file is accessible and shared through windoze) that i need all of us to get to and modify. This has been done on the windoze pc's now i want to do this on the mac. What i would like to do is place a link to the shared file on the desktop. How do i do this on the mac?

V.K. wrote:
connect to the windows machine from the mac via file sharing (if the windows machine has sharing on it should show up in the sidebar of any finder window) and make an alias to the file in question on your desktop. just commandoptiondrag the file from the share top the desktop.
I connected to the windoze server using go->connect to server and then browse to the file. Then i commandoptiondrag and it is copied to my desktop. Get info shows it being on my desktop. So i am not sure about "making an alias". Exactly how do you do that?

Similar Messages

  • Trouble With Links to Network Files Within Online PDF

    I posted this at the end of someone else's thread who had a similar problem but it may have gotten lost in the shuffle. Either that or no one has an answer. Here goes...
    I create a Word document that contains links to network files (tested and working) and convert the document to a PDF. The links still function in the PDF when I test them. However, when someone opens the document from our intranet, the file:/// is replaced with some form of a relative link, either to a users C: drive or to an http:// directory. If I then go into the PDF and change the link action from Open File to Open Web Link and provide the full file:/// path, everything works as intended. This really wouldnt be a big deal if I was the one maintaining the document or if it were an occasional thing. The problem is that updating or adding a link to the document means correcting the existing links all over again. This is very cumbersome for the user who maintains the document.
    I'm using Acrobat 8 Professional. Any ideas?

    I'm having a similiar issue with cross platform (Vista to Mac OS X 10.5) file linking. We currently store indesign files on a folder in a shared drive (the mac unix path to the drive is /Volumes/SharedDrive and the vista path is Z:\) and link assets in the document to another folder stored on the shared drive. Note that all linked assets are not stored in the same location on the shared drive, for instance a linked image could be deep in the folder structure (/Volumes/SharedDrive/Marketing/Images/Fall09/example.jpg).
    The Vista computer references files differently than the mac on the shared drive, it seems to mount the network drive directly on the root level rather than in the /Volumes folder. I've tried to symlink the graphics folder (the one containing all the linked assets) to the root level of the hard drive (ln -s /Volumes/SharedDrive/Graphics /Graphics) but when we tried relinking the assets InDesign figured out it was a symlink and resolved the path to the absolute path. Is there some sort of configuration option in mac to mount this windows drive (it is on SBS Windows 2003) in a way that won't cause linking conflicts between mac and pc? Any thoughts are much appreciated!
    Thank you for all your help!

  • Link to network document - cannot find file

    I have a report which needs to provide links to pdf files on a protected network resource.  Meaning that the user of the Crystal Report does not have native access to the network resource, not even read access.  Is there any way to configure the link to use something akin to a "run as admin" auth attribute, so that the general report user has access to the files via the Crystal report but not via other means?

    > the driver does not support XP  I'm not so sure about that, HP has a driver posted for XP.  What the rep may have meant to say is that they do not support the WinXP OS anymore.  If it works, great, if not then they wont get thier hands dirty.  The WinXP driver for this model was last updated in Aug 2014.  They must have supported WinXP up until then but no longer. If HP wont help you with the suggested full software solution then you may have to get by with an alternative print and scan driver.  For example try downloading a Universal Print Driver from http://support.hp.com.  You can pick any of the 3 options that are available (postscript, pcl5 and pcl6).  I suggest starting with PostScript. That leaves you with finding a compatible scan driver and scanning application for WinXP.  Hopefully the scanner object was successfully installed on your Device Manager.  If so then you can use any TWAIN scanning application to continue your scanning such as MS Word, Paint or Adobe products.  If the scanner did not install then you might be out of luck.  WinXP can sometimes find scanner drivers via updates but MS stopped supporting WinXP in April 2014.  Its unlikely you will find another compatible scan driver if you dont already have one.  The scanner driver files should still be in teh Full Software Solution under one of the folders even if the installer is having trouble finding them. The only downside is that free scan software usually cannot scan directly to PDF, you will have to resort to .Tiff instead.    

  • Allowing user to create link to a network file

    Is there a way to allow the user of a form to enter the path to a local network file (such as a Word document), so that when others click it, it will take them to the file?
    In a thread in another forum, someone posted the following method of create a button containing the following code that converts text entered into a text field into a hyperlink:
    if (xfa.host.name != "XFAPresentationAgent")
        var oURI = xfa.resolveNode("form1.page1.header.TextField2").rawValue;
        var oLink = "<body xmlns=\"http://www.w3.org/1999/xhtml\" xmlns:xfa=\"http://www.xfa.org/schema/xfa-data/1.0/\"><p style=\"letter-spacing:0in\"><a href=\"" + oURI+ "\" style=\"margin-top:0pt;margin-bottom:0pt;text-valign:bottom;font-fami ly:'Myriad Pro';font-size:8pt\">" + oURI + "</a></p></body>";
        xfa.resolveNode("form1.page1.header.TextField2").value.exData.loadXML (oLink, false, true);
    This works great for internet URLs; however, when you enter a local or network path (for example "Y:\Network\File.doc"), you get the following error message in your default browser:
    Firefox doesn't know how to open this address, because the protocol (y) isn't associated with any program.
    How would you alter this code so that it links to a local or network file, and doesn't try to open it in a web browser? Or, if this isn't possible, is there any other way to allow the user to create a clickable link to a file?
    Thanks,
    Jo

    I've never tried it and there may be alternative ways of doing it, but I would think the only way you can provide formatting tools - without recreating each tool - is to use an Applet.
    What you're trying to do is create a document object on the server, have the user select an command on the client side (such as underlining text), have the client pass the command back to the server, and echo the results of that operation, right?
    It would be incredibly awkward and impractical to do that through a conventional stateless HTTP medium such as JSPs, PHP or JavaScript. It may have been done before, I'm just not aware of any attempts to do so.
    Are you willing to consider alternative third-party solutions, open source or not? Or is this something that you explicitly have to code?

  • Web-Disk on OSX 10.9 Give me this error: "Finder got an error: Network file permission error."

    Previously I was using OSX 10.8 and Web Disk was working great.
    Since I upgraded to OSX 10.9 Web Disk Dont Attach to my compputer and give me this ERROR:
    FInder got an error: Network file permission error.
    When I got this ERROR first time I searched GOOGLE and found this link: http://cammodude.blogspot.no/
    And I did:
    To force all connections to be SMB1:
    Open A terminal window
    paste in the following line followed by the return key(should be all on one line): 
    echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf
    What the command does:
    Creates a file called nsmb.conf  in your  home directory at the path ~/Library/Preferences/nsmb.conf.
    Adds directives to force SMB connections to use the SMB1 protocol.  This is slower but stable.
    Then I could use Web Disk on OSX 10.9 after executing this command in Terminal.
    But now I restarted my Macbook and now Im NOT able to connect to Web Disk and get the same ERROR.
    FInder got an error: Network file permission error
    After trying 100 times it attaches 1 time but then show this ERROR:
    Can't get <<class cdis>> "my.server.com/2078" of application "Finder".
    If this happen then I can see the files in Finder and see the Contents and Size of files but if I open a PHP file in BBEdit then it shows BLANK.. But actually it is NOT blank.
    Now Im stuck How can I solve this? All help is highly appericated..
    Thank you so much...

    Hi,
    Make sure to chmod the app, something like this :
    chmod -Rf 777  secure_site_WebDisk.app
    (in my case the CPanel provided the app for my OSx version.)

  • Emailing a link to a file on an SMB server

    How do you create a link to a file on an SMB server, to send to other people (e.g. in email)?
    In a large corporation with mixed Mac/Windows network we use Samba to allow Mac OS X 10.6 to access the file servers.
    This works fine for basic operations such as browsing the servers, or copying files, etc. However, it isn't clear how to create a link to a file on a server, such that it can be emailed to people.
    Creating a link to a folder works ok, via this syntax:
        smb://servername/SomeFolder/AnotherFolder/
    When the email recipient clicks on the link (which appears by default as blue underlined), OS X automatically mounts the server as a local volume, and Finder  opens a window so that they can see the folder contents.
    But when trying to create a link to a particular file, via this syntax:
        smb://servername/SomeFolder/AnotherFolder/FileToShare.mp4
    It doesn't work. When the recipient clicks on the link, Finder appears to mount an empty fictitious volume called SomeFolder/AnotherFolder/FileToShare.mp4, containing no files. It is as if the URL parsing support for Samba links only supports referencing directories rather than individual files.
    By contrast, on Windows sharing a file can be done via this syntax:
         \\servername\SomeFolder\AnotherFolder\FileToShare.mp4
    And clicking on the link would automatically open the file (e.g. in whatever application is associated to play the video, edit the document, etc).
    Is there any way to create a clickable link to a file (not folder) on an SMB server?
    Matthew

    Thank you for trying to help.
    However, that utility does not solve the problem as far as I can tell. Regardless of whether the link text is typed in manually, or is 'snagged' via some utility, it still doesn't work in the case I was mentioning. All options in PathSnagger require that the drive is already mounted, as far as I can tell. And once it is mounted, PathSnagger generates the following strings for various options:
         Snag Path Windows:          \Volumes\servername\SomeFolder\AnotherFolder\FileToShare.mp4
         Snag Path Unix:               /Volumes/servername/SomeFolder/AnotherFolder/FileToShare.mp4
         Snag Path HFS:          servername:SomeFolder:AnotherFolder:FileToShare.mp4
         Snag Path File:          file://localhost/Volumes/servername/SomeFolder/AnotherFolder/FileToShare.mp4
    Note that none of these retain the original server location and protocol (smb://servername) because the volume is now mounted. As such, if emailed to another recipient, in general they do not work.
    Perhaps my original question was not clear. Is there any way to create a clickable link to a file (not a folder) on an SMB server, so that the link can be emailed to other people, and email recipient clicks on the click, the file is opened? (And server volumes mounted automatically as necessary)
    On Windows it can be done via a link such as:
         \\servername\SomeFolder\AnotherFolder\FileToShare.txt
    On Mac, the corresponding support for Samba URLs seems incomplete. A link such as:
         smb://servername/SomeFolder/AnotherFolder/FileToShare.txt
    does not appear to work even on the sender's computer, and even if the server is already mounted.
    The expected behaviour is that when a user (e.g. email recipient) clicks on the link, it should mount the server (if necessary) and open the file (in the example above, FileToShare.txt). Unfortunately, this does not seem to happen.
    Matthew

  • Service for network file system fails to install

    Installation of the File Service and Service for NFS in Windows 2008 R2 server fails. Following are the steps used to perform the install.
    Open Server Manager from Start> All Programs> Administrative Tools> Server Manager.
    Click on the Roles node in the left pane, and then click the
    Add Roles link.
    On the Add Roles Wizard welcome page, click Next to continue.
    From the list of roles to install, select File Services, and click
    Next to continue.
    On the Introduction to File Services page, click Next to continue.
    On the Select Role Services page, keep the File Server box checked and select
    Services for Network File System. Click Next to continue.
    On the Confirmation page, review the settings and click the Install button.
    Click Close when the wizard completes.
    ServerManager Log:
    From the ServerManager.log file under C:/Windows/Logs I can see the below.
    2272: 2013-02-12 16:13:51.479 [CBS]                       IsCacheStillGood: True.
    2272: 2013-02-12 16:14:05.534 [Provider]                  System changed since last refresh: False
    2272: 2013-02-12 16:15:45.816 [InstallationProgressPage]  Loading progress page...
    2272: 2013-02-12 16:15:45.831 [InstallationProgressPage]  Begining Sync operation...
    2272: 2013-02-12 16:15:45.842 [Sync]                     
    Sync Graph of changed nodes
    ==========
    name     : File Services
    state    : Changed
    rank     : 1
    sync tech: CBS
    guest[1] : File Server
    guest[2] : Distributed File System
    guest[3] : File Server Resource Manager
    guest[4] : Services for Network File System
    guest[5] : Single Instance Storage
    guest[6] : Windows Search Service
    guest[7] : Windows Server 2003 File Services
    guest[8] : BranchCache for network files
    provider : FileServerRoleProvider
    name     : Services for Network File System
    state    : Changed
    rank     : 2
    sync tech: CBS
    provider : FileServerRoleProvider
    name     : File Server
    state    : Changed
    rank     : 2
    sync tech: CBS
    provider : FileServerRoleProvider
    2272: 2013-02-12 16:15:45.842 [Sync]                      Calling sync provider of Services for Network File System ...
    2272: 2013-02-12 16:15:45.843 [FileServer]                Sync:: guest: 'Services for Network File System', guest deleted?: False
    2272: 2013-02-12 16:15:45.843 [FileServer]                Begin installation of 'Services for Network File System'...
    2272: 2013-02-12 16:15:45.843 [FileServer]                Install: Guest: 'Services for Network File System', updateElement: 'ServicesForNFS-ServerAndClient;ClientForNFS-Infrastructure;NFS-Administration;ServerForNFS-Infrastructure'
    2272: 2013-02-12 16:15:45.843 [FileServer]                Installation queued for 'Services for Network File System'.
    2272: 2013-02-12 16:15:45.843 [Sync]                      Calling sync provider of File Server ...
    2272: 2013-02-12 16:15:45.843 [FileServer]                Sync:: guest: 'File Server', guest deleted?: False
    2272: 2013-02-12 16:15:45.843 [FileServer]                Begin installation of 'File Server'...
    2272: 2013-02-12 16:15:45.843 [FileServer]                Install: Guest: 'File Server', updateElement: 'CoreFileServer'
    2272: 2013-02-12 16:15:45.843 [FileServer]                Installation queued for 'File Server'.
    2272: 2013-02-12 16:15:45.844 [CBS]                       installing 'ServicesForNFS-ServerAndClient ClientForNFS-Infrastructure
    NFS-Administration ServerForNFS-Infrastructure CoreFileServer ' ...
    2272: 2013-02-12 16:15:46.315 [CBS]                       ...parents that will be auto-installed: '<none>'
    2272: 2013-02-12 16:15:46.316 [CBS]                       ...default children to turn-off: '<none>'
    2272: 2013-02-12 16:15:46.325 [CBS]                       ...current state of 'ServicesForNFS-ServerAndClient': p:
    Staged, a: Staged, s: UninstallRequested
    2272: 2013-02-12 16:15:46.325 [CBS]                       ...setting state of 'ServicesForNFS-ServerAndClient' to
    'InstallRequested'
    2272: 2013-02-12 16:15:46.335 [CBS]                       ...current state of 'ClientForNFS-Infrastructure': p: Staged,
    a: Staged, s: UninstallRequested
    2272: 2013-02-12 16:15:46.336 [CBS]                       ...setting state of 'ClientForNFS-Infrastructure' to 'InstallRequested'
    2272: 2013-02-12 16:15:46.345 [CBS]                       ...current state of 'NFS-Administration': p: Staged, a:
    Staged, s: UninstallRequested
    2272: 2013-02-12 16:15:46.345 [CBS]                       ...setting state of 'NFS-Administration' to 'InstallRequested'
    2272: 2013-02-12 16:15:46.354 [CBS]                       ...current state of 'ServerForNFS-Infrastructure': p: Staged,
    a: Staged, s: UninstallRequested
    2272: 2013-02-12 16:15:46.354 [CBS]                       ...setting state of 'ServerForNFS-Infrastructure' to 'InstallRequested'
    2272: 2013-02-12 16:15:46.363 [CBS]                       ...current state of 'CoreFileServer': p: Staged, a: Staged,
    s: UninstallRequested
    2272: 2013-02-12 16:15:46.363 [CBS]                       ...setting state of 'CoreFileServer' to 'InstallRequested'
    2272: 2013-02-12 16:15:46.373 [CBS]                       ...'ServicesForNFS-ServerAndClient' : applicability: Applicable
    2272: 2013-02-12 16:15:46.390 [CBS]                       ...'ClientForNFS-Infrastructure' : applicability: Applicable
    2272: 2013-02-12 16:15:46.408 [CBS]                       ...'NFS-Administration' : applicability: Applicable
    2272: 2013-02-12 16:15:46.426 [CBS]                       ...'ServerForNFS-Infrastructure' : applicability: Applicable
    2272: 2013-02-12 16:15:46.435 [CBS]                       ...'CoreFileServer' : applicability: Applicable
    2272: 2013-02-12 16:15:46.493 [CbsUIHandler]              Initiate:
    2272: 2013-02-12 16:15:46.494 [InstallationProgressPage]  Installing...
    2272: 2013-02-12 16:15:51.958 [CbsUIHandler]              Error: -2147021879 :
    2272: 2013-02-12 16:15:51.958 [CbsUIHandler]              Terminate:
    2272: 2013-02-12 16:15:52.035 [InstallationProgressPage]  Verifying installation...
    2272: 2013-02-12 16:15:52.049 [CBS]                       ...done installing 'ServicesForNFS-ServerAndClient
    ClientForNFS-Infrastructure NFS-Administration ServerForNFS-Infrastructure CoreFileServer '.
    Status: -2147021879 (80070bc9)
    2272: 2013-02-12 16:15:52.052 [FileServer]                Skipped configuration of 'Services for Network File System' because install operation failed.
    2272: 2013-02-12 16:15:52.053 [FileServer]                Skipped configuration of 'File Server' because install operation failed.
    2272: 2013-02-12 16:15:52.053 [Provider]                 
    [STAT] ---- CBS Session Consolidation -----
    [STAT] For
              'Services for Network File System',
              'File Server'[STAT] installation(s) took '6.2058637' second(s) total.
    [STAT] Configuration(s) took '0.0002143' second(s) total.
    [STAT] Total time: '6.206078' second(s).
    2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 105
    2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot
    is required to roll back changes made
    2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 255
    2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot
    is required to roll back changes made
    2272: 2013-02-12 16:15:52.054 [InstallationProgressPage]  Sync operation completed
    2272: 2013-02-12 16:15:52.054 [InstallationProgressPage]  Performing post install/uninstall discovery...
    2272: 2013-02-12 16:15:52.056 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
    2272: 2013-02-12 16:15:52.056 [CBS]                       IsCacheStillGood: False.
    2272: 2013-02-12 16:15:52.526 [CBS]                       >>>GetUpdateInfo--------------------------------------------------
    2272: 2013-02-12 16:15:59.342 [CBS] Error (Id=0) Function: 'ReadUpdateInfo()->Update_GetInstallState' failed:
    80070bc9 (-2147021879)
    2272: 2013-02-12 16:15:59.342 [CBS]                       <<<GetUpdateInfo--------------------------------------------------
    2272: 2013-02-12 16:15:59.380 [DISCOVERY]                 hr: -2147021879 -> reboot required.
    2272: 2013-02-12 16:15:59.390 [InstallationProgressPage]  About to load finish page...
    2272: 2013-02-12 16:15:59.390 [InstallationFinishPage]    Loading finish page
    2272: 2013-02-12 16:15:59.401 [InstallationFinishPage]    Finish page loaded
    In Windows Event long I can see the following events logged:
    Event 3002, Port Map:
      Windows(R) failed a request to register RPC Port Mapper on TCP port 111.  RPC Port Mapper cannot start.
      Network File System (NFS) clients use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on remote servers.  Without RPC Port Mapper, Server for NFS
    cannot start and NFS clients cannot access files on this server.
      Verify that no other software is registered on TCP port 111, then start Server for NFS manually (which will also start RPC Port Mapper).
    Event 7000, Service Control Manager:
    The Server for NFS Open RPC (ONCRPC) Portmapper service failed to start due to the following error:
    A device attached to the system is not functioning.
    Event 7001, Service Control Manager:
    The Server for NFS Driver service depends on the Server for NFS Open RPC (ONCRPC) Portmapper service which failed to start because of the following error:
    A device attached to the system is not functioning.
    Event 7001, Service Control Manager:
    The Server for NFS service depends on the Server for NFS Driver service which failed to start because of the following error:
    The dependency service or group failed to start.
    Based on a technet forum I have already checked and made sure there is no other service running on port 111 (command used is netstat -a -b -o).
    Dependent Service Status:
    During the installation process “Client for NFS” seems to have gone well and the service started successfully. But the “Server for NFS” failed, when checked for the status of the dependent process “portmap” service failed to start with the WIN32_EXIT_CODE
    “31 (0x1f)”. Please find below the query result.
    C:\Users\CMMAdmin>sc query rpcxdr
    SERVICE_NAME: rpcxdr
            TYPE               : 1  KERNEL_DRIVER
            STATE              : 4  RUNNING
                                    (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\Users\CMMAdmin>sc query msnfsflt
    SERVICE_NAME: msnfsflt
            TYPE               : 2  FILE_SYSTEM_DRIVER
            STATE              : 4  RUNNING
                                    (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\Users\CMMAdmin>sc query portmap
    SERVICE_NAME: portmap
            TYPE               : 1  KERNEL_DRIVER
            STATE              : 1  STOPPED
            WIN32_EXIT_CODE    : 31  (0x1f)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\Users\CMMAdmin>
    As the EXIT CODE is 31 ( A device attached to the system is not functioning), I have checked device manager and made sure there is no yellow warning shown against any hardware device. Further I am not sure how to proceed and debug this issue.
    Please let me know if you have any suggestion on how debug this issue further.
    Thanks
    -Poopesh

    Hey,
    I had this same problem running MS Server 2008 R2 and server log is as follow:
    name     : Services for Network File System
    state    : Changed
    rank     : 2
    sync tech: CBS
    ant.     : empty
    pred.    : File Services
    provider : FileServerRoleProvider
    5676: 2014-01-14 14:08:57.474 [Sync]                      Calling sync provider of Services for Network File System ...
    5676: 2014-01-14 14:08:57.521 [FileServer]                Sync:: guest: 'Services for Network File System', guest deleted?: False
    5676: 2014-01-14 14:08:57.536 [FileServer]                Begin installation of 'Services for Network File System'...
    5676: 2014-01-14 14:08:57.536 [FileServer]                Install: Guest: 'Services for Network File System', updateElement: 'ServicesForNFS-ServerAndClient;ClientForNFS-Infrastructure;NFS-Administration;ServerForNFS-Infrastructure'
    5676: 2014-01-14 14:08:57.536 [FileServer]                Installation queued for 'Services for Network File System'.
    5676: 2014-01-14 14:08:57.536 [CBS]                       installing 'ServicesForNFS-ServerAndClient ClientForNFS-Infrastructure NFS-Administration
    ServerForNFS-Infrastructure ' ...
    5676: 2014-01-14 14:09:00.173 [CBS]                       ...parents that will be auto-installed: '<none>'
    5676: 2014-01-14 14:09:00.173 [CBS]                       ...default children to turn-off: '<none>'
    5676: 2014-01-14 14:09:00.204 [CBS]                       ...current state of 'ServicesForNFS-ServerAndClient': p: Staged, a: Staged, s: UninstallRequested
    5676: 2014-01-14 14:09:00.204 [CBS]                       ...setting state of 'ServicesForNFS-ServerAndClient' to 'InstallRequested'
    5676: 2014-01-14 14:09:00.235 [CBS]                       ...current state of 'ClientForNFS-Infrastructure': p: Staged, a: Staged, s: UninstallRequested
    5676: 2014-01-14 14:09:00.235 [CBS]                       ...setting state of 'ClientForNFS-Infrastructure' to 'InstallRequested'
    5676: 2014-01-14 14:09:00.266 [CBS]                       ...current state of 'NFS-Administration': p: Staged, a: Staged, s: UninstallRequested
    5676: 2014-01-14 14:09:00.266 [CBS]                       ...setting state of 'NFS-Administration' to 'InstallRequested'
    5676: 2014-01-14 14:09:00.282 [CBS]                       ...current state of 'ServerForNFS-Infrastructure': p: Staged, a: Staged, s: UninstallRequested
    5676: 2014-01-14 14:09:00.282 [CBS]                       ...setting state of 'ServerForNFS-Infrastructure' to 'InstallRequested'
    5676: 2014-01-14 14:09:00.313 [CBS]                       ...'ServicesForNFS-ServerAndClient' : applicability: Applicable
    5676: 2014-01-14 14:09:00.360 [CBS]                       ...'ClientForNFS-Infrastructure' : applicability: Applicable
    5676: 2014-01-14 14:09:00.422 [CBS]                       ...'NFS-Administration' : applicability: Applicable
    5676: 2014-01-14 14:09:00.469 [CBS]                       ...'ServerForNFS-Infrastructure' : applicability: Applicable
    5676: 2014-01-14 14:09:01.624 [CbsUIHandler]              Initiate:
    5676: 2014-01-14 14:09:01.624 [InstallationProgressPage]  Installing...
    5676: 2014-01-14 14:09:35.117 [CbsUIHandler]              Error: -2147021879 :
    5676: 2014-01-14 14:09:35.117 [CbsUIHandler]              Terminate:
    5676: 2014-01-14 14:09:41.170 [InstallationProgressPage]  Verifying installation...
    5676: 2014-01-14 14:09:41.264 [CBS]                       ...done installing 'ServicesForNFS-ServerAndClient ClientForNFS-Infrastructure NFS-Administration
    ServerForNFS-Infrastructure '. Status: -2147021879 (80070bc9)
    5676: 2014-01-14 14:09:41.279 [FileServer]                Skipped configuration of 'Services for Network File System' because install operation failed.
    5676: 2014-01-14 14:09:41.279 [Provider]                 
    [STAT] ---- CBS Session Consolidation -----
    [STAT] For
              'Services for Network File System'[STAT] installation(s) took '43.7368586' second(s) total.
    [STAT] Configuration(s) took '0.0062843' second(s) total.
    [STAT] Total time: '43.7431429' second(s).
    5676: 2014-01-14 14:09:41.279 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 105
    5676: 2014-01-14 14:09:41.279 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot is required to roll back changes
    made
    5676: 2014-01-14 14:09:41.279 [InstallationProgressPage]  Sync operation completed
    5676: 2014-01-14 14:09:41.279 [InstallationProgressPage]  Performing post install/uninstall discovery...
    5676: 2014-01-14 14:09:41.295 [Provider]                  C:\windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
    5676: 2014-01-14 14:09:41.295 [CBS]                       IsCacheStillGood: False.
    5676: 2014-01-14 14:09:43.900 [CBS]                       >>>GetUpdateInfo--------------------------------------------------
    5676: 2014-01-14 14:09:57.394 [CBS] Error (Id=0) Function: 'ReadUpdateInfo()->Update_GetInstallState' failed: 80070bc9 (-2147021879)
    5676: 2014-01-14 14:09:57.410 [CBS]                       <<<GetUpdateInfo--------------------------------------------------
    5676: 2014-01-14 14:09:57.488 [DISCOVERY]                 hr: -2147021879 -> reboot required.
    5676: 2014-01-14 14:09:57.613 [InstallationProgressPage]  About to load finish page...
    5676: 2014-01-14 14:09:57.628 [InstallationFinishPage]    Loading finish page
    5676: 2014-01-14 14:09:57.644 [InstallationFinishPage]    Finish page loaded
    My solution was to run netstat -ano to identify what process was running on port TCP/UDP :111, then with the command tasklist I got PID matching with the task name. Once identified I stopped the process, rebooted and installed
    the NFS service. On top of that, before installing NFS services I disabled firewall and antivirus. It worked fine for me. I hope this will be usefull for you. By the way, don't forget to enable all process back!
    Have a good one!

  • How do I email a link to a file on my server?

    I know on windows machines you can email a link to different files on your computer that other people have access to like c:/caleb/documents/... but I am not sure how to do that with a mac
    We use a server at work and my boss always tells me to open different files that are hard to navigate to. I am wondering if there is a way for him to just email me a link to the file so I can just click on the text in my email and it will open up the finder window with the file in it.
    Any help would be appreciated.
    Thank you,
    Caleb

    If users are on the local windows machine then "C:/path/..." will work, but if they're accessing it through the network then "\\servername\sharename\path\file" is how it's linked.
    In the mac it's the same way. If "windows" file sharing is enabled then the slash-slash method will work if the users are on a windows PC. Otherwise, it will require the use of specific protocol prefixes in the address. For connecting via AFP (apple filing protocol -- the default and mac-native networking system) the following is the address to use:
         afp://servername/sharename/path/file
    Emailing this address to users who can get network access to the computer will allow them to click the link and connect. For example, my machine is called "Laptop" (ip address is 192.168.1.3) and I have a file called "textfile.txt" located in a "testfolder" in my "Public" directory (which is the shared directory that is readable by users other than myself). To send a link to that file I'd send the following:
         afp://Laptop/Public/testfolder/textfile.txt
    Alternately I can link to it using the IP address as follows:
         afp://192.168.1.3/Public/testfolder/textfile.txt
    To connect to the same computer via windows networking (from a PC or Mac that has windows networking enabled), ensure you have windows networking turn on in your computer and the only difference in the address would be to use "smb" instead of "afp" in the addresses above. This is for NON-windows computers; since windows machines will not know what to do with "smb://servername...", and instead will require the "\\servername\..." notation.

  • Using getURL to access network files

    I am working on an Intranet site and I need a button in Flash
    to open a file that's on our network share. I know about the getURL
    function and use it often to link to HTML files that are on the
    same server as the web files, but I don't know how to use getURL to
    open external files on the network:
    example:
    on (release) {
    getURL("page1.html", "_blank");
    page1.html is located on the webserver but contains a link to
    \\server1\share1\document1.doc (server1 is a different server on
    our network)
    I want to eliminate the middle man and link directly to
    document1.doc, but I don't know how to do that with getURL since
    document1.doc is not on the webserver.
    Thanks for any advice.

    I don't believe you can like directly to this file on your
    network because of the security features built into flash which
    will not allow network access such as this.

  • Want to access network file system using JFileChooser

    Hi all,
    I want to access and display the drives of a network file system in the JFileChooser dialog. For example by specifying a machine name, I want to access the drives(C, E, F....) of that machine. Can anyone please guide me on how to go forward with this.
    Thanks in advance

    Any links or guidance provided would bhi helpful

  • [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

  • Creating hyperlink to a network file?

    Hello All,
    I am having issues with Adobe Acrobat and hyperlink to a network file.  I am using Acrobat XI and I have successfully created a link to a text that "Open a File" located on our network share.  It works great, when others are executing the PDF from the network share, but when I send the PDF to another user and he/she tries to click the link it adds the local computer path in front of the "original" path of where the file is located.
    Is there a way to correct this? 

    You attached the PDF to the email. The reciepent views the PDF from within the email client/application or saves the attached PDF to the local machine's hard drive. In either case, yes, Acrobat and Reader resolve the link from within context of the local machine.
    Network shares typically are provided a mapped drive.
    Perhaps "X" or "S" or whatever.
    If this is common to all users  then simply place the path shown in the file browser's address bar in the body of the email.
    Example:
    "X:\PDF\Saves\" would, when clicked from within the body of the email, open a file browser session to the "Saves" folder and display whatever files were in the folder.
    Or
    "X:\PDF\Saves\xxxx.pdf" would result in the PDF being opened in the Adobe Reader / Acrobat.
    How a PDF can refer to the contents of another PDF file read section 7.11 File Sepecifications in ISO 32000-1.
    http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_200 8.pdf
    Be well...

  • Link to attached file

    Hi,
    I have a PDF with and a file attached to it (Excel sheet). I want to make a link in my document to open the attached file. How can I do that?
    The background:
    I was not my first idea to attach the file. I would like better linking the file which is normally on a mapped network drive. I have to share my PDF between users and I did no manage putting an absolute link into my PDF. If the first part of my question does not work, can someone tell me how I can put a static (link will never change), absolute link to a file which is on a mapped network drive?
    Thanks to all,

    It's possible, but only using a script... (I was talking about linking to an attached file, not an external file on a server)

  • Links to external files do nothing after being burned to disk

    I built a product catalog a while ago in CS4 and now I've had to edit it in InDesign CS5. With InDesign CS4, everything worked fine. The files were linked and then all the file were burned to disk, all the files worked on the disk (links, etc). I have since edited the files in InDesign CS5. I build the catalog, created all the links (interior within the same pdf, links to external pdfs and other file types). Everything works on the computer  but somehow fails after being burned to disk.
    My sequence  was like this:
    Set up product catalog last year with links and files, everything was fine and worked as expected.
    Opened the file, made my edits.
    Made links between the pdf's pages and from the pdf to external pdfs and videos etc. All of these links work in the pdf.
    Burn the files to a disk
    Some of the old links work
    All the links within the main pdf work
    None of the new links to external files work. I click the link and nothing happens. The paths are exactly the same as the previous version
    I have tried:
    Examining the links, everything is based on pseudo relative paths (last year it worked fine)
    Burning the disk on a Mac and a Windows XP
    Please help. Any and all help is very much apprecitated.

    I figured it out.
    I created the links in InDesign by making an interactive link to a file. When I open the file in Acrobat, the links work fine over the network. I burn to disk and the links no longer work.
    Problem: At some point, InDesign changes the "open file" hyperlink command in InDesign into a URL webpage request in Acrobat.
    Solution: So basically, I now have to go into the file in Acrobat and change all the buttons from "open web link" to "open file." It's only a product catalog with about 1,200 links that's due today.

  • Office 2010 - Opening Network Files causes crashes

    Our users documents are mapped to network storage via a Home folder location. Our treasurer has began encountering an issue with Office 2010 with Word (this is where I've been putting most of my effort) and Excel, other programs not tested. 
    Upon going to 'File->Open' it automatically redirects to his Home folder on the Network drive, and Office goes through it's various stages of crashing (encountered an issue, etc.) I've copied the contents of one specific folder he does most of his work in
    to his desktop, but this is not optimal. Opening the contents from the desktop yields no issue.
    As far as troubleshooting goes, I first tried doing a repair, then reinstall, and finally an advanced uninstall with Revo figuring it may be a corrupted registry key. None of this worked. I Googled some info on it and found add-ons commonly caused an issue.
    I went as far as recommended by a MS support article, ultimately removing both the entire add-ins folder in Program files and in the registry. Still an issue. I progressed through various other support articles, removing various further keys (settings, toolbars,
    etc.) Still occurring. I landed upon a technet article with nearly an exact issue, and it recommended updating as MS had fixed this various issue. (duh!) Update-wise, it was pretty far behind because all of our updates are signed through SCCM, regardless,
    I have it fully updated up to Office Service pack 2. It's doing selective startups through msconfig as well, down to only Microsoft services. Finally, I've tried sfc /scannow, as well as safe mode, and neither had promising results (it was the first time I
    was really hoping for sfc to find an error!
    Just for further reference, I've tried all fixes in this article (before realizing it was only on network docs.) http://support.microsoft.com/kb/921541/en-us
    As well as everything here: http://social.technet.microsoft.com/Forums/office/en-US/a31f0a8e-e371-420f-a3f3-f85713f7ac0f/word-crashes-when-trying-to-open-file-from-network?forum=word
    I attempted the crash dumps in this thread but was ultimately unsuccessful http://social.technet.microsoft.com/Forums/office/en-US/95bc7898-e92d-4e47-8f73-390dba53e851/office-2010-applications-can-not-open-network-files-without-crashing?forum=officeitproprevious 

    Hi,
    Have you found anything in event Viewer?
    Press Win + R and type “eventvwr” in the blank box, then press Enter.
    You may find some information to determine the issue and post the information here to let me know more about this issue.
    You can learn how to user event viewer from this link:
    http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/
    Regards,
    Melon Chen
    TechNet Community Support

Maybe you are looking for