Difficulty accessing 1 remote desktop when connected with VPN

Hello world

I have an ASA 5505 and have a problem where when I connect via VPN, I can RDP into a server using its internal address but I can't RDP to another server using its internal address.

One that I can connect to a an IP of 192.168.2.10 and I can't connect to a a 192.168.2.11 on 3390 port IP address.

The two rules are configured exactly the same except for the IP addresses and I can't see why I can't connect to this server.

I am also able to connect to my camera system with an IP on port 37777 192.168.2.25 and able to ping any other device on the network internal.

I also tried ping he and Telnet to port 3390 without success.

Here is the config.

ASA 4,0000 Version 1

!

!

interface Ethernet0/0

switchport access vlan 3

!

interface Ethernet0/1

!

interface Ethernet0/2

switchport access vlan 2

!

interface Ethernet0/3

!

interface Ethernet0/4

!

interface Ethernet0/5

!

interface Ethernet0/6

!

interface Ethernet0/7

!

interface Vlan2

nameif inside

security-level 100

IP 192.168.2.2 255.255.255.0

!

interface Vlan3

nameif outside

security-level 0

10.1.1.1 IP address 255.255.255.0

!

passive FTP mode

clock timezone IS - 5

clock to summer time EDT recurring

network obj_any object

subnet 0.0.0.0 0.0.0.0

network of the OWTS-LAN-OUT object

10.1.1.10 range 10.1.1.49

network of the OWTS-LAN-IN object

Subnet 192.168.2.0 255.255.255.0

service of the RDP3389 object

service destination tcp 3389 eq

Description of DC

the object SERVER-IN network

host 192.168.2.10

network of the SERVER-OUT object

Home 10.1.1.50

network of the CAMERA-IN-TCP object

Home 192.168.2.25

network of the CAMERA-OUT object

Home 10.1.1.51

service object CAMERA-TCP

Service tcp destination eq 37777

the object SERVER-Virt-IN network

Home 192.168.2.11

network of the SERVER-Virt-OUT object

Home 10.1.1.52

service of the RDP3390 object

Service tcp destination eq 3390

Description of VS for Master

network of the CAMERA-IN-UDP object

Home 192.168.2.25

service object CAMERA-UDP

Service udp destination eq 37778

the object OWTS LAN OUT VPN network

subnet 10.1.1.128 255.255.255.128

the object SERVER-Virt-IN-VPN network

Home 192.168.2.11

the object SERVER-IN-VPN network

host 192.168.2.10

the object CAMERA-IN-VPN network

Home 192.168.2.25

object-group Protocol TCPUDP

object-protocol udp

object-tcp protocol

AnyConnect_Client_Local_Print deny ip extended access list a whole

AnyConnect_Client_Local_Print list extended access permit tcp any any eq lpd

Note AnyConnect_Client_Local_Print of access list IPP: Internet Printing Protocol

AnyConnect_Client_Local_Print list extended access permit tcp any any eq 631

print the access-list AnyConnect_Client_Local_Print Note Windows port

AnyConnect_Client_Local_Print list extended access permit tcp any any eq 9100

access-list AnyConnect_Client_Local_Print mDNS Note: multicast DNS protocol

AnyConnect_Client_Local_Print list extended access permit udp any host 224.0.0.251 eq 5353

AnyConnect_Client_Local_Print of access list LLMNR Note: link Local Multicast Name Resolution protocol

AnyConnect_Client_Local_Print list extended access permit udp any host 224.0.0.252 eq 5355

Note access list TCP/NetBIOS protocol AnyConnect_Client_Local_Print

AnyConnect_Client_Local_Print list extended access permit tcp any any eq 137

AnyConnect_Client_Local_Print list extended access udp allowed any any eq netbios-ns

implicit rule of access-list inside1_access_in Note: allow all traffic to less secure networks

inside1_access_in of access allowed any ip an extended list

outside_access_in list extended access allowed object RDP3389 any host 192.168.2.10

outside_access_in list extended access allowed object RDP3390 any host 192.168.2.11

outside_access_in list extended access allowed object CAMERA TCP any host 192.168.2.25

outside_access_in list extended access allowed object CAMERA UDP any host 192.168.2.25

pager lines 24

Enable logging

exploitation forest-size of the buffer 10240

asdm of logging of information

Within 1500 MTU

Outside 1500 MTU

local pool RAVPN 10.1.1.129 - 10.1.1.254 255.255.255.128 IP mask

no failover

ICMP unreachable rate-limit 1 burst-size 1

don't allow no asdm history

ARP timeout 14400

NAT static destination SERVER-IN-VPN SERVER-IN-VPN (indoor, outdoor) static source OWTS LAN OUT VPN OWTS-LAN-OUT-VPN

NAT static destination of CAMERA-IN-VPN VPN-IN-CAMERA (indoor, outdoor) static source OWTS LAN OUT VPN OWTS-LAN-OUT-VPN

NAT static destination of SERVER Virt-IN-VPN-SERVER-Virt-IN-VPN (indoor, outdoor) static source OWTS LAN OUT VPN OWTS-LAN-OUT-VPN

!

network of the OWTS-LAN-IN object

NAT dynamic interface (indoor, outdoor)

the object SERVER-IN network

NAT (inside, outside) Shared SERVER-OUT service tcp 3389 3389

network of the CAMERA-IN-TCP object

NAT (inside, outside) static CAMERA-OFF 37777 37777 tcp service

the object SERVER-Virt-IN network

NAT (inside, outside) Shared SERVER-Virt-OUT 3390 3390 tcp service

inside1_access_in access to the interface inside group

Access-group outside_access_in in interface outside

Route outside 0.0.0.0 0.0.0.0 10.1.1.2 1

Timeout xlate 03:00

Pat-xlate timeout 0:00:30

Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02

Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00

Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00

Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute

timeout tcp-proxy-reassembly 0:01:00

Floating conn timeout 0:00:00

dynamic-access-policy-registration DfltAccessPolicy

identity of the user by default-domain LOCAL

Enable http server

http 192.168.2.0 255.255.255.0 inside

No snmp server location

No snmp Server contact

Server enable SNMP traps snmp authentication linkup, linkdown warmstart of cold start

Crypto ipsec transform-set ikev1 ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac

Crypto ipsec transform-set ikev1 ESP-DES-SHA esp - esp-sha-hmac

Crypto ipsec transform-set ikev1 SHA-ESP-3DES esp-3des esp-sha-hmac

Crypto ipsec transform-set ikev1 esp ESP-DES-MD5-esp-md5-hmac

Crypto ipsec transform-set ikev1 ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac

Crypto ipsec transform-set ikev1 ESP-3DES-MD5-esp-3des esp-md5-hmac

Crypto ipsec transform-set ikev1 ESP-AES-256-SHA esp-aes-256 esp-sha-hmac

Crypto ipsec transform-set ikev1 ESP-AES-128-SHA aes - esp esp-sha-hmac

Crypto ipsec transform-set ikev1 ESP-AES-192-SHA esp-aes-192 esp-sha-hmac

Crypto ipsec transform-set ikev1 ESP-AES-128-MD5-esp - aes esp-md5-hmac

crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 pfs Group1 set

crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 define ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP

DES-SHA ESP-DES-MD5

outside_map card crypto 65535-isakmp dynamic ipsec SYSTEM_DEFAULT_CRYPTO_MAP

outside_map interface card crypto outside

Crypto ca trustpoint ASDM_TrustPoint0

Terminal registration

name of the object CN = SACTSGRO

Configure CRL

Crypto ikev1 allow outside

IKEv1 crypto policy 10

authentication crack

aes-256 encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 20

authentication rsa - sig

aes-256 encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 30

preshared authentication

aes-256 encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 40

authentication crack

aes-192 encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 50

authentication rsa - sig

aes-192 encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 60

preshared authentication

aes-192 encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 70

authentication crack

aes encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 80

authentication rsa - sig

aes encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 90

preshared authentication

aes encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 100

authentication crack

3des encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 110

authentication rsa - sig

3des encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 120

preshared authentication

3des encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 130

authentication crack

the Encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 140

authentication rsa - sig

the Encryption

sha hash

Group 2

life 86400

IKEv1 crypto policy 150

preshared authentication

the Encryption

sha hash

Group 2

life 86400

Telnet 192.168.2.0 255.255.255.0 inside

Telnet timeout 15

SSH 192.168.2.0 255.255.255.0 inside

SSH timeout 5

SSH version 2

SSH group dh-Group1-sha1 key exchange

Console timeout 15

dhcpd auto_config inside

!

a basic threat threat detection

statistical threat detection port

Statistical threat detection Protocol

Statistics-list of access threat detection

no statistical threat detection tcp-interception

WebVPN

username admin privilege 15 xxxxx encrypted password

attributes of user admin name

VPN-group-policy DfltGrpPolicy

type tunnel-group CTSGRA remote access

attributes global-tunnel-group CTSGRA

address RAVPN pool

IPSec-attributes tunnel-group CTSGRA

IKEv1 pre-shared-key *.

!

class-map inspection_default

match default-inspection-traffic

!

!

Policy-map global_policy

class inspection_default

inspect the icmp

!

global service-policy global_policy

context of prompt hostname

no remote anonymous reporting call

Cryptochecksum:0140431e7642742a856e91246356e6a2

: end

Thanks for your help

Ok

So, basically, you set up the router so that you can directly connect to the ASA using the Cisco VPN Client. And also, the goal was ultimately only allow traffic to the LAN through the VPN Client ONLY connection.

It seems to me to realize that you have only the following configurations of NAT

VPN Client NAT0 / free of NAT / identity NAT

the object of the LAN network

Subnet 192.168.2.0 255.255.255.0

network of the VPN-POOL object

subnet 10.1.1.128 255.255.255.128

NAT static destination LAN LAN (indoor, outdoor) static source VPN-VPN-POOL

The NAT configuration above is simply to tell the ASA who don't do any type of NAT when there is traffic between the network 192.168.2.0/24 LAN and VPN 10.1.1.128/25 pool. That way if you have additional hosts on the local network that needs to be connected to, you won't have to do any form of changes to the NAT configurations for customer VPN users. You simply to allow connections in the ACL list (explained further below)

Failure to PAT

object-group network by DEFAULT-PAT-SOURCE

object-network 192.168.2.0 255.255.255.0

NAT automatic interface after (indoor, outdoor) dynamic source by DEFAULT-PAT-SOURCE

This configuration is intended just to replace the previous rule of PAT dynamic on the SAA. I guess that your router will do the translation of the ASA "outside" IP address of the interface to the public IP address of routers and this configuration should allow normal use of the Internet from the local network.

I suggest you remove all other NAT configurations, before adding these.

Control of the VPN clients access to internal resources

Also, I assume that your current VPN client is configured as full Tunnel. In other words, it will tunnel all traffic to the VPN connection, so that its assets?

To control traffic from the VPN Client users, I would suggest that you do the following

  • Set up "no sysopt permit vpn connection"

    • This will change the ASA operation so that connections through a VPN connection NOT allowed by default in order to bypass the ACL 'outside' interface. So, after this change, you can allow connections you need in the 'outer' interface ACL.
  • Configure rules you need for connections from VPN clients to the "external" ACL interface. Although I guess they already exist as you connect there without the VPN also

I can't say this with 100% certainty, but it seems to me that the things above, you should get to the point where you can access internal resources ONLY after when you have connected to the ASA via the connection of the VPN client. Naturally take precautions like backups of configuration if you want to major configuration changes. If you manage remotely the ASA then you also also have the ability to configure a timer on the SAA, whereupon it recharges automatically. This could help in situations where a missconfiguration breaks you management connection and you don't have another way to connect remotely. Then the ASA would simply restart after that timer missed and also restart with the original configuration (as long as you did not record anything between the two)

Why you use a different port for the other devices RDP connection? I can understand it if its use through the Internet, but if the RDP connection would be used by the VPN Client only so I don't think that it is not necessary to manipulate the default port 3389 on the server or on the SAA.

Also of course if there is something on the side of real server preventing these connections then these configuration changes may not help at all.

Let me know if I understood something wrong

-Jouni

Tags: Cisco Security

Similar Questions

  • SE error message: the local policy of this system does not log in an interactive way, trying to access a remote desktop connection.

    Original title: the local policy of this system does ot allows you to open an interactive session

    I get this error message when you try to access a remote desktop connection.  The local policy of this system does ot allows you to open an interactive session

    Hi CamilleHolt,

    1. were you able to use the before remote desktop connection?

    You can try the following steps and check if it helps.

    a. Click Start, point to settings and then click Control Panel.

    b. double-click System and select the remote settings and then click the Remote tab.

    c. click Select users, and then add the name of the user account

    d. click Add and then click OK.

    Note: Adding users to the remote desktop group requires that you are connected via an administrator account.

    Hope this information is useful.

    Jeremy K
    Microsoft Answers Support Engineer.

  • Windows Server 2003 r2 64-bit Remote Desktop RDP connection does not

    Hello

    I went through most of the support guides I can find on the internet and nothing seems to work.

    I enabled and disabled the service. Enabled and disabled Internet connection sharing. I totally disabled the firewall on the server and I can not always connect to the server via RDP

    I only get an error message.

    Remote Desktop cannot connect to the remote computer to one of the following reasons:

    (1) remote access to the server is not enabled

    (2) the remote computer is disabled

    (3) the remote computer is not available on the network

    Make sure that the remote computer is on and connected to the network, and remote access is enabled.

    When should I wear analysis server there is no enabled 3389 port. I am using RDP just for administrative purposes. I used to connect to the machine via RDP but one day it just stopped working.

    I also checked a few updates selection to determine if they are installed. All updates that might have compatibility problems are not installed on the server.

    Any request for information will be answered promptly.

    Thanks in advance.

    Hello

    Please post your apparent in the following link for assistance with problems of desktop connection remotely:

    https://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?Forum=winserverTS

    I hope this helps.

  • Remote Desktop cannot connect to the remote computer

    Hi all

    I'm having a problem on my server running Windows Server 2008 R2.

    I can not can not on the remote server by using remote desktop (mstsc).

    Here is the error I get when connecting:

    Remote Desktop cannot connect to the remote computer to one of the following reasons:
    (1) remote access to the server is not enabled
    (2) the remote computer is disabled
    (3) the remote computer is not available on the network

    Make sure that the remote computer is on and connected to the network, and remote access is enabled.

    I tried to restart the services, but nothing helped.

    I even restarted the server, which did not help.

    Also, I can ping the server without any problem.

    Kindly help. !

    Hello

    Search logs events on the Terminal Server and the Local user's PC

    Try disabling the firewall - may have to be reconfigured.

    I suggest that repost you the question in the TechNet Windows Server forum for assistance.

    TechNet

  • Remote Desktop cannot connect to the remote computer to one of the following reasons:

    We are using Windows server 2003 sp2 & windows xp professional sp3. We want to connect to the server using Remote Desktop, but we get the following error:
    --------------------------------------------------------------------------------------------------------------------------------
    Remote Desktop cannot connect to the remote computer to one of the following reasons:
    (1) remote access to the server is not enabled
    (2) the remote computer is disabled
    (3) the remote computer is not available on the network

    Make sure that the remote computer is on and connected to the network, and remote access is enabled.
    --------------------------------------------------------------------------------------------------------------------------------
    We have enabled remote access on the server & the user is member of admin & users group to the remote desktop on the server. The firewall is turned on & exceptions for port 3389 remote desktop.

    Could you please help us on this.

    Hello

    Search logs events on the Terminal Server and the Local user's PC

    What is happening to all users?

    -If you get an error in the TS, then this is a client-side problem.

    -Take TCP Dump using wire shark and see who is the RST sendign package.

    Look for this error message in google that could give you light...!

    Kind regards

    Dhruv

  • error when connecting with SmartConnection inCopy

    Hello world

    I had to install Adobe inCopy for Clients in my workplace. After installing it, I use a SmartConnection and an installer of fix to this issue. She successfully for almost all customers except one, I still get the error when connecting with the SmartConnection. When I open the event logs, he said that it is related to public.dll plugin.

    I was installing it again and again and it's always the same error that pop up.

    The customer is a 64-bit Windows 7.

    inCopyerror.PNG

    Some help would be welcome.

    Best regards

    Problem solved

  • Equipment does not respond when connected with the desktop remotely

    Hello

    I have a PC with labview controlling a power supply via a serial connection. It works fine, except when I am looged in remote to my PC from another PC lab via desktop remotely. The VI runs correctly, but does not have the equipment to receive orders. Why would it be?

    Thank you

    Guillaume.

    If you have configured, the remote computer might try to use the serial port on the computer you're remot desktopping of.  Carefully go through the remote desktop settings and make sure that you are not telling the remote computer to use local ports.

  • Try to use remote desktop to connect to a computer in safe mode with networking

    I'm trying to troubleshoot a remotley pc on the network using remote desktop. I can connect properly, however, I want to continue to solve the problems with the pc remote in safe mode. When I choose to restart the pc in safe mode with network remote I am unable to connect to this computer by using remote desktop. Is there a certain config that I need to put in place inside msconfig which will restart in safe mode and I would still like access to connect to this computer by using remote desktop. Thank you.

    Hello

    @hoosier1077

    Assuming this isn't a general network problem (such as restarting changes to the local IP address on the remote computer).

    Maybe this can help.

    http://support.Microsoft.com/kb/315222

    http://support.Microsoft.com/kb/316434

  • REMOTE DESKTOP cannot connect home via VPN to WORK computer

    Hi all

    Having problems connecting to the PC of Office WORK PC using remote desktop.  Currently, I connect to the WORK PC to WORK laptop with no problems.

    Page HOME of PC is a Dell Dimension 4600 Windows XP, version of Microsoft Office Home, ATT, anti-virus Norton 360 Wireless internet service.  Work VPN up and running.  Set up my computer remote tab in order to allow the communication and remote AUTHORIZED Norton 360 desktop, I can PING my computer work fine.

    I run my VPN and connect to function properly the network but when I run the Remote Desktop application, I get "this computer cannot connect to the remote computer."

    I know that my work IP address and logon information is exact and know that my work computer is configured to allow remote access because I do this work laptop.  I do not understand why my home PC has a problem if the VPN works and I can PING my computer work fine.

    Any advice would be appreciated. I looked all over the internet and cannot find additional ideas.

    Use teamviewer, it is much easier to understand. And you can give the PC connecting to a fixed password youre. If you do not have to change.  Just install on both, give the youre one connecting a password fixed, then log in with the other

    Is XP Home or Pro? If it does not support his home desk remotely

  • Remote Desktop issues connecting from home to work the computer in Windows XP. Remote Desktop stops responding and eventually disconnects.

    Just around the beginning of July (2011) I started to have remote Office questions when connecting from home to work. If I minimize the connection for a while and come back later, it will be often does not. I'll have to hit the close X button several times before, he ends by abruptly disconnects. By the sudden I want to say that I don't get no dialogue usual warning that the session will be disconnected.

    Also, sometimes when I connect I get a white screen instead of a connection window.

    Anyone know if there was a Windows Update, or anything that can cause problems with RDP.

    I used to be able to connect perfectly without any problems.

    Thank you

    original title: Remote Desktop problems for the months spent on XP

    Hello

    Your question of Windows is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the public on the TechNet site. Please post your question in the below link: http://social.technet.microsoft.com/Forums/en-US/itproxpsp/threads

  • I am unable to remote desktop to connect to my laptop

    First of all, I looked through all the troubleshooting options on the microsoft page for troubleshooting remote desktop connection. None of these options worked for me. Even turning the firewall for my laptop worked. My laptop can remote access my office perfectly find it's just the reverse does not work.
    I think the problem is that I can't put my laptop to allow connections. My laptop home premium windows 7 don't have any remote desktop options in the "remote" of System Properties tab. I'm trying to access remotely to this laptop, but I am unable to probably for that reason. When I go to the Remote tab in system properties, all I see is a box for remote assistance and nothing on it as on my desktop, where it shows remote access options.
    Is there any solution for this?

    You have read obviously not what I wrote.

    I actually did, but obviously, you thought that the respondents have the x-ray vision. "You wrote" ""first of all, I looked through all the troubleshooting options on the microsoft page troubleshooting remote desktop connection ' , but then you did not designate one page you may have consulted.

    As long as illustrative, I would say that you did not know that Windows 7 Home Premium machines cannot be the target of a remote desktop session. You need at least the professional version.

  • XP Remote Desktop cannot connect to Windows 7: error 0xc00002fd

    I use Remote Desktop 6.1.7600 on Windows XP sp3 on two different computers and I am trying to connect to a Windows 7 machine on the same domain of one of them.  On the first machine to XP, I have several times a 0xC00002fd error "an authentication error has occurred" when you try to connect to the Windows 7 computer.  On the second XP machine I'm simply asked to password and user id several times.  On both XP machines I have activated CredSSP according to MS kb article 951608.  I'm an admin on the Windows 7 machine and uses my own credentials to connect.  This connection has worked in the past at least one of these XP machines and now all of a sudden it does not, or only intermittently.  Dr Mac OSX version seems to work perfectly.  This makes me wonder if there was an update on the XP side that makes CredSSP work correctly?

    Hi Bruce,.

    The question you have posted is related to the connection via the remote desktop of XP to Windows 7 computer on a domain network and would be better suited to the TechNet community. Please see the link below to find a community that will provide the support you want.

    http://social.technet.Microsoft.com/forums/en-us/category/w7itpro

    I hope this helps.

    Thank you and best regards,

    Srinivas R

    Microsoft technical support.

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • I can't access my remote desktop settings

    so, I recently tried to set up my remote desktop settings, but in my attempt, I came across a bone of sorts. When I tried to access the settings, I couldn't find even if it should have been there.

    This is where I got stuck (see photo) I do not know what causes this error, but it is quite confusing. If anyone of you has a solution for this problem I would be grateful for any help

    my system is a windows 7 Home premium (laptop) - if that makes a difference.

    Thank you very much.

    What version of Windows 7 you are using.  Remote Desktop is available in the Professional Edition, Ultimate or enterprise.

    To clarify this point a bit: only Windows 7 Professional can act as a remote host. Any Windows machine can use remote desktop to start a session on a host RDP.

  • BlackBerry Smartphones "Cannot access local files" error when syncing with Outlook

    I have an old BlackBerry Bold 9780 which works well. However, just yesterday, I started getting a "Cannot access local files" error when you try to use BB Desktop to synchronize with Microsoft Outlook 2016. I uninstalled and reinstalled the BlackBerry Desktop Software 7.1, but the problem persists. There is no error when using Outlook or other aspects of synchronization in BB Desktop.

    I am running 64-bit Windows 10 on my desktop computer. I got no synchronization issues in the past until yesterday. To my knowledge, nothing has changed.

    A Google search for the error message returns questions posted on several different forums, but there is no clear solution given.

    The problem seems to be in Outlook, rather than with the BlackBerry Desktop, at least in my case. I solved it by repairing my Microsoft Office installation. For most versions of Office, this is accomplished by going to the list of programs installed in the Control Panel, highlight and right-click on the desktop and select the option to repair or change.

  • BlackBerry Smartphones "Cannot access local files" error when syncing with Outlookl

    I have an old BlackBerry Bold 9780 which works well. However, just yesterday, I started getting a "Cannot access local files" error when you try to use BB Desktop to synchronize with Microsoft Outlook 2016. I uninstalled and reinstalled the BlackBerry Desktop Software 7.1, but the problem persists. There is no error when using Outlook or other aspects of synchronization in BB Desktop.

    I am running 64-bit Windows 10 on my desktop computer. I got no synchronization issues in the past until yesterday. To my knowledge, nothing has changed.

    A Google search for the error message returns questions posted on several different forums, but there is no clear solution given.

    The problem seems to be in Outlook, rather than with the BlackBerry Desktop, at least in my case. I solved it by repairing my Microsoft Office installation.  For most versions of Office, this is accomplished by going to the list of programs installed in the Control Panel, highlight and right-click on the desktop and select the option to repair or change.

Maybe you are looking for