Hello Seniors & all Members

Status
Not open for further replies.
@digital BD we are all representing our brand or own name here in the user ID. But when you say your name is also Bangladesh, that's why i laughed. Good to see you are someone representing your country here. Anyways i am from Bangladesh as well as @nahid133. But we both are badass not doing the same. Respect man and all the best for your new journey :). BTW don't call me sir please. It reminds me my actual age ;)
 
@digital BD we are all representing our brand or own name here in the user ID. But when you say your name is also Bangladesh, that's why i laughed. Good to see you are someone representing your country here. Anyways i am from Bangladesh as well as @nahid133. But we both are badass not doing the same. Respect man and all the best for your new journey :). BTW don't call me sir please. It reminds me my actual age ;)

Thank you, Brother :) Thank you so much. So nice of you :)
 
You can use trial Amazon windows VPS only for 1$ for one year. You can try that .

Thanks

Sir, yesterday I got an Amazon server successfully. But today I am unable to connect the server remotely. Note: I connected yesterday remotely and used. But today I am finding same message again that the server is unable to make a connection. Please see the attached screenshot of the message.
 

Attachments

  • Screenshot_1.jpg
    Screenshot_1.jpg
    34.4 KB · Views: 2
Sir, yesterday I got an Amazon server successfully. But today I am unable to connect the server remotely. Note: I connected yesterday remotely and used. But today I am finding same message again that the server is unable to make a connection. Please see the attached screenshot of the message.
it's occured for me also. What i did is, log into your ec2 dashboard, click in your Instance, Click Stop. After couple of Min click Start. You will get new DNS, Click "Connect" download the remote file usename, Password to connect your Amazon RDP. I hope it will help you, If the problem doesn't resolve I wonder you need to terminate your existing Instance & Install windows again.

How to avoid this Problem: Don't use or change VPN IP too frequently, Connect rdp using your real ip (gp, robi or local ISP what ever u use). void to connect RDP while you connected in a VPN.
I hope it will help, it help me to avoid this problem.
 
it's occured for me also. What i did is, log into your ec2 dashboard, click in your Instance, Click Stop. After couple of Min click Start. You will get new DNS, Click "Connect" download the remote file usename, Password to connect your Amazon RDP. I hope it will help you, If the problem doesn't resolve I wonder you need to terminate your existing Instance & Install windows again.

How to avoid this Problem: Don't use or change VPN IP too frequently, Connect rdp using your real ip (gp, robi or local ISP what ever u use). void to connect RDP while you connected in a VPN.
I hope it will help, it help me to avoid this problem.

Thank you, Sir.
Stopping... Hope it will help :)
 
it's occured for me also. What i did is, log into your ec2 dashboard, click in your Instance, Click Stop. After couple of Min click Start. You will get new DNS, Click "Connect" download the remote file usename, Password to connect your Amazon RDP. I hope it will help you, If the problem doesn't resolve I wonder you need to terminate your existing Instance & Install windows again.

How to avoid this Problem: Don't use or change VPN IP too frequently, Connect rdp using your real ip (gp, robi or local ISP what ever u use). void to connect RDP while you connected in a VPN.
I hope it will help, it help me to avoid this problem.


No, Sir :(
I did the same you have told. But again same issue :(
 
Sir, yesterday I got an Amazon server successfully. But today I am unable to connect the server remotely. Note: I connected yesterday remotely and used. But today I am finding same message again that the server is unable to make a connection. Please see the attached screenshot of the message.
You should go to amazon and have to take a look of this that you terminated that or not .. or your amazon account have been deactivate due to violation . If your account not been deactivated then you have to reactive the service again or create another one server from there and delete that first one .
I think it will help your

Thanks
 
No, Sir :(
I did the same you have told. But again same issue :(
Log into your EC2 dashboard. Click "Actions" >> Terminate to delete your existing Instance. When the process is done. Click "Launch Instance" to get a new one.
Please be careful to connect your RDP, it can be a mass pain in arse.
It gave me a huge pain, but now it seems ok, Just be careful with your IP.
 
Status
Not open for further replies.
Back
Top