Archive
Datto RMM Agent Browser lost in Chrome extensions
A few days ago I noticed that after some updates or whatever on my laptop, that the Agent Browser for Datto (Autotask) RMM wasn’t opening when trying to access a client’s machine. I could do the web access but anything requiring the Agent Browser to open, failed. Rather than uninstalling I dug into what was going on between a working machine and a non working machine. Plus found something on the web that described similar issue with other application.
Long story short, this is because the Agent Browser setting got lost in the Chrome Setting Preferences file. The file is located here:
c:\users\\appdata\local\google\chrome\user data\default\preferences
Look for Excluded_Schemes and if not found, add the information below back to the preferences file and save. then close out of Chrome and re-open. Thereafter when you want to connect to client’s desktop using the Agent Browser, it will be called upon.
Look for this area of preferences:
{“prompt_seed”:”3D27E4CC2D0E92F24A3C5968E9DBDADBE0EBA5B25796B65941263B9AA403604F”,”prompt_version”:”3DA0AEEA958AC953255D01DECEE8E9C6B22C092A3506B81E2C72B7BDEAFEF4A8″,”reporting”:”3B35D18EE559CA6ABF680C70EAC5575A6D243BEA86B122BC695E781FE07E12FC”}}},“protocol_handler”:{“excluded_schemes”:{“cag”:false,”gotoopener”:false,”teamviewer8″:false,”zoommtg”:false,”zoomrc”:false}},“session”:{“restore_on_startup”:4,”startup_urls”:
Add section in italics to the file, hit save and reopen chrome.
hope this helps MSP’s out there in need of this relief!
You cannot turn on Network Discovery in Network and Sharing Center in Windows Server
Assume that you try to turn on Network Discovery on a computer that is running any version of Windows Server. To do this, you change the Advanced sharing settings in Network and Sharing Center. However, the changes are not saved. Therefore, you cannot turn on Network Discovery, and you experience the following issues:
- You cannot browse or find any network share.
- You cannot view shared folders on a local network.
This issue occurs for one of the following reasons:
- The dependency services for Network Discovery are not running.
- The Windows firewall or other firewalls do not allow Network Discovery.
To resolve the issue, follow these steps:
- Make sure that the following dependency services are started:
- DNS Client
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
Configure the Windows firewall to allow Network Discovery. To do this, follow these steps:
- Open Control Panel, click System and Security, and then click Windows Firewall.
- In the left pane, click Allow an app or feature through Windows Firewall if you are running Windows Server 2012. Or, click Allow a program or feature through Windows Firewall if you are running Windows Server 2008 or Windows Server 2008 R2.
- Click Change settings. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
- Select Network discovery, and then click OK.
Configure other firewalls in the network to allow Network Discovery.
Turn on Network Discovery in Network and Sharing Center.
Adding or Changing Remote Desktop Listening Port
In supporting several clients with servers behind their firewall routers, I find that hiding the default RDP port 3389 is most beneficial in preventing remote attacks. The way I do this is to change or rather add another RDP-TCP listening port on servers and then add this port to the firewall rules. To connect to the server remotely, just use the command: mstsc /v:{remote dns name of server}:{Port Number} Normally you don’t have to add the :port number but since you’ve changed it or added it to the server, specifying it in the command will use that port for the RDP connection.
How to do this you ask. Well here’s a simple procedure:
1. Open up regedit on the server (or workstation as it works for them as well).
2. Browse under: HKLM\System\Currentcontrolset\control\Terminal Server\Winstations\
3. Under this Key, there is a key called RDP-TCP – this has all the setting information as found in the Terminal Server Configuration Console (tscc.msc).
4. Export this key to a text file or .reg file – I usually store it in the Documents folder.
5. Open the .reg file in Notepad editor and look for the line that says Port Number. The default value is 0x00000d3d which equates to 3389
6. Change this port number to another port number like say 25000 (in hex this will be 0x000061A8). Change the port to the new Hex value.
7. If you’re going to change the default listening port from 3389 to 25000, just save the reg file, then double-click to merge it into the registry. If though you’d rather just add this listening port (which I recommend) then make sure to change the name at the top where it has the full path to the RDP-TCP and just add a 2 (RDP-TCP2).
The Reg file the top line will look like this:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp2]
8. Save the reg file and then double click it to merge it into the registry. If you then open the tscc.msc console, you’ll now see two connections – one named RDP-TCP and RDP-TCP2.
9. Check to make sure the server is now listening on the secondary port by running this at the cmd prompt: netstat -an |findstr 25000 – If it returns with nothing, you might need to reboot the erver. If it still returns nothing then the import wasn’t successful.
10. Lastly, go to your firewall and direct port 25000 (TCP) from the outside to your server internally. Of course then test this remotely by either checking to see if the port is listening by using portqry (portqry -n -e 25000). If it returns listening then you’re in business! You can then connect to it using the syntax above.
Troubleshooting:
1. I recently had a customer where at some point the second port just wasn’t working anymore. To fix this, I opened up Tscc.msc and deleted both remote desktop connections. Also need to make sure to delete them from the registry as they do leave remnants which will prevent you from creating new ones on the server.
Note: If doing this remotely, make sure you have another means to connect to the server such as gotomypc or logmein clients installed, otherwise when you delete the RDP-TCP connection – you’ll lose your connection to the server as well.
2. After deleting both connections both in the console and in the registry, I went to the console and created a new default RDP-TCP connection – just follow all the prompts and pick the default settings.
3. Then go back and add the second RDP port from above and it should restore both the 3389 listening port as well as the 25000 one.
JVH Consulting's Blog 