Error Creating Listening Daemon
board cookies • All times are UTC Powered by phpBB Forum Software © phpBB Group
to work and connect Trouble getting RC to work and connect Post Reply Author Message Brew SysAider 4 Trouble getting RC to work and connect Feb. 04, 2010 01:08 PM I've been "fighting" with the remote control feature in sysaid for a few days. I've got the program installed and running. I then downloaded and installed SysAid administrator tools. When I go to my start menu, all programs, sysaid, and then deploy sysaid, the window pops up for me to select my users computers to intall the second peice on, but nothing happens from there. Now, Ill say this, in our agency, I have two user accounts. I have my regular user account and I have an Admin account. When I follow the steps above under my Admin account, it scans the network, shows http://forum.ultravnc.info/viewtopic.php?f=3&t=31695 me the computers and I deploy the tool to the end users computers, but I still cant remote in. If I then switch over to my regular account, I still cant log in. If I go to start, all programs, sysaid, sysaid remote control tool, I get a pop up saying: VNC Viewer error Error creating listening daemon; (Error creating flasher socket) Perhaps another VNC viewer is already running? Any ideas? Obelix SysAid Wiz 909 Trouble getting RC to work and connect https://www.sysaid.com/Sysforums/posts/list/3687.page Feb. 04, 2010 10:43 PM Well... have you follow up the error message ? Try changing the port no ? SBIT Super SysAider 78 Re:Trouble getting RC to work and connect Feb. 06, 2010 03:32 PM Hi Brew, The agents call back to the server (by the address you typed in when you deployed it), on port 4228 by default. You need to make sure the path from the remote PC to your admin PC on port 4228 is open. Check your firewall on the remote PC, check / configure your port forwarding on the router/firewall to your admin PC, open the port on your admin PC. Let me know if that helps. SBIT Super SysAider 78 Re:Trouble getting RC to work and connect Feb. 06, 2010 03:40 PM Also make sure your encryption settings match in the SysAid Remote Control screen (either checked or unchecked), with your Admin Tools... hover the mouse over the tray icon to see if it is encrypted or not. Brew SysAider 4 Re:Trouble getting RC to work and connect Feb. 08, 2010 08:13 AM Thanks for the input guys. Ill work on these "fixes" today. We actaully use port 2525 for our incoming and outgoing, as we dont use an SMTP server here. This may be the culprit. Ill get back to you all with any findings. itayH SysAid Customer Relations 1092 Re:Trouble getting RC to work and connect Feb. 11, 2010 10:34 AM Hi Brew, In o
Sign in Pricing Blog Support Search GitHub This repository Watch 266 Star 3,545 Fork https://github.com/docker/machine/issues/2366 959 docker/machine Code Issues 666 Pull requests 18 Projects 0 https://archive.realvnc.com/pipermail/vnc-list/2004-March/044345.html Wiki Pulse Graphs New issue Docker daemon does not start properly on DigitalOcean #2366 Closed lucj opened this Issue Nov 20, 2015 · 15 comments Projects None yet Labels area/swarm driver/digitalocean Milestone No milestone Assignees No one assigned error creating 6 participants lucj commented Nov 20, 2015 I use the following script to create a consul KV and a swarm (one master + one node) # KV Store docker-machine create \ --driver digitalocean \ --digitalocean-access-token ${TOKEN} \ --digitalocean-region "lon1" \ --digitalocean-size "1gb" \ consul eval "$(docker-machine env consul)" docker run error creating listening -d -p "8500:8500" -h "consul" progrium/consul -server -bootstrap sleep 5 # Swarm master docker-machine create \ --driver digitalocean \ --digitalocean-access-token ${TOKEN} \ --digitalocean-region "lon1" \ --digitalocean-size "1gb" \ --swarm --swarm-image="swarm" --swarm-master \ --swarm-discovery="consul://$(docker-machine ip consul):8500" \ --engine-opt="cluster-store=consul://$(docker-machine ip consul):8500" \ --engine-opt="cluster-advertise=eth1:2376" \ demo0 sleep 5 # Swarm node docker-machine create \ --driver digitalocean \ --digitalocean-access-token ${TOKEN} \ --digitalocean-region "lon1" \ --digitalocean-size "1gb" \ --swarm --swarm-image="swarm:1.0.0-rc2" \ --swarm-discovery="consul://$(docker-machine ip consul):8500" \ --engine-opt="cluster-store=consul://$(docker-machine ip consul):8500" \ --engine-opt="cluster-advertise=eth1:2376" \ demo1 Output while creating demo0 swarm master (same error when creating demo1 swarm node) Creating machine... (demo1) OUT | Creating SSH key... (demo1) OUT | Creating Digital Ocean droplet... (demo1) OUT | Waiting for IP address to be assigned to the Droplet... Waiting for machine to be running, this may take a few minutes... Machine is running, waiting for SSH to be available... Detecting operating system of created instance... Detecting the provisioner... Provisioning cr
following error when I try to start the viewer: VNC Viewer Error Error creating listening daemon (error binding daemon socket) Perhaps another VNC viewer is already running? No, another viewer is not running. Can someone explain what it means and what is the solution? Thanks. Shmuel =========================================== Shmuel Meyer Tel: 02-5862017 Meyer Services Fax: 02-5862695 "For All Your Computer Needs" Jerusalem, Israel e-mail: meyersrv "at" netvision.net.il http://meyersrv.tripod.com/computer.htm =========================================== Previous message: Automatic startup Next message: VNC Viewer Error Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]