Greetings to all
Friends people with more knowledge than me ( and sense) can help to troubleshoot it.
When one should try to connect to port 3306 of particular ip here e.g. 345.56.67.87 it should be redirected to port 3306 of internal machine.
This is the scene : How can I access the particular port of the machine which is behind the router . i.e.
so i have the lg esteem on metro pcs and ive rooted it. i aso use wifi tether to play games on my laptop using my 4g, but i cant pay diablo 2 because i get a error saying port 6112 is closed. ive tried the port forwarding app but it doesnt work. ive also ran a port scanner i found that says port 53 on my phone is the only port open. any assistance in solving my problem would be appreciated.
Hello folks,
I have an AIX server that is connected to a storage array via a Brocade switch using 4 ports from either side. The zoning is done such that there are 4 paths visible from the server to the storage.
My work involves frequent disabling or enabling the switch ports that are connected to the server.
I edited my SSH configuration to accept connections on Port 213, as it was one of the few ports that my work firewall allows through.
I then restarted sshd and everything was going well.
I tested the ssh server locally, and checked the sshd service was listening on port 213; however, I still cannot get it to work outside of localhost.
PuTTY gives a connection refused message, and some of the si
I am running a linux machine between two IP Phones with Two NIC card's.
All of the traffic passing through between eth0 and eth1 should move through TCP/IP stack.
Currently,IP-forwarding is enabled in linux and traffic routes directly at Kernel level.
If I am doing port forwarding using IPtables, I can get the traffic in TCP/IP stack but I dont want to perform port forwarding.
Edit /etc/apache2/ports.confIf your ISP doesn't block port 80 I would set your router externet port to that.Hope that helps.Edit: sorry just reread your OP ports.conf should do the trick,also check /etc/apache2/apache2.conf for these lines# Include the virtual host configurations:
Include sites-enabled/
NameVirtualHost 192.168.1.xxx:80
NameVirtualHost 192.168.1.xxx:443and change if needed.
I'm not port forwarding that way either or anything like that.
So yeah, I have a (paid) static outside ip, and when I type that in I get access to my browser. What the hell is up with this?
I have set up vagrant-dns but it's a shame I can't use the names from within my Vagrant VMs. (vagrant-dns sets up a nameserver on port 5300 on the host machine)
I found the resolver cookbook and it occurred to me I could maybe use that with Vagrant's port forwarding to make the vagrant-dns nameserver accessible from with the VM.
I configured port forwarding through iptables and ufw. But there is something I do not understand, I just cant get iptables to forward port 443 to 8443 without allowing port 8443 on UFW.