Can't forward port 63639 on local network [closed] - networking

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.

Related

How do devices know how to connect a server from a different network using SSH? [closed]

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 2 years ago.
Improve this question
A SOHO network exists with many devices on it including more then 1 server, several end clients and network switchs. Lets say the private IP address for a specific server is 192.168.0.10 we will say the public IP address for the whole network is 11.2.2.11. A device from a different location wants to connect to the specific server mentioned earlier using SSH from 141.10.2.2. With so many devices on the network 11.2.2.11 how does the computer know that 141.10.2.2 wants to communicate with the server at 192.168.0.10? Using putty as an example we know that SSH communicates on port 22, how would the computer know that we want to connect to 192.168.0.10 on the private network and not another one of the servers with SSH setup? Does the person on the private network need to setup SSH to work on different port numbers for each server that is expecting to be remoted into?
For some context i am currently trying to setup a basic Linux server on my own home network and I am confused as to how I would connect to my servers when I am on different networks. I plan to have more then one server and I intend to use virtual machines. I am learning and trying to figure out how i would connect to each server.
You should use ssh port forwarding
let's say you want to connect to the port 22 of the 192.168.0.10 inside the private remote network .
use
ssh -L1337:192.168.0.10:22 user_remote_public#11.2.2.11
this will tell the 11.2.2.11 that you want to connect to the host 192.168.0.10 inside their private network on the ssh port .
now in order to establish the connection you should ssh on your localhost on port 1337 which will then be forwarded to the port 22 of the 192.168.0.10 inside remote private network
ssh user_remote_private#localhost -p 1337

Why do we have to use port 8001 when Port Forwarding? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
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.
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.
Improve this question
I've tried to do as much research as I can around this and I can't seem to understand one thing. For my University project we were required to do the following:
In VirtualBox Manager select File>Preferences. Select Network and choose NatNetwork (or the one you are using).
Chose the edit network icon.
Select Port Forwarding
In the dialogue box provide a name for the rule (e.g. web), leave the host IP blank, provide a host port (e.g. 8001), then enter the
Guest IP as the IP address of UBUNTU#1 and Guest port as 80 for a web
server (answer yes to any Firewall questions).
Start a simple web server on UBUNTU#1 by using the following command in the terminal window:
sudo python2 -m SimpleHTTPServer 80
Start Wireshark on the private network.
Start a web browser on the host computer and enter x.x.x.x:8001, where x.x.x.x is the IP address of your host computer.
Now we need to explain why do we use this address and port number?
My understanding is that the IP address being used belongs to the router/client on the network we want to make accessible to computers on the internet.
What I don't understand is why we have to use the port 8001?
I've seen that port 8001 is used for diagnostics, I have also seen 8001 is used as it is an available port. But how can it be available if it is being used by someone else.
You can use any port you like as long as both server and client agree on the port number.
Commonly, most services use a "well known" port to make it easy for someone else to connect to them (e.g. TCP 25 for SMTP, UDP 53 for DNS, TCP 80 for WWW, ...).

port 80 blocked by ISP [closed]

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 8 years ago.
Improve this question
I want to run a web server on my home network but my ISP doesn't let incoming requests from port 80, so I have to use port 81, is there a way I could hide the port number from my domain so that people don't have to type mysite.com:81 in the address bar?
I tried to use an SRV record but after failing so many times I realized that the browser needs to obey the SRV record and it doesn't so that's why it doesn't work.
Note
My ISP also wouldn't let me buy a static IP so I have to use a dynamic dns service provided by noip.com.
If your ISP blocks port 80, then you can't run anything, not even a port forwarder, on port 80. Which means your visitors will need to use the port number. Period. Sorry, but there's just no way to make the browser use a different port without telling it to.
One thing that some dyndns providers allow you to do is to create a page that's shown when the domain is offline. You could get jordanjones.noip.com and realjordanjones.noip.com, set jordanjones.noip.com to offline, and make a page there that's nothing but a frameset with one big frame that pulls in realjordanjones.com:81. Don't know if noip.com offers that service, though.
The only real answer is: get a decent provider.
You need to do either port forwarding or redirect requests on server.
For example run server on 8080 port and redirect all requests from port 80 to 8080.
See this: Apache VirtualHost: How to ServerName a port different from 80

Whatismyip and ifconfig giving different IP addresses [closed]

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.

Allow remote access to a localhost website in asp.net [closed]

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

Resources