New to profiling, I found JetBrains DotTrace as a recommendation by lot of developers. Started testing and ran successfully on Local Machine.
The problem I am facing right now is I am unable to use this for Remote Machine that is hosted on Windows Azure Server 2012. I have followed the instructions mentioned in their documentation provided but no help and getting error like
TCP Error Code 10060
Can anyone help me connect to remote server? Please help.
You need to open an end point in the Cloud Services and your Azure VM to allow the TCP connection from outside world to the DotTrace Remote Agent. One thing you have to remember is to use same port for External Port & Internal port and set it to the port that your RemoteAgent is listening on.
Related
I have just finished setting up Node-red on the a cloud machine hosted with vultr ( Ubuntu 20.04 x64 ) and I am wanting to be able to hit the Node-Red web page but I am failing to do so.
I have setup WireGuard so I can VPN into the machine
I am able to ping the servers Local IP address from my Windows PC
But I am still unable to hit the Node-Red Web Page
Even though Node-Red is running
I am fairly new to working with cloud machines so any help would be highly appreciated.
I'm going to guess that you haven't opened port 1880 for the server.
This could be in one of 2 places
Vultr appear to have their own firewall which you will need to ensure a suitable rule to allow TCP traffice on port 1880 exists. How to configure the firewall appears to be documented here https://www.vultr.com/docs/vultr-firewall-quickstart-guide/
You will need to make sure that the port is open in the Ubuntu Firewall as well. Running sudo ufw allow 1880/tcp should do this.
I have created a Web Service API console application in VS, for .NET 6, and specified the ports 6060 and 6061, where I want them to listen:
app.Urls.Add("http://localhost:6060");
app.Urls.Add("https://localhost:6061");
Deployed the application on Linux (Amazon Linux 2).
Then, went to the AWS management console added Outbound rules to open ports 6060 and 6061.
I can connect to ports 6060 and 6061 locally using Telnet, from the same Linux machine, but the ports 6060 and 6061 are still unaccessible from outside.
And, it is not a lag with exposing ports on AWS, because if I run another service on those ports, I CAN connect to them. They are open.
Must be missing something simple and obvious. Did anyone else experience the same problem?
Thanks
Archie
Yes! The suggestion from Lei Yang to change the localhost to 0.0.0. worked! Thank you very much!
I recently wrote an echoserver / echoclient program in C for the online class I'm taking (Graduate Introduction to Operating Systems, here). I was able to complete it with the help of (and modification from Beej's Network guide (here). I can run it just fine on my Ubuntu 20.04 virtual machine, running on my Windows 10 laptop. However, I'm trying to run the echoserver on an AWS Linux instance and the echoclient from the Ubuntu VM, as my end goal is building a client program that has a central server data repository. However, I'm running into issues where I start the echoserver C code on the AWS EC2 instance through SSH-ing by PuTTy, then I run the echoclient on the Ubuntu VM, but it can't connect (the error I receive on the client side is that it failed the connect phase of the socket call). I've tried the following steps:
Editing the inbound rules of the security configuration of the EC2 instance to allow for 'All TCP' connections from the IP address that comes up when I run curl ifconfig.me on my Ubuntu machine
Changing the network setting of my Ubuntu VM from NAT to Bridged Network
Testing port access by telnet <AWS Public IP> <PortNo> - which led to "Connection Refused" error
Ensuring that my outgoing ports aren't blocked by following these instructions
I've looked through the AWS pages (here) as well as multiple developer / SO threads (best one I found so far here) and I just can't seem to figure out out. If anyone could help me out, I'd really appreciate it. I'm happy to post my server & client code if that would be of help.
Figured it out: was missing the following line of code in my server.
hints.ai_flags = AI_PASSIVE;
I have set up SAMBA to act as an AD DC and my machine connects to it fine but when I try to find the Active Directory tools from inside my windows machine I get the error 'naming information cannot be located because: the rpc server is unavailable'
I have no idea what thats bout and the few cases ive seen online deal in different situation not applicable to my case.
The problem can be on either the client or server machine.
Make sure Samba is listening on the right ports. RPC is on port 135. If you don't see Samba listening on port 135, then that's your problem.
Also make sure that, on your client Windows machine, the "TCP/IP NetBIOS Helper" service is running (in services.msc) and set to run automatically. If that was not running, then that's your problem.
I am working on a project and am attempting to run a FTP daemon on an azure vm running the Technical Preview 2. The Daemon reports that it is behind a NATed router, and as such I can not connect in via another means but the remote desktop connection. (I will be running other daemons on this server as well, and they also have this problem)
I need some way to access this router that my Azure server is behind to configure it to allow for the range of ports that i need to access.
The fine folks at MVA instructed me to ask here, so here I am.
I think you just need to open the port (endpoint setting in the portal) to the virtual machine, so check this article out.
Also, make sure the local firewall isn't blocking that ftp port... I'm pretty sure it's off by default.