Background Info:
I have a Openfire set up on a virtual machine inside Windows Vista (host). This set up is connected via ethernet to the router to the cable modem. The VM is set to Bridged Mode.
Host IP: 192.168.1.101
VM Openfire: 192.168.1.102 --- (Openfire's Admin Console)
I can access .102 from any computer that is directly connected to the router by entering the .102 or localhost:9090 --- I also know that the server works within the 192.168.1.X network. I've used Spark and Pidgin clients connected to .102 to confirm it.
What am I trying to do?-- I want access .102 from any network connected to the internet.
Example: My IP is x.x.0.13 and I want to access .102
What I have tried:
Adding .102 to router's port forwarding 80 to 80
Adding .102 to the DMZ
Adding port 80 to Windows Firewall
Disabling Windows Firewall completely
Openfire Server is already set on Windows Firewall to "Allow communication with this program from any computer, including those on the Internet or just from computers on your network."
Maybe I am doing something wrong? -- Wrong port forwarding?
When adding .102 to the port forwarding or DMZ. I'm assuming I access that by doing .102:8080
Also tried, Public IP:8080
I'm not sure if my question is clear. I'm happy to try to clarify it as much as possible. Also, thanks for looking.
Access Server Outside of LAN
Page 1 of 12 Replies - 7603 Views - Last Post: 20 October 2012 - 08:19 PM
Replies To: Access Server Outside of LAN
#2
Re: Access Server Outside of LAN
Posted 19 October 2012 - 05:50 PM
Try from Bridge mode to NAT on the VM.
#3
Re: Access Server Outside of LAN
Posted 20 October 2012 - 08:19 PM
I believe OpenFire uses Ports 5222 and 5223.
In the router I would adjust port forwarding on those two ports to the 192.168.1.102 IP address.
In the router I would adjust port forwarding on those two ports to the 192.168.1.102 IP address.
Page 1 of 1

New Topic/Question


MultiQuote




|