I have used a windows command to find this
nslookup myip.opendns.com resolver1.opendns.com
and gives me an IP but if I run the same command in other pc which is in the same subnet will also give the same IP. There is no difference in both's IP.
This is same when I search in the browser as What is my IP?
Now How can I know My external IP address of my windows system? However I got internal IP from the command ipconfig which is not usefull now.
Internal IP:
A local Area Network Address provided by your DHCP server/ Router.
External IP:
A Wide Area Network address provided by your ISP(Internet service provider).
Internal IP/ LAN Address, can only be accessed within the same network. Think of babies and a mother in a house. Babies talk to each other and to their mom but don't know anything about outside. If they want any outside information, they ask their mother and mother translates the outside information to them.(NAT Translation)
Similarly, no one from outside can reach to the babies. The mother will protect her babies from anyone and everyone except she knows someone and she trusts someone what their intention is. (Port forwarding)
In your case, it is normal that both PC (babies) in the same LAN network have same external IP (Mother's name/IP). If you would like to reach to a specific baby from outside, you must ask the mom and configure the mom (Your gateway router) to permit this action.
usually default gateways in a home setup are 192.168.1.1 / 192.168.2.1 You will find this information using ipconfig
In Addition,
babies within the same household do not require mothers permission to talk to each other. They can freely communicate. However if wish to play hide-and-seek, then they need their mother's permission (UPNP settings). Where mother reveals information about one child to another.
Related
I am configuring a High Availability load balancing based on HAProxy and Keepalived.
Everywhere I do research they talk about Virtual IP like something that fell off the sky – I mean, with little to none explanation about how to get one.
By now, I have arbitrary defined a virtual ip address in the keepalived.conf like this:
virtual_ipaddress {
10.0.0.100
}
With both Servers running keepalived, I do ip address command in the MASTER machine and it shows inet 10.0.0.100/32 scope global eth0 next to the Public IP, which I believe is correct.
When I do service keepalived stop in the MASTER machine and run ip address in the BACKUP machine, BACKUP shows inet 10.0.0.100/32 scope global eth0, IP which effectively disappeared from MASTER.
The above mentioned behavior indicates me that the config is all right.
Now, how can I publish that Virtual IP? Do I need to buy one? If my server provider (Contabo) doesn't offer the Virtual IP service, where to buy it?
My goal is to have my Front-End API requests aiming at the Virtual IP.
Thanks very much in advance for any guidance!
Server A and server B addresses are either manually configured when setting up the servers, or obtained via dhcp.
There is nothing magical about the virtual ip, other than it is not obtained in the same way.
If it is your own network, you can just pick one in the same range as for the two servers, and make sure that no new servers will use it.
Since you are talking about a provider, you will need to ask them if they provide floating ip addresses.
10.x.x.x is a private ip, so you can not publish that to the internet, but you could use it for example to fail over internal services.
I installed ws2016 server as a domain controller on virtualbox using internal network .
Everything was successfully installed about active directory and i created domain name as 'stark.local'
Also i created another ws2016 on virtualbox using internal network and I want to join new virtual machine to my domain controller.
Can ping dns server(which is my domain controller) and also Firewall off, no anti-virus installed.
However when i try to join dc it gives below error;
what i realized that i can not make nslookup to my dns server ip.
Even if on domain controller can not nslookup its self.
ipconfig of Domain Controller
ipconfig of node1;
I had no hair now and need your help.
Finally solved!
The problem was using internal network. I changed to host-only network and it worked.
AC DC
Using public IP addresses will always get you in trouble, try changing them to something like:
192.168.1.10 & 192.168.1.20
(Please read entire answer before modifying)
Also, i would recommend checking this link on the official microsoft forum. I know it's from windows 7, but i think the main problem you have is with the DNS configuration and it's very well explained there.
I'll summarise the link above here:
#Meinolf Weber's answer
If domain machines contain public DNS servers as 200.88.127.23 and 196.3.81.5 you will always have trouble.
Remove them on ALL domain machines and run ipconfig /flushdns and ipconfig /registerdns and reboot clients and domain member servers and restart the netlogon service on DCs instead reboot.
For internet access please configure the FORWARDERS in the DNS server properties in the DNS management console with the public DNS servers.
Explanation:
You can't join a machine to the domain using public IP because it is trying to locate your domain to the public IP which has not information of the private build domain.
Use only local IP in the clients NIC.
Hope it helps, if not please give more detailed information of the issue as well as the DNS configuration (screenshot or whatever you can).
EDIT 1: also check "time settings" on both machines, i know it might seem silly, but that sometimes gives DNS and DC issues. Check IPv6, could be another probable cause of the issues you're having (Go to the network and sharing center, modify the properties of the NIC and unselect TCP/IPv6).
I'd check first IPv6, that'll save you work if it's only that.
EDIT 2: again, i would recommend changing the IPs (if possible) to another network, as long as the 169.254.x.x is used (assigned) when there's no DHCP server, but as you say they can ping to each other, it may not be necessary the problem.
I can see there's no router in the network but, a Windows Server should be providing DHCP, otherwise things like DNS suffix don't work.
So check that:
- You have the DNS role installed and configured to support AD.
SOLVED on answer below
The explanation i would give for this is that "secure communication" is an often requirement, thing that internal network doesn't provide.
Let's say my computer name is "MY_PC". It will be "MY_PC" no matter which LAN I am currently connected to. So at home or at some open wirless access point, my computer name will be the same, right?
How does this come into play with DNS? The way I understand it, my computer's FQDN is used for DNS lookup. How does this work exactly?
When I connect my PC to a network, my PC sends its computer name to the nearest DNS server (usually the router, I guess) and is added to its DNS table?
I guess what I am asking is: What role does my computer's name play in my everyday internet activities. I was a little suprised to find out, it is the same in any network, but when is my computer's name actually used? Why does it have to be the same in any network?
Your computer name has little to do with DNS unless it is joined to a domain. Even then the computer name is not a DNS entry.
A FQDN is something like www. google. com:
Each period represents a subgrouping
www - is the world wide web group #
google - this is the company owning that group which belongs to
com - this is the entire group of companies in the united states with registered web addresses
The point of a DNS is to allow you to remember logical word groups instead of IP addresses (ie. it is easier to remember www.google.com, instead of 172.217.9.132).
Even on a company/private network the same is true, a DNS is used to allow a central administrator to assign names to certain network addresses.
When you assign your computer name it is similar but it not a DNS entry, as it is not administered on a centralized computer(s).
So if no one on your network, or outside of your network, need to easily remember where to find your computer (for some service) then you do not need a DNS entry.
This is just a basic version of why we use DNS. Other benefits include Disaster Recovery, ease of system migration and ease of building nested systems. Let me know if you would like me to elaborate further on this answer to accept it.
I've just begun the setup of proxmox for our none profit educational VPS service. However, the problem we're facing is a lack of IPv4 addresses available to us.
Is it possible to route a sub-domain to the host servers IP address and then get that forwarded to the individual containers accordingly. For example:
SSH root#node-123.w-a-s-d.me
Will allow a client with the VM ID of 123 to access their server
And the same goes for things like: node-123.w-a-s-d.me
This would be the web address allowing any applications running on port 80 for that specific node
I'm unsure how to go about this and have looked online with no luck. I hope our goal is clear. I look forward to hearing from you. Josh
Exposing SSH that way will not be easy as you can only have one thing listening on port 22 for every given IP address, and while you could just adding random ports to each VPS and the forward it from primary box which holds public IP (and vms are behind nat) this is not exactly the best solution.
What you may want to do instead is set up one public-facing box that people can ssh into via public IP and from it SSH to subsequent private machines by their internal IP. Alternatively you can set that box with openVPN and set it to assign internal IP address to anyone connecting via it. While openVPN takes more time to set up right, it can come with it's own DNS so when connected to it calling out SSH root#node-123.w-a-s-d.me will automatically route you to the private IP address rather than the shared public facing one.
With HTTP this is much easier as you can set up a proxy on the front-facing machines which then proxies requests for given sub domain to specific internal IP address.
I'm trying to use Cain & Abel to log the network traffic between my domain controller which is a Windows 2008 Server (Machine A) and Windows XP computer (Machine B). They're both installed as virtual machines on an ESXi server I recently bought, and rather than putting them on a NAT, I've configured ESXi to keep them both bridged to my network.
Machine B is on a domain known as 'test.local' with an IP of:
192.14.0.195
Machine A is hosting the domain 'test.local' with an IP of:
192.14.0.196
My target is to detect the hashes being sent by Machine B to Machine A.
I was able to log traffic using the sniffer + ARP Poising technique. However, I like to learn how to reverse engineer and hack things, and then try writing something to 'patch' or 'prevent' it and since one my of my friends had told me earlier that he had used Cain and Abel to log the same stuff, but when the domain controller had an IP of something like:
192.15.0.198
And Machine B had an IP of:
192.14.0.195
As you can see there's different subnets. Knowing this is possible, how would I go about accomplishing attacks on the hosts that are on my subnet, but the domain controller is not? I know it is accessible because running 'nslookup' sets it as the default server and traceroutes and pings are successful. I can also RDP to it.
Any help is appreciated, thanks!