Client drive mapping - ERROR_NO_NET_OR_BAD_PATH

I'm trying to set up CDM from a on Linux running SGD to a Windows 2003 SP1. The enhancement tools are installed and configured.
However, I get not network drives connected. I see the following on the sgd server:
2006/05/05 00:27:34.535 (pid 31430) cpe/circuit #0
Sun Secure Global Desktop Software(4.2) ERROR:
Failed to connect to service at: /opt/tarantella/var/ttasocket-cdm
2006/05/05 01:07:23.753 (pid 31430) cpe/circuit #2
Sun Secure Global Desktop Software(4.2) ERROR:
Failed to connect to service at: /opt/tarantella/var/ttasocket-cdm
but the processes are running:
appl5p01:/opt/tarantella/var/log # ps -ef | grep cdm | grep -v ttaaux
ttasys 1333 1 0 02:02 ? 00:00:00 /opt/tarantella/bin/bin/ttacdmd /opt/tarantella 5427
ttasys 1363 1333 0 02:02 ? 00:00:00 /opt/tarantella/bin/bin/ttacdmd /opt/tarantella 5427
On the Windows 2003 box after logging in I see the following log:
01:51:13 : 00000391: doehrm : Device name I
01:51:13 : 00000391: doehrm : Display name Drive C for Doehr
01:51:13 : 00000391: doehrm : Device class 9
01:51:13 : 00000391: doehrm : Characteristics 0
01:51:13 : 00000391: doehrm : accessFlags 1
01:51:13 : 00000391: doehrm : Packet >> Packet nLength 0
01:51:13 : 00000391: doehrm : Packet >> Authentication type 1
01:51:13 : 00000391: doehrm : Packet >> Packet nLength 44
01:51:13 : 00000391: doehrm : URI smb://appl5p01.aubi.de/Drive C for Doehr
01:51:13 : 00000391: doehrm : Packet >> Packet nLength 20
01:51:13 : 00000391: doehrm : Packet >> Packet nLength 0
01:51:13 : 00000406: doehrm : Found service provider
01:51:13 : 00000406: doehrm : addDevice : Drive C for Doehr 0 smb://appl5p01.aubi.de/Drive C for Doehr
01:51:13 : 00000406: doehrm : Base64Buffer length = 20
01:51:13 : 00000406: doehrm : 0x009c1810 5a 47 39 6c 61 48 4a 66 58 31 38 31 4e 6a 49 33 ZG9laHJfX181NjI3
01:51:13 : 00000406: doehrm : 0x009c1820 4d 6a 55 3d MjU=
01:51:13 : 00000438: doehrm : Base64Buffer length = 20
01:51:13 : 00000438: doehrm : 0x009c1810 51 54 6c 43 49 7a 4e 66 4b 30 4e 45 49 55 70 56 QTlCIzNfK0NEIUpV
01:51:13 : 00000438: doehrm : 0x009c1820 4e 44 51 3d NDQ=
01:51:13 : 00000469: doehrm : URI host appl5p01.aubi.de
01:51:13 : 00000469: doehrm : URI file Drive C for Doehr
01:51:13 : 00000469: doehrm : Share = \\appl5p01.aubi.de\Drive C for Doehr
01:51:13 : 00000469: doehrm : Packet >> Packet nLength 5
01:51:13 : 00000469: doehrm : General options flags 8
01:51:13 : 00000469: doehrm : Alternative name = Z:
01:51:13 : 00000469: doehrm : Packet >> Packet nLength 3
01:51:13 : 00000469: doehrm : DEVICE_CLASS_FILESYSTEM
01:51:13 : 00000469: doehrm : device flags 2
01:51:13 : 00000469: doehrm : Device info : Dos name = , search = 1, searchUp = 0
01:51:21 : 00008875: doehrm : Add device failed with ERROR_NO_NET_OR_BAD_PATH
01:51:21 : 00008875: doehrm : failed to add device
01:51:21 : 00008875: doehrm : WTSVirtualChannelWrite returned 18 bytes
01:51:21 : 00008875: doehrm : 0x0042b270 01 10 00 00 00 00 00 00 00 01 01 00 00 00 00 00 ................
01:51:22 : 00008906: doehrm : 0x0042b280 00 00 ..
In the /opt/tarantella/log/cdm<pid>.log I see also:
Connected client for Tarantella user ".../_ens/o=organization/cn=Doehr" (mapped to SMB user "doehr___562724")
2006/05/05 01:45:57.326 (pid 1333) cdm/audit/info #9 Sun Secure Global Desktop Software(4.2)
I already increased the timeout parameters in the registry and rebooted the system, restarted tarantella etc. but no avail. :( Somtimes I see a "nonconnected network drive" in the explorer but it is indeed not connected. Name resolution works in both directions.
Does anyone have an idea what can be wrong?
This is tta-4.20-909.
Thank you very much!
Markus

Yes, we have the same sympthoms. After tarantella stop cdm and start cdm and relogin of the user it works. This is in 4.20 so I think its also onm 4.00 which is pretty old.
Btw: I always use the WINS support which gave me a better stability.

Similar Messages

  • Client Drive Mapping (Windows) not working in SGD 4.6

    I've upgrade your sgd 4.5 to 4.6. Currently we are using Virtual Desktop Connector 1.0 with VMware.
    Now I'm ran into a problem with client drive mapping for Windows. CDM has changed in 4.6 from smb to rdp-protocol. So there ist no need for the Enhancement Module on the client.
    CDM works well with Windows Server 2003 R2 Terminal Services, but not with Windows XP SP3. In XP there are not clientdrives in explorer. Opening \\tsclient I can see the clientdrives e.g. +\\tsclient\F (rw)+. But when I try to open the folder I get an error, telling me that I didn't have enough rights to access this share.
    This happens with a regular VDI-VM (in domain) and to a fresh standalone VM. Also a direct rdp-connect to the vm from Win XP and Win 7 Remote Desktop Client works (local drives are mapped).
    Is there any known problem with sgd 4.6 cdm and win xp?
    I didn't find any error in the logfiles, but perhaps I didn't look in the right logs. :-)
    Thomas

    We've just encountered this issue on a SGD 4.6 & Oracle VDI 3.2.1 deployment (XP Desktops), disappointed because we moved from 4.5 to 4.6 due to the expired Verisign cert therein.
    Connecting to a 2008R2 Domain controller is fine, no problem and drives mapped as expected.
    Have logged a service request, hopefully I've missed something obvious.

  • SGD (Tarantella) 4.0.903: Client Drive Mapping: Unknown Error 64

    Hi,
    Environment: SDG Server on SUSE 9 Enterprise
    Windows Server 2003 SP1 (application server) with enhancement module installed.
    I have the folowing issue with the SDG: The ClientDriveMapping Feature worked some time ago. But from one day to another it stopped working.
    I tried all advices mentioned in the Troubleshooting Guid from the docs.
    All Services seem to work.
    If I use the ttatdm.exe tool on the W2k3 Server for debugging, I can see that it tries to map all of the client drives but fails with <Unknown Error 64>.
    Any ideas are welcome...
    Here is part of the debug log:
    17:10:14 : 00000016: xxxx : WTSQuerySessionInformation dwLength = 2
    17:10:14 : 00000016: xxxx : WTSServer::isDesktopSession returns 1
    17:10:14 : 00000016: xxxx : Global\TTDMP-1-Reconnect
    17:10:14 : 00000016: xxxx : Global\TTDMP-1-Disconnect
    17:10:14 : 00000016: xxxx : Created server channel
    17:10:14 : 00000016: xxxx : WTSVirtualChannelWrite returned 13 bytes
    17:10:14 : 00000032: xxxx : 0x0042a220 01 00 01 00 04 00 73 6d 62 00 01 00 00 ......smb....
    17:10:14 : 00000032: xxxx : ServerChannel::isDataAvailable WTSVirtualChannelRead returned 2 bytes
    17:10:14 : 00000032: xxxx : 0x0042a864 01 00 ..
    17:10:14 : 00000032: xxxx : TTDMServer::process waiting for the init reply
    17:10:14 : 00000032: xxxx : TTDMServer:process got init reply version 1.0
    17:10:14 : 00000032: xxxx : ServerChannel::isDataAvailable WTSVirtualChannelRead returned 190 bytes
    ...snip...
    17:10:15 : 00000094: xxxx : TTDMServer::process messagecode 0 deviceid 0
    17:10:15 : 00000094: xxxx : AddDevice
    17:10:15 : 00000094: xxxx : Device name Z
    17:10:15 : 00000094: xxxx : Display name Drive C for Administrator
    17:10:15 : 00000094: xxxx : Device class 9
    17:10:15 : 00000094: xxxx : Characteristics 0
    17:10:15 : 00000094: xxxx : accessFlags 1
    17:10:15 : 00000094: xxxx : Packet >> Packet nLength 0
    17:10:15 : 00000094: xxxx : Packet >> Authentication type 1
    17:10:15 : 00000094: xxxx : Packet >> Packet nLength 44
    17:10:15 : 00000094: xxxx : URI smb://tarantella.xxx.yy/Drive C for Administrator
    17:10:15 : 00000110: xxxx : Packet >> Packet nLength 20
    17:10:15 : 00000110: xxxx : Packet >> Packet nLength 0
    17:10:15 : 00000110: xxxx : Found service provider
    17:10:15 : 00000110: xxxx : addDevice : Drive C for Administrator 0 smb://tarantella.xxx.yy/Drive C for Administrator
    17:10:15 : 00000110: xxxx : Base64Buffer length = 20
    17:10:15 : 00000110: xxxx : 0x009b16a0 59 57 52 74 61 57 35 70 63 33 51 31 4e 44 41 32 YWRtaW5pc3Q1NDA2
    17:10:15 : 00000110: xxxx : 0x009b16b0 4e 6a 41 3d NjA=
    17:10:15 : 00000110: xxxx : Base64Buffer length = 20
    17:10:15 : 00000110: xxxx : 0x009b16a0 4e 31 46 4c 57 55 70 66 53 45 34 74 4a 55 45 35 N1FLWUpfSE4tJUE5
    17:10:15 : 00000125: xxxx : 0x009b16b0 53 55 55 3d SUU=
    17:10:15 : 00000125: xxxx : URI host tarantella.xxx.yy
    17:10:15 : 00000125: xxxx : URI file Drive C for Administrator
    17:10:15 : 00000125: xxxx : Share = \\tarantella.xxx.yy\Drive C for Administrator
    17:10:15 : 00000125: xxxx : Packet >> Packet nLength 5
    17:10:15 : 00000125: xxxx : General options flags 8
    17:10:15 : 00000125: xxxx : Alternative name = W:
    17:10:15 : 00000125: xxxx : Packet >> Packet nLength 3
    17:10:15 : 00000125: xxxx : DEVICE_CLASS_FILESYSTEM
    17:10:15 : 00000125: xxxx : device flags 2
    17:10:15 : 00000125: xxxx : Device info : Dos name = , search = 1, searchUp = 1
    17:10:15 : 00000297: xxxx : Add device failed with Unknown error 64
    17:10:15 : 00000297: xxxx : failed to add device
    Cheers

    I experienced this as well and fixed this by changing firewall settings (fw between sgd and w2k3 appserver)
    Do you have a firewall (or other device) between sgd and w2k server.
    If a intermediate device responds somehow on port 445 to the w2k3 server then it will try to use the wrong protocol (by default) to map the sgd drives. sgd cdm only uses port 137/139 to show drives to their clients.
    Regards,
    Erik.

  • TTA 4.1 Client Drive Mapping

    The following problem is occurring on various Windows Terminal Server
    sessions using TTA 4.1.
    In the Windows Application Event Log:
    Event ID: 20
    Description:
    The specified password is invalid ("T:"
    "\\tarantella.internal.hostname\Drive C for Person Object Name")
    -- The client C drive is mapped to T on the WTS.
    When this problem occurs, the client's local drive is not available.
    Looking forward to replies.

    Hi,
    i discovered some CDM problems in vers. 4.1 too.
    Is there anything known, related to problems
    with CDM in sgd environments using NT
    authentication for some users???
    Background: i setup a sgd/ee 4.1 together with
    a WTS 2003, turning on all cdm logging (c.f. hint
    url below). cdm works fine a while... when
    no further cdm-log statements about user logins
    and name translations appear, from this moment on
    cdm doesn't work.
    More strange, i put the WTS in a different sgd/ee
    4.1 environment, there cdm works... the only
    (obvious) difference in the setup of both systems
    is, that the working one doesn't use ntauth...
    Kind regards,
    Tankred
    John Doe wrote:
    Daniel,
    Have you looked at the following URL?
    http://www.tarantella.com/support/documentation/sgd/ee/4.1/help/en-us/base/standard/cdm.html
    Let us know where you are in the debug process.
    Daniel Hamelberg wrote:
    The following problem is occurring on various Windows Terminal Server
    sessions using TTA 4.1.
    In the Windows Application Event Log:
    Event ID: 20
    Description:
    The specified password is invalid ("T:"
    "\\tarantella.internal.hostname\Drive C for Person Object Name")
    -- The client C drive is mapped to T on the WTS.
    When this problem occurs, the client's local drive is not available.
    Looking forward to replies.

  • Allow Mapping of Client Drives via Security Group?

    Hello,
    I am setting up a RDS/Citrix farm (on server 2008 unfortunately), and I am trying to limit who can have their local client drives mapped to their server session. I know there is simply a check box in their AD properties to "Connect client drives at
    login", but since accounts get copied all the time for new users, this setting tends to get copied along with it. I'd really love to just create a security group and only allow the client drive mapping based on membership in this group. Is there a way
    to accomplish this? I was thinking maybe via GP Preferences or something similar? Any help would be greatly appreciated. Thanks in advance!
    -JR

    Hi,
    You can check below article might useful for your case.
    Using Group Policy Preferences to Map Drives Based on Group Membership
    http://blogs.technet.com/b/askds/archive/2009/01/07/using-group-policy-preferences-to-map-drives-based-on-group-membership.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Problems with drive mapping

    We have changed the server of linux that supports tarantella. We have
    installed tarantella on redhat 8 and worked perfectly. I have installed
    the tarantella enhancement module for windows and activated in the array
    manager the option " let users access client drives " but on having
    entered the session of windows not does not appear the local hard disks.
    There is something more than I have to do in order that me it works? Thank
    you for yours help

    Carmelo wrote:
    The problem is
    18:32:27 : 00007219: javi : Add device failed with ERROR_BAD_NETPATH
    You may want to enable WINS per
         http://www.tarantella.com/documentation/sgd/ee/3.42/help/en-us/base/standard/am_array.html
    -> Client Drive Mapping: Use WINS for better performance
    Regards,
    Javi wrote:
    Carmelo,
    I have verified that is running cdm, besides I have verified also that
    from the windows servers solves perfectly the name of the redhat server.
    I write you the mistakes that me appear in the log of the ttadm, for if
    you know which is the mistake. Thank you very much
    18:32:21 : 00000453: javi : URI file Drive A for Administrator
    18:32:21 : 00000453: javi : Share = \\medea\Drive A for Administrator
    18:32:21 : 00000469: javi : Packet >> Packet nLength 5
    18:32:21 : 00000469: javi : General options flags 8
    18:32:21 : 00000469: javi : Alternative name = V:
    18:32:21 : 00000469: javi : Packet >> Packet nLength 3
    18:32:21 : 00000469: javi : DEVICE_CLASS_FILESYSTEM
    18:32:21 : 00000469: javi : device flags 2
    18:32:21 : 00000469: javi : Device info : Dos name = , search = 1,
    searchUp = 0
    18:32:27 : 00007219: javi : Trying alternate device V:
    18:32:27 : 00007219: javi : Failed to add device to V:
    18:32:27 : 00007219: javi : Add device failed with ERROR_BAD_NETPATH
    18:32:27 : 00007219: javi : failed to add device
    18:32:27 : 00007219: javi : WTSVirtualChannelWrite returned 18 bytes
    18:32:27 : 00007219: javi : 0x0042a160 01 10 00 00 00 10 00 00 00 01 01
    00 00 00 00 00 ................
    18:32:27 : 00007235: javi : 0x0042a170 00 00 ..
    18:32:27 : 00007235: javi : ServerChannel::isDataAvailable
    WTSVirtualChannelRead returned 176 bytes
    18:32:27 : 00007235: javi : 0x0042a7a4 00 b0 00 00 00 11 00 00 00 01 00
    43 19 00 44 72 ...........C..Dr
    18:32:27 : 00007235: javi : 0x0042a7b4 69 76 65 20 43 20 66 6f 72 20 41
    64 6d 69 6e 69 ive C for Admini
    18:32:27 : 00007250: javi : 0x0042a7c4 73 74 72 61 74 6f 72 09 00 00 00
    00 00 00 00 01 strator.........
    18:32:27 : 00007266: javi : 0x0042a7d4 5c 00 00 00 25 00 73 6d 62 3a 2f
    2f 6d 65 64 65 \...%.smb://mede
    18:32:27 : 00007266: javi : 0x0042a7e4 61 2f 44 72 69 76 65 20 43 20 66
    6f 72 20 41 64 a/Drive C for Ad
    18:32:27 : 00007281: javi : 0x0042a7f4 6d 69 6e 69 73 74 72 61 74 6f 72
    00 00 00 00 01 ministrator.....
    18:32:27 : 00007281: javi : 0x0042a804 2c 00 00 00 14 00 59 57 52 74 61
    57 35 70 63 33 ,.....YWRtaW5pc3
    18:32:27 : 00007297: javi : 0x0042a814 51 35 4d 44 41 33 4f 44 45 3d 14
    00 55 6b 64 42 Q5MDA3ODE=..UkdB
    18:32:27 : 00007297: javi : 0x0042a824 50 54 4a 57 55 44 59 77 4d 43 73
    79 57 53 45 3d PTJWUDYwMCsyWSE=
    18:32:27 : 00007313: javi : 0x0042a834 14 00 00 00 05 00 00 00 08 00 01
    00 56 03 00 00 ............V...
    18:32:27 : 00007313: javi : 0x0042a844 00 02 00 00 00 00 00 00 00 00 00
    00 00 00 00 00
    18:32:27 : 00007328: javi : TTDMServer::process messagecode 0 deviceid 17
    Carmelo wrote:
    Javier,
    What version of Tarantella are you running? The reason I ask, is that
    since v3.30 you also need to run
         $ tarantella start cdm
    Also see
    http://www.tarantella.com/documentation/sgd/ee/3.42/help/en-us/base/standard/cdm.html
    >>
    >>
    Regards,
    Javier wrote:
    We have changed the server of linux that supports tarantella. We have
    installed tarantella on redhat 8 and worked perfectly. I have installed
    the tarantella enhancement module for windows and activated in the array
    manager the option " let users access client drives " but on having
    entered the session of windows not does not appear the local hard disks.
    There is something more than I have to do in order that me it works? Thank
    you for yours help
    If you are using WINS the problem appears to be one of WINS name mapping.
    Check if the Tarantella server is not on the same subnet as the Windows
    Terminal Server that you
    are using to run your Windows applications.
    You need to add the Tarantella server to each of the Windows Terminal
    Servers as a WINS server.
    After that you may need to restart the Windows terminal Server.
    Hope it helps.
    Regards,
    Gonzalo

  • Network drive mapping Issue in WINDOWS 8 Client

    HI,<o:p></o:p>
    We have 2 Win2k8 R2 Domain controller. & around 100 Windows XP & Windows 7 Client. All the network mapping which was mapped through Group policy
    is worked fine.<o:p></o:p>
    Recently we have added 5 machines of WINDOWS 8 Client in our Network. We have observed that in none of the Windows 8 client machines,  Network drives are not
    getting automatically mapped. I checked through Gpresulr/r to confirm that whether the policy get applied or not, All the Windows 8 client machines has GP Applied.<o:p></o:p>
    I have run gpupdate & restart the machine, I have slow the network logging of Windows 8 Client,but it couldn't help me.
    <o:p>Regards,</o:p>
    <o:p>Chetan</o:p>

    Hi,
    In Group Policy Preferences,is "Reconnect" option ticked? If yes, please un-tick this option and check the result. Meanwhile, please check the below post which is discussing the same problem in Windows 8.
    Group Policy Preferences Drive Maps Not Working in Windows 8 RTM When "Reconnect" Option is Active
    http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/64e01325-9b2f-477c-ab51-7b10692b583a
    If this post does not help solve the problem, I suggest you ask in Group Policy forum.

  • Drive Map to DFS Folder Getting Lost

    We had a problem yesterday morning with every user (about a dozen) in one of our small branch offices being unable to access a certain network share.
    Their T: drive, which is the one they had a problem with, is mapped to this:
    \\domain.com\namespace\OfficeShare1
    which is a DFS folder that simply points to:
    \\2012FileServer\OfficeShare1
    That is a Server 2012 R2 server.
    This share is only a few weeks old, and has been working fine for them until today. We have other offices that have their own shares on the same server, and mapped to a DFS folder the same way, and those have been working OK (as far as I know).
    The PCs are all running Windows 7.
    Their S: drive is mapped to
    \\2003FileServer\CompanyShare
    which is a MS Server 2003 server. They had no problems with accessing this, ever.
    Going to Computer > Map network drive, I could see the label for \OfficeShare1 was still attached to T:, but the path was empty. The T: drive appeared in the Computer window, but was showing as disconnected, and double-clicking it would throw an error about
    the path being unavailable.
    Typing \\domain.com\namespace\OfficeShare1 in the address bar would cause the Computer window to hang before erroring-out. Thus, re-creating the drive map would not work.
    After trying that, a user could go to \\domain.com\namespace and that would work fine. From there, they could go to the \OfficeShare1 folder without any errors.
    If they then went back into Computer, their T: drive would again be working, without having to re-create the mapping.
    Also, even though users couldn't browse directly to \\domain.com\namespace\OfficeShare1,without first browsing \\domain.com\namespace, they could browse directly to \\2012FileServer\OfficeShare1.
    I've seen a few other users outside the aforementioned office who had the issue, but this is the first opportunity I've had to get more information on it before the client PC was rebooted. Some of those users who have had this issue, also have an X: drive,
    which is mapped to:
    \\domain.com\namespace\DeptShare1
    But this is a CIFS share. And like the share on the 2003 server, no user has experienced the issue with this share.
    It has only happened with the shares on the Server 2012 system. And it has been kinda rare (currently less than 75 users who could potentially experience it).
    All drives are mapped via Group Policy. Users do have a script they can run to re-create drive maps.
    It's probably some connectivity issue that causes the drive to get disconnected (wifi signal drops, VPN gets disconnected, etc). But I'm not sure why the problem persists after connectivity is restored, why the path disappears from the mapping, and why only
    with this one drive. The servers hosting those shares are all in the same subnet, same data center.
    I'm about to migrate about a share accessed by 500 users to this 2012 system, and I can't until I get this figured out. My hunch is that something in the Windows 7 client PC is getting... lost. It's only happening to drives that map to DFS folders in that namespace
    that point to shares on that 2012 server (no one has a drive that maps directly to the shares on that server). The share itself doesn't appear  to actually go offline or anything like that. And this morning is the first time I've seen it happen to multiple
    people at once.
    Weird.
    Any help is appreciated.
    Thanks!

    Hi,
    Is there any error message in the Event Log? Do you add more than one namespace server in the DFS namespace? Since the server hangs when you access the DFS link, you could refer to the article below to establish connectivity with the target computer and shared
    folder.
    Troubleshooting Dfs Problems
    http://technet.microsoft.com/en-us/library/cc962144.aspx
    Best Regards,
    Mandy
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Creating a new folder and drive map with Preferences

    So I am trying to set things up using GPP so that users of a particular security group get a U:\ drive at the following location:
    \\server\share\%username%
    I have set up the drive map preference & also a folders preference (to create the user's folder).  The problem is that it works BACKWARDS and the drive tries to map prior to folder creation and thus fails, THEN the folder gets created.  So
    that the 2nd time the user logs in they actually get the U:\ drive at the correct location.  The goal is to have the folder created and mapped to on the 1st try for the user.
    How can I get this working WITHOUT resorting to scripts, folder redirection, or manually setting the U drive on the AD Profile?  I just want that folder to be created for only users in the proper security group, and then have the drive map
    to it.
    # When I wrote this script only God and I knew what I was doing. # Now, only God Knows!

    > How can I get this working WITHOUT resorting to scripts, folder
    > redirection, or manually setting the U drive on the AD Profile?  I just
    > want that folder to be created for only users in the proper security
    > group, and then have the drive map to it.
    You cannot. The execution order of GPO parts (called Client Side
    Extensions) cannot be changed, so you're stuck with this error if you
    don't resort to a script :)
    Greetings/Grüße,
    Martin
    Mal ein
    gutes Buch über GPOs lesen?
    Good or bad GPOs? - my blog…
    And if IT bothers me -
    coke bottle design refreshment (-:

  • Drives mapped via GPO, NET USE shows mapping but doesn't show up in Explorer - Win 8.1

    Fresh install of Windows Enterprise 8.1
    Connected PC to domain, logged in, drive mapping worked as it should.
    Rebooted a few times after installing software that I normally install on my computers (from the same sources/locally from my file server, etc).  Rebooted a few more times all is well.
    A few reboots later, the only drive that is mapped is X: which is my user drive done via the user profile in AD.  The rest of the mappings that normally show up done by the GPO no longer show up.
    After some digging, and noticing no errors in any logs I ran NET USE in a CMD prompt window, low and behold the drives are actually mapped and I can access them via the CLI without issue.  I can navigate via their mapped drive letters, etc.
    They just don't show up in Windows Explorer at all and I cannot navigate to the drive letters via the address bar.  Strangely enough, it still kinda works since the Downloads start menu item is mapped to a network drive and that still works (Q:\) and
    Chrome can access it as well if I try to download something.
    I'm really not sure what else to check/try here. 
    Have other Windows 7 and Windows 8.1 machines (my laptop) and all works just fine, so it's only this specific install on my desktop that is showing this issue.

    Hi,
    There are several reasons causing the issue:
    First, The problematic client doesn't reconnect to the target share at logon. 
    Please follow the steps to re-configure the mapped driver on the client and then check if the issue will re-occur.
    Steps:
    a. Open "My Computer"
    b. Click on "Tools" and then select "Map Network Driver"
    c. input the \\ipaddressofserver\sharename to give the path of the share
    d. Check "Reconnect at logon"
    e. Drive gets mapped
    f. Double click on the drive to check.
    Second, Antivirus software or Windows Firewall may block the mapped share.
    If there is any Antivirus software and the Windows Firewall is enabled on the problematic client. If so, please disable them to check if the issue can be resolved.
    Third, Fast Logon Optimization is enabled on the clients.
    The fast logon feature may affect the display and drive letter assignment of a mapped network drive. As a result, the drive may have been mapped; however, the user on client cannot see it in Windows Explorer. He may recognize it as a failed network drive
    mapping. This is the reason why we usually suggest you to disable fast logon on the clients via a GPO, and please check if the mapped network drive will be occur under this circumstance.
    Please also configure the following group policy setting to disable Fast Logon Optimization to see if the issue still exists on the problematic clients.
    Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon
    If we cannot get this issue fixed, please post back the event log related to this issue.
    Kate Li
    TechNet Community Support

  • Group Policy error 1112 - Drive Maps

    Hi everyone
    We are getting hundreds of these alerts from SCOM every day from multiple 2008 R2 terminal servers:
    Alert from Operations Manager 2007:
    Alert description: The Group Policy Client Side Extension Group Policy Drive Maps was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish
    completely before the next startup or logon for this user, and this may result in slow startup and boot performance.
    Looking on the Server itself in the System log I see these entries for every time a user logs onto the server (via RemoteApp)
    Log Name:      System
    Source:        Microsoft-Windows-GroupPolicy
    Date:          15/03/2012 2:23:58 p.m.
    Event ID:      1112
    Task Category: None
    Level:         Warning
    Keywords:      
    User:          HOT\xxxxxx
    Computer:      HOTAKLRD01.hot.co.nz
    Description:
    The Group Policy Client Side Extension Group Policy Drive Maps was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the
    next startup or logon for this user, and this may result in slow startup and boot performance.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
        <EventID>1112</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>1</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2012-03-15T01:23:58.350306600Z" />
        <EventRecordID>57243</EventRecordID>
        <Correlation ActivityID="{651EFA61-7FA8-4444-9E68-81D0F82DEFE4}" />
        <Execution ProcessID="900" ThreadID="22780" />
        <Channel>System</Channel>
        <Computer>HOTAKLRD01.hot.co.nz</Computer>
        <Security UserID="S-1-5-21-1288906317-135625827-1544898942-500" />
      </System>
      <EventData>
        <Data Name="SupportInfo1">1</Data>
        <Data Name="SupportInfo2">3961</Data>
        <Data Name="ProcessingMode">1</Data>
        <Data Name="ProcessingTimeInMilliseconds">4656</Data>
        <Data Name="ErrorCode">1274</Data>
        <Data Name="ErrorDescription">The group policy framework should call the extension in the synchronous foreground policy refresh. </Data>
        <Data Name="DCName">\\HOTAKL31.hot.co.nz</Data>
        <Data Name="ExtensionName">Group Policy Drive Maps</Data>
        <Data Name="ExtensionId">{5794DAFD-BE60-433f-88A2-1A31939AC01F}</Data>
      </EventData>
    </Event>
    However it each case the user still gets their drive mapping!
    I've this only occurs with Drive Map GP Preference -I've even taken a user out of all policies except for a new test drive map policy and they still get this error. I've applied the hotfix that should be the latest version of the GP dll's (KB2622802) but
    the error remains. I've tried all options within the GPP for Drive Maps - Update, Replace etc, 
    Should I just override the OpsMgr alerts? It seems like this is a bug with 2008 server and GP Drive Map Preferences?
    Any ideas would be appreciated
    Thanks
    Rik

    > *"Note: For servers, the startup and logon processing always behaves
    > as if this policy setting is enabled."*
    >
    > **
    >
    > **
    >
    > **
    >
    > **
    >
    > **
    >
    I must admit that I never used Drive Maps on a Server (-: Maybe this is
    a bug in the Drive Maps CSE... If it bothers: Set NoBackgroundPolicy 
    (REG_DWORD) to 1 in HKLM\Software\Microsoft\Windows
    NT\CurrentVersion\WinLogon\GPExtensions\
    {5794DAFD-BE60-433f-88A2-1A31939AC01F}. This will prevent the Drive Maps
    CSE from being invoked during background GP updates.
     sincerely, martin
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!

  • Drive mapping during posture remediation

    I am doing ISE (1.1.1) deployment for client. The customer is using AD logon script do do drive map to a nas server. My posture remediation acl is blocking drive mapping unless I use 'permit ip any any' which is a security hole. My acl should be modified to allow the drive mapping during unknown/posture-remediation interval. Could any one suggest if you have faced similar issue.

    You need to permit access to your domain controllers during posture remediation and add a delay to your logon script -
    http://www.cisco.com/en/US/products/ps6128/products_configuration_example09186a0080a70c18.shtml

  • Looking for clarification on network latency issue vs drive mapping

    Hi,
    I am seeing this as mystery and not getting crystal clear idea on the reason for the issue. Issue is related to the performance of the application interms of time it is taking in processing the input file.
    I wrote a swing application, which is a client application. Which takes some parameters like server name and iphostaddress and connects to the Process Server which is, responsible for processing client application requests. Client application will communicate with process server through TCP/IP connection and process the input file and returns the decisions back to the user through the output file.
    Below is the scenarios I am using for launching the application:
    1. If both client application and server are running locally in my desktop the time it is taking to process the input file is 2 minutes.
    2. If client is running my application and server is running remotely on wondows server, it's taking 13 minutes to process same input file.
    3. To reduce the time in scenario2, I installed the client appliation also on the remote server ( so that both client and server application are running on the windows server). and mapped the server's share drive to my desktop. And launched the application from my desktop (from U drive, where application is mapped), now it's taking 10 minutes to process the same input file.
    I am struggling in understanding why it's taking that long in scenario 3. Because application is installed locally on the server and input file and output files also copied onto the U drive. Sometimes thinking am I launching the application in the right way or not?
    Can somebody explain me, if we launch the remote java application through drive mapping will there be network latency there eventhough everything is there on the server (U drive)? Here I need to tell one more scenario 4, If loginto the remote windows server and launch the client application time it's taking to process the same input file is about a minute.
    Below are some more details on the issue: I am not encoding the file, I am using third party application, which provides an API to communicate with the process server. Just using the API methods and classes to pass the input file data to server. I have used the 'tracert' command for the remote server and I am seeing 8 hops between my desktop and remote server. I even installed network sniffer tool in my laptop and captured the files when application running.
    The input file has 140000 records (text lines with comma delimited) of 6.271MB in size. I have posted to understand the time it is taking in scenario3, where evrything is on mapped drive (i.e, client application and input file are technically recides on the server right?) , but client application is launched from desktop. The reason I am doing this way is, instead of log-in into the remote server, user can easily launch the application from the desktop. So, when I try to launch the application this way, this doesn't count as if client application is running local to the server? Will it becomes remote (I have even captured the network traffic file in this scenario too, and I have seen the comminication between my desktop ip address to server ip address and server is taking abour 3.84 milliseconds for each item to respond to client, I think it's just travel time not the process time). I am assuming, even when application launched from drive that is mapped, it should take about 1 minute (the time taking when I launch the aplication after log-into the server,not through drive mapping) to prcess input file as everything is on the server.
    Thanks in advance,
    Jyothi

    reading and writing the data shouldn't be the problem, its what you are doing with the data which will be taking all the time.
    Try this
    public class WriteFile {
        public static void main(String... args) throws IOException {
            String filename = "record.csv";
            int records = 140 * 1000;
            int values = 6;
                long start = System.nanoTime();
                PrintWriter pw = new PrintWriter(new BufferedWriter(new FileWriter(filename)));
                for (int r = 0; r < records; r++) {
                    for (int i = 0; i < values; i++) {
                        if (i > 0)
                            pw.print(',');
                        pw.print(r * 10 + i);
                    pw.println();
                pw.close();
                long time = System.nanoTime() - start;
                System.out.printf("Time to write %,d records was %.3f sec. file size=%.3fMB%n",
                        records, time / 1e9, new File(filename).length() / 1e6);
                long start = System.nanoTime();
                BufferedReader br = new BufferedReader(new FileReader(filename));
                String line;
                while ((line = br.readLine()) != null) {
                    // do some work.
                    String[] parts = line.split(",");
                    int[] nums = new int[parts.length];
                    for (int i = 0; i < parts.length; i++)
                        nums[i] = Integer.parseInt(parts);
    br.close();
    long time = System.nanoTime() - start;
    System.out.printf("Time to read %,d records was %.3f sec%n",
    records, time / 1e9);
    PrintsTime to write 140,000 records was 0.462 sec. file size=6.193MB
    Time to read 140,000 records was 0.792 sec

  • Erratic drive mapping - Vlan assignment

    Hello all,
    We are having issues with inconsistent drive mapping after vlan change. The client computers (running Windows 7) first authenticate against our NPS server (using mac authentication bypass), and are then placed in vlan 10. After the users log in, they are
    placed into a different vlan based on user's AD group membership. The actual vlan switch works fine, and the users always end up in the right vlan. The drives, however, aren't always there. The user's home drive is mapped via the Home Folder in the users'
    properties in AD, and the rest of the drives (staff data, etc.) are mapped via a log on script. Drives mapped via GP are almost always mapped, but drives mapped via AD properties are missing much more often. All of the drives can be manually accessed from
    all of the vlans. There are no errors on the NPS side, and the only errors I can see in the event viewer are DHCPNack messages (The IP address lease 10.42.13.xx for the Network Card with network address 0x has been denied by the DHCP server 10.42.10.xx). Does
    anyone have any advice or a possible solution? Any info would be much appreciated.
    Here's how authentication is set up locally:
    Cache user information for subsequent connections to this network
    Enabled
    Authentication Mode
    User authentication
    Maximum Authentication Failures
    2
    Maximum EAPOL-Start Messages Sent
    Not setup
    Held Period (seconds)
    Not setup
    Start Period (seconds)
    Not setup
    Authentication Period (seconds)
    Not setup
    Single Sign On
    Before user logon
    Maximum acceptable delay for network connectivity
    10
    This network uses different VLAN for authentication with machine and user credentials
      is enabled
    Allow additional dialogs during single sign on is disabled
    Fast Reconnect is disabled
    Authentication method is PEAP-MSCHAP V2
    Thank you,
    Nikita

    Hi,
    When an interface changes VLANs, line protocol goes down for a moment then comes back up again. It is similar to physically disconnecting the interface for a very short time. Your problem might be caused by the interface being down for this short period
    of time, because this is when the home drives are being mapped, but I'm not sure.
    If the GP mappings are almost always working, why not do everything there and dispense with the home drive mapping?
    You can also try setting Computer Configuration ->
    Administrative Templates -> System ->  Logon -> Always wait for the network at computer startup and logon to
    Enabled and see if this helps.
    -Greg

  • Network Drive Mapping for users who have Port 445 (possibly others) Blocked by their ISP to a Server 2008 system

    Nice to see my original posts are still up.  I was hoping that in the ensuing time someone had found a solution.  At least I can now see many other posting the same problems.  :)  Thought I was losing it for a while.
    We have 100% proven that the problem (in our case) is from the ISP blocking port 445 (possibly others but 445 for SURE) with the reasoning that it prevents the spread of some Internet "worms".  It also just happens to prevent people who work
    from home from being able to map to their network drives at work.
    What I was hoping was that eventually someone would comer up with a solution for this short of having to load a server using a different OS from Windows.  The SMB protocol is the one needing port 445 as far as I can tell.  Not all ISP block
    port 445 and the laptops that use those ISP's  have no problem.  Unless they travel.  Then it is "hit or miss" as to whether the ISP for the Hotel they stay at blocks it.
    I have run multiple tests to prove that this was in FACT the problem.  Even the particular ISP in question which is a very large national ISP company freely admits they do this supposedly to prevent the spread of an unnamed Internet Worm.  It also
    happens to prevent Business use of their Internet by Home Subscribers at they cannot map to their Business Servers which also need port 445 to map.
    I have used WebDAV successfully to get around this but at a huge loss of speed and performance.  Cloud services all do essentially the same thing and all have pretty much the same loss of speed.
    If anyone has come across a method of allowing a drive mapping to be rerouted to any other port, that is the only hope I have short of changing to an alternate OS for the Office Server and even then I cant be sure until I try if it would help.  I read
    somewhere about the possibility of routing through a proxy but again, the problem would still be that the requests for mapping are expected on port 445 on the server and they will not get through even to the proxy since the originating ISP is the one blocking
    the port from the User's system. 
    Any help or suggestions would be greatly appreciated  I have posted this question now for several years with no one yet providing a working solution.  Hope burns Eternal though :)

    Yes, OwnCloud is an option as well as many others.  Even self hosted Cloud services such as the WD MyCloud all work.  The problem is speed.  JungleDisk is the best I have found so far.  I am not sure exactly what they use to allow the
    drive mapping but it seems to work faster that anything else I have found.
    VPN's don't work.  At least none of them I have tried.   I can connect a VPN with no problem.  But still cannot map a drive over it.   Actually, there are some issues with the VPN as well but these are just a matter of methodology. 
    Mapping to the FQDN works for some people while others require the public IP.  Some users on some ISP's can map using the FQDN, others have to map to the IP.  That in itself was a bit odd.
    I have tried every trick I could find including adding  the IP and/or FQDN to the Windows Hosts file on the server as well as on the client systems.  This actually did help to get the VPN to connect in some cases.  However, it still would
    not allow me to map a drive letter.
    I can create a Network Place,  This also works.  But it will not allow me to MAP that "network place" to a drive letter.  I have tried multiple utilities that allow mapping of Drive letters to almost anything but they wont work to map to a
    Network Place.
    The software that needs the mapped drive is a SQL database which runs on port 2004.  The program itself has no problems at all connecting to the server to run the database.  Even on systems which cannot map to the needed drive letter for the documents
    referred to in the database.    Users can run it and look up all kinds of material but it it is only a half-solution since the database refers to files stored in a "common-mapped" drive letter.  Which I cannot Map.
    I have tried every possible configuration of the VPN setup I could find, I have even tried a "Test System" with the NIC connected directly to the T1 Modem.  With all firewalls off and no AV software.  Even if that had worked,  there is no
    way I could run like that.  But it didn't.  Same issues.  All this did was put the blame squarely on the User's ISP which was the only reason I did it.  I had to rule out even the slightest chance that it was something in our equipment.
    This was already almost a certain fact since the same user could take their laptop to a WiFi Hotspot at a fast food restaurant and connect as well as map the drive.  As soon as they went back home, no drive.  On the ones I could convince to pay
    the extra charges, if they switched to a business connection from their ISP, No Problems.
    On most MiFi or other Cellular Internet devices, No Problem,  Although that had a habit of changing.  We had a few that worked for a while, then they got a software update for their MiFi which immediately blocked the ability to map.  Others
    it would be that some models of Cellular HotSpot units worked while other would not work even if both came from the same carrier.
    Coincidentally, we had none of these problems before two other events occurred: 
    One was the release of Server 2008 R2, (which was a kid of "surprise" change for all of us used to Server 2008 R1.  Welcomed changes, but not expected with a simple SP release. 
    The other was IPV6 finally became a reality:  June of 2012.
    This left us with much head scratching as to what was the real cause of the problem.  It took months to narrow it down to port blocking by the Outside ISP's with a 100% certainty.  Even tried reloading a system with Server 2008 R1 just to rule
    that out.  As well as disabling IPV6 on every network device.  The problem stayed with the User when Outside and which ISP they were connected to.
    Currently we are using a mix of normal VPNs for those who can run them, and CLOUD access for those who can't.  Even this is problematic since we have to keep both the local copy and the cloud copy in constant sync so that everyone sees the same versions
    of the same files on each one.
    Sorry to make this so long but I wanted to cover everything to show that we tried it all.  The only thing left short of getting the ISP's to remove the port blocks would be to find a way to route the SMB file requests around port 445 in some way. 
    I have been told that this is easy enough if using a file system other than Windows but that is not an option even if true. 
    Thanks for the updates and ideas.  I keep hoping that eventually there will be some secure method for mapping a drive letter that does not depend on having port 445.

Maybe you are looking for