Network PC World

I am using GNS3 VM and connecting to it remotely from my laptop. I was facing an issue where telnet to GNS3 routers/switches stopped working, though required router or switch was working properly and passing traffic but somehow it was disconnecting the telnet session. This issue happened when I directly close the telnet session,  or when my laptop is locked/logged off and upon re-connecting to GNS3 VM, I was unable to take console session to the router/switch until i restart the particular router/switch. Solution to this problem was to properly " exit the console session with cli command " and not closing the putty window directly. Or you can configure your router/switch for console timeout after some time. 

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore. I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option) All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world. The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address. After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started. 

If you planning to upgrade your graylog and want to see what your graylog current version is, here is how you can check it. Go to the Graylog Web Interface Click on System/Nodes Under System/Nodes --- Click on the N odes  Scroll down to the ' System ' Here you can see the current version of your graylog server

Graylog is restarting... There is no Graylog web application running at the moment, please reload this page in a minute. It can take up to 1-2 minutes until all services are running properly. In case this is a permanent error, check the following: Check if all services are running - sudo graylog-ctl status shows an overview of all running services Check for errors in log files - Relevant services write log files here: /var/log/graylog/*/current Ask for help - If there is no way to fix the issue ask for help: I got this error on my Gray-log server, upon troubleshooting I found that the disk was 100% full and was unable to start elastic search mongodb and etcd while checking gray-log server status with command #graylog-ctl status Solution to this problem was obvious that I have to clean some disk space to get gray-log working again but what file should I delete was my next thought! Upon googling I found that I could safely delete the old log files of elastic search to free

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

I got this issue with my iSCSI disk provided by Microsoft Windows Server. I am able to access the iSCSI datastore, all of my Virtual Machines are operational with any issue, my iSCSI datastore is showing as inactive but its status is showing normal. It happend after I had removed iSCSI targets from Windows but and added new target after some time. What I did; Rescanned all datastore multiple times --- no luck restarted management services from SSH of all ESXi hosts with command  $ services.sh restart --- no luck Removed and re-added targets from iSCSI (Windows) Side --- no luck Removed few VMs which were in inaccessible state and then rescanned datastore --- no luck Finally restarted each ESXi host at a time, it solved the problem.

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine. What worked for me, is 1. Uncheck the "Connected and Connect at power on" from Device Status. 2. Then Change the Device type from " Datastore ISO File to Client Device " Radio Button 3. and press OK to save the changes. Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui where it asks "The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?" You need to select yes to eject the CD-ROM and then remove the ISO file successfully.