Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am looking to get the IP of my dev server. Everything online says to either do ifconfig or to curl something like whatismyip. These are giving me 2 different addresses. Why?
To add: I have no idea if it's behind a router or anything. I simply have an IP that I SSH into. I assumed that address was the address of the server - but when I curl http://ifconfig.me/ I get a completely different address.
Disclaimer: I have close to 0 networking knowledge.
You are most likely behind a router that does network address translation. Your ifconfig could be showing an IP address from a private range, such as 192.168.xxx.xxx.
An alternative is that your development server has several network interfaces, in which case ifconfig should be showing you several (such as eth0, eth1). However, I have the feeling it's the first, because you didn't mention this.
You could possibly check for the former with a tool such as tracepath, thereby discovering the nodes in between your development server and the other servers. But it might just be easier to check with the IT administrator(s) for your development server.
Well if you're behind a router that could be one reason.
If your dev server is externally facing it's entirely possible that the DNS server that whatismyip is using has a different IP entry than the DNS server ifconfig.me is using.
try running tracert www.yahoo.com from the command line and see what IPs shows up in the results.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am running Tunnelblick from my Mac.
My local network is 192.168.0.0/32 and the network I am trying to connect is 192.168.252.0/22.
Also, I am using a VM (Parallels) running Windows 8.1.
I want to connect to a VPN from my Mac and share this network with my VM.
So, I am facing some problems to do that. Here they go:
When I'm connected to the VPN, my ip address does not change to the ip address from the VPN network. My ip is still 192.168.0.132.
Despite the problem with the ip address, from the host I still can 'ping' the hosts from the network I am trying to connect writing 'ping host.domain.com'. But 'ping host' does not work.
I've already set the network to ‘shared’ in the device menu from Parallels. But, even with this, my ip address from the VM is 10.211.55.4.
In my VM I can't even ping the hosts from the other network
I'm sorry if I wasn't clear enough. All this problem is a little complex to describe.
Something important: The same configuration file I am using works perfectly (without the IP and the DNS problems) when I am using a Windows machine.
Change the VM's network adapter type to "Shared" within Parallels Desktop.
Configure virtual machine
Change network source to shared network
if that still does not work, disable ipv6 in guest machine.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
The ping utility works above the network layer and DNS works in the application layer.
If we try ping www.google.com, how does it resolve the IP address of GOOGLE since the DNS is above these layers?
ICMP (the protocol) may operate above IP, alongside TCP but a ping program itself almost certainly still uses the normal methods for name resolution, be that DNS, hosts file or resolv.conf.
For example, the ping program located here calls on gethostbyname() to turn DNS names into IP addresses.
Certainly on windows computers, ping also uses LLMNR (Link-Local Multicast Name Resolution) to perform hostname resolution.
A host may be pinged just fine while other services still fail if a computer is only known by LLMNR and the failing service relies on DNS.
Vice versa: DNS may work but ping fails
Hostnames are still resolved through DNS, after that ping uses ICMP for the actual communication. You can try changing the DNS configs to invalid servers and see that ping won't work with hostnames.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Hi I have developed a website and is on a machine(localhost), I want a friend to access it from outside my network, I have done some research and am being pointed to port forwarding as a solution. Any good links I can refer too will be highly appreciated.
Not a programming question, but how to setup your router.
The router, especial the adsl modems that you probably use, they not forward outside request to inside network, for security and because they are not know where to send them.
So on the setup of your router you need first of all forwarder the outside calls to your pc.
Now, this have two parameters, what port send to what inside ip.
How to forward ports on your router page with images and examples.
Let say that you have a pc behind the router at ip 192.168.1.100, and setup there a local iis on 80, then you need to setup the router so when is accept call on port 80, to send it to 192.168.1.100
Now you need to know what ip to give to your friend to try to make call to you, you can find it using the http://www.whatismyip.com/ The ip they see you outside is the one your friend must type on browser.
And then need to make your iis run, and allow your pc firewall to accept calls on port 80.
#Aristos gave you the answer. But have in mind that some internet providers block port 80 so you might have to change to 88 for example. And your friend will access it as
http://your_external_ip:88
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am developing a windows service application that listens on port 63639
and can get messages an retrive messages
When I do this in the cmd
telnet 127.0.0.1 63639
it get inside and get back the welcome message
but I want to communicate with this application from another computer on the local area network
I have 3 computers on the network with a d-link dsl-2650u router.
My ip address is 10.0.0.3
When I try the cmd:
telnet 10.0.0.3 63639
from another computer I receive "could not open connection to the host, on port 63639"
Then if I try:
telnet 10.0.0.3 80
I am able to get access. I also tried port 135 and that is able to get access also.
That leads me to think the blocking is from my router because I have win 7 and I looked in the firewall logs and I can see the logs for ports 80 and 135 but not for port 63639.
I am very sure that is the router. I also set the router for NAT/DMZ for 10.0.0.3 and it still does not work and I am not able get any log. I also tried defining NAT/Virtual Servers.
Thanks guys, I am going crazy since I have been trying to get it to work for over 6 hours
If you bind to 127.0.0.1, you'll only be able to connect from 127.0.0.1; if you bind to 10.0.0.3, you'll only be able to connect from devices on that network interface. If you bind to 0.0.0.0 you'll able to connect from interface the computer has.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
How do I set up a network between the Host and the guest OS in Windows vista?
Give the guest two network adapters, one NAT and the other Host-only. The NAT one will allow the guest to see the Internet, and the Host-only one will allow the host to see the guest.
One of them also allows the guest to see the host. I'm not sure which, but I know it works since I've tested web server stuff with it. You just have to choose the right IP address, 10.x.x.x or 192.168.x.x.
Also, you may have to be careful about having File and Printer Sharing running on both adapters at once, since the guest will see its own name and conflict with itself. I ran into this during install.
I've got a better answer than my first one.
Give the guest a single Host-only network adapter, and enable Internet Connection Sharing (ICS) on the host. I've tried this on a Windows XP host with a Windows XP guest.
The guest can connect to the Internet.
The guest can connect to the host at an address like 192.168.0.1 (chosen by ICS). -- Remember to allow the guest through the host's firewall.
The host can connect to the guest at an address like 192.168.0.22 (assigned by the DHCP service provided by ICS).
You can do this on a Linux host. I've documented the steps I took in Ubuntu 9.04 here.
I don't run vista, but virtualbox should do most of the setup for you - all you need to do is assign an IP address, subnet mask, and (optionally) a default gateway to your guest OS, and it should just work.
Don't bother with any of the advanced network settings in the options for the VM - they're useful in some situations, but I've never had to use them, and I've been using virtualbox for some years now.
If you post the specific problem you're having perhaps I can help more. But your question is rather vague...