I have tried to connect a page which is hosted in ec2 instance. It is showing server timed out error but rest of my collegues able to connect to it.
I use mac laptop
Things i did:
clearing cache
tried to change my network
3.tried in incognito mode
nothing works. Thanks in advance
Things to normally check:
Confirm that the EC2 instance is running a web server (try to access it from somewhere else, or login to the instance and try curl localhost)
Confirm that the EC2 instance is in a public subnet (defined as the subnet having a Route Table entry that points to an Internet Gateway)
Confirm that the Security Group associated with the EC2 instance is permitting inbound access on port 80 (for HTTP) and possibly port 443 (for HTTPS)
Confirm that you are attempting to access the instance via a public IP address (not a private IP address) and that the public IP address is currently associated with the instance
Don't change default NACL rules
You mention "rest of my colleagues able to connect" but you don't mention from where they are accessing the instance. Quite clearly, something is either different with your computer or with the network that you are using. I would suggest you focus on:
The Security Group "inbound" rules, to confirm that they are not blocking access
Try to connect from a different network (eg home vs office vs tethered via your phone) to confirm that your network is not blocking access
If you are connecting from the same network as your colleagues, then the problem is on your computer. This is unlikely because the timeout normally indicates a lack of network connectivity (rather than software configuration).
Related
I have a VM running Orion that has an internal status page. Example https://<cluster.com>/internal
I have assigned an external IP to the host and I'm about to SFTP and SSH to the host perfectly. But this internal page requires port 2201 to be open. Which I do have open. But I can't access the site with https://external-IP/internal. If I create a VPN to the network on GCP from my laptop I am able to connect using the https://internal-IP/internal. I'm not a network expert or a GCP expert an help would be welcomed.
This pattern worked for me in the GCP Compute Engine
https://external-IP/internal/internal-IP:2201
I'm setting up an Active Directory in Windows 2012 for user authentication in Windows 10. Server and client PCs are not in the same area, therefore, it is a Wan connection.
For testing purposes, all firewalls are off. Server's public IP is 34.207.231.151 and a has a local IP 172.31.13.53. DNS in the server is active and correctly points the desired domain adir.school1.com to local IP. Client PCs use the server's public IP as DNS, that works well because if I ping adir.school1.com, I get the servers local IP.
If I try to join the clients to the domain it says Cannot contact with an Active Directory Domain Controller in the domain. In the details it says that the DNS was successfully query and it identified a domain controller but it cannot contact the Domain Controller.Which is expected as it cannot connect to 172.31.13.53 outsdie the LAN. How do I configure my ADDS to be reachable outside the LAN?
It looks like about your network configurations. I draw a basic network configuration.
Also you can see a wan network here. Gateway is very important at this point.
In order to use ADDS through WAN, you do need a VPN. I could not use this solution, though, because the admins of the network did not want to open the required ports for VPN overt the firewall.
The solution was to change the network configuration of the entire campus so our virtual server became part of the internal nerwork (which is a bunch of LANs with gateways) and voila!, the ADDS was reachable from all other computers. Still, not accesible outside the campus, but inside it works perfectly.
we are using solr version 6.5.1 ,we are set the solr in server need to access the url outside server ,we using server windows server 2012 now local host weare using this url how to access this url in outside
http://localhost:8983/solr/kmartdev/select?&indent=on&defType=dismax&q=amul&qf=name+model&wt=json
When using in same network
When client is in same network, then you don't need to have a public IP of the server to access it. Follow these steps:
Find the IP of the server
Add into host file of the client, say XX.XX.XX.XX solr.com
Open http://solr.com:8983/solr/ for admin panel.
Step 2 is not mandatory, but if you dont add in host, then use IP address in browser. It will be `http://XX.XX.XX.XX:8983/solr/
When using in different network
To access the server that is not in your domain, you need to have a public IP. If you have taken the domain name then use http://yourdomain.com:8983/solr/, but if not, then add in host, or directly use IP address (steps are same as in the previous ones)
I got the answer, actually we need to open a port into our server. So, I've opened a post from control panel-> windows firewall-> inbound rules. And I've opened same port into azure server also. Now I can access my solr from anywhere.
Hope this answer will help someone and save their time. :)
I am new to AWS. I have created a Spring Web app and a database(MySql) in a EC2 instance (which is working fine). In my web application, I am connecting to a database that is in another server to read and write to this other database.
So, This database is not a MYSQL database. The network admin has opened up the port 3306 for this EC2 instance to access the database from EC2. So, the problem is in my end.
I have opened up the 3306 port (My SQL) in the security group. But when I telnet the port, the connection fails. I can see that in EC2 127.0.0.1:3306 is listening just like 80.
So my question is, what am I missing here?
What are the options to trouble shoot this issue?
Do I have to authorize the tomcat user or Bitnami user to access ports to connect to an outer database?
Anything relevant to this issue would be helpful
thanks in advance :)
If its listening on 127.0.0.1:3306 it is listening locally only and is not accessible form outside. If you change that to 0.0.0.0:3306 make sure your security groups are configured to only allow access to your database from your own instances. Dont just "open up 3306", open up 3306 only to the same security group or the security group your application spring server is in.
You say its not a mysql db, yet it uses mysql default port 3306. Thats a bit confusing. If its mysql you need to change the bind-address in my.cnf.
I think you need to give permissions to user like "dbuser#192.168.1.5" where IP is the IP from dbuser is trying to access the database.
Krish
It seems, This question is stupid, But then, This was a real problem. So, I will summarize what I learned and answer the question. IP Addresses are categorized into types, minimize the exhaustion of IP addresses (That is why we moved from IPV4 to IPV6). Anyways, there are Public IP addresses and Private IP addresses. Private IP addresses are for local networks and Public IP addresses are for accessing through the internet. So, What I did was, I opened up the port for the connecting Servers public IP address (It turned out to be PORT is not 3306, It was 2001 in my case, You only have to do it through Security Groups because my default all the outbound ports are open for EC2) and also, from the other end TCT PORT was opened for EC2. To do that I had to create a Elastic IP address for my EC2 (What Elastic IP address do is, it assigns a Public IP address that will not change when EC2 get restarted or changed). Then it should connect, For me it did not work till I created the Elastic IP
I have a veru bizare issue.
When trying to connect via RDP to a remote laptop which has been taken off the network for a few days. When connected again to the network, i cannot RDP into it using DNS name but can using IP. OS is windoes 7 Enterprise x64 using AD.
Taking it off the domain and adding it again does not help.
Any suggestions?
Can you ping the DNS name via the command prompt? Sounds like rejoining the network may have assigned a different IP to the alias.
To rule out firewall issues you could also disable firewalls on both temporarily and try again - though I doubt a firewall is the problem because you're able to access it via the IP address.
DNS was the issue. It was not releasing the associated IP. Had to purge all old data and schedule auto periodic purge.