Ошибка 1202 невозможно подключить сетевой диск

[{«Product»:{«code»:»SSSH27″,»label»:»Rational ClearCase»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»View: Dynamic»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»7.0.1.1;7.0.1;7.0.0.2;7.0.0.1;7.0;2003.06.16;2003.06.00″,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}},{«Product»:{«code»:»SSSH27″,»label»:»Rational ClearCase»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»MVFS»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]

Я только что обновил свой компьютер с Windows 10 до Обновления 1607 (Anniversary Update). Теперь я получаю ошибку в заголовке при выполнении следующих действий:

1. Из командной строки cmd: runas /user:contoso\mwolfe /netonly cmd
2. Из этого нового окна cmd: net use g: \\fs\Sales
3. Из нового приглашения cmd: runas /user:contoso\mwolfe /netonly cmd
4. Из этого второго нового окна cmd: net use g: \\fs\Operations
   • Это приводит к следующему выводу:
     

     Произошла системная ошибка 1202.

     Имя локального устройства имеет запомненное соединение с другим сетевым ресурсом.

Это работает для меня в течение многих лет (начиная с Windows 7) и для Windows 10 до обновления 1511. После установки обновления 1607 он теперь не работает. Это ошибка в обновлении Windows или мне нужно использовать обходной путь?

Перейти к контенту

mount -o anon 2.168.1.103cube6Films Z:

% cat /etc/exports                                                                                         ~
# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#

/video  192.168.0.0/16(rw,root_squash,subtree_check,crossmnt)
% showmount -e localhost                                                                             
Export list for localhost:
/video 192.168.0.0/16

% nfsstat -s                                                                                          ~
Server rpc stats:
calls      badcalls   badauth    badclnt    xdrcall
4571165    0          0          0          0

Server nfs v3:
null         getattr      setattr      lookup       access       readlink
2         0% 8070      0% 0         0% 439       0% 2408      0% 0         0%
read         write        create       mkdir        symlink      mknod
4469992  97% 57711     1% 2         0% 0         0% 0         0% 0         0%
remove       rmdir        rename       link         readdir      readdirplus
30        0% 1         0% 0         0% 0         0% 0         0% 403       0%
fsstat       fsinfo       pathconf     commit
5         0% 2         0% 1         0% 32099     0%

% nfsstat -c                                                                                  ~
Client rpc stats:
calls      retrans    authrefrsh
72440      0          0

Client nfs v3:
null         getattr      setattr      lookup       access       readlink
0         0% 219       0% 0         0% 42        0% 72        0% 0         0%
read         write        create       mkdir        symlink      mknod
72097    99% 0         0% 0         0% 0         0% 0         0% 0         0%
remove       rmdir        rename       link         readdir      readdirplus
0         0% 0         0% 0         0% 0         0% 0         0% 6         0%
fsstat       fsinfo       pathconf     commit
0         0% 2         0% 1         0% 0         0%

[% id rabitsa
uid=526(rabitsa) gid=600(rabica) groups=600(rabica)

Event Details

Summary

The DFS Replication service failed to contact a domain controller to access configuration information. The service will try again during the next configuration polling cycle. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain
Services, or DNS issues.

Causes

DFS Replication failed to contact a domain controller to retrieve configuration information. If replication was working previously, the service will use cached configuration stored locally but will not respond to any configuration changes until the issue
is resolved.
This issue can be caused by the following factors:

• Basic network connectivity issues
• Firewall settings
• Active Directory Domain Services (AD DS) issues

Resolutions

• Test basic network connectivity
• Check Firewall settings

Test basic network connectivity

To test network connectivity with the affected server, use the following procedure:

1. Open a command prompt window and then use the ping command to check basic network connectivity.
   
   If the ping command fails, it is likely that the server is not running, or has network problems that require local access to resolve. If ping is blocked in your network environment, skip this step.
2. If the ping command is successful, test the server’s registration in DNS by using the
   nslookup command.
   If the nslookup command fails, there is a problem with DNS. Check the DNS server health or contact the DNS server administrator.
3. If the nslookup command succeeds, DNS is working properly.

Note: For more information about troubleshooting network issues, see
article 325487 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkid=46059).

Check Firewall settings

If a firewall has been configured between replication partners, ensure that it is not blocking RPC communication. DFS Replication depends on RPC for communication. DFS Replication uses the RPC Endpoint Mapper (port 135) and a randomly assigned
dynamic port in the range of 49152 through 65535 for Windows Server 2008 R2 and Windows Server 2008, or in the range of 1025 through 5000 for Windows Server 2003 R2.

You can use the Dfsrdiag command-line tool to specify a static port instead of the dynamic port. For more information about how to specify the RPC Endpoint Mapper, see
article 154596 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=73991). For more information about dynamic port usage in Windows Server 2008, see
article 929851 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=187092).

Verification

To test DFS Replication’s ability to communicate with AD DS, open a command prompt window and then type the following command:
Dfsrdiag pollad /verbose. The command should report Operation Succeeded. If not, there is a problem communicating with AD DS.

See Also

• DFS Replication Event 1202 (for Windows Server 2003 R2)