can not connect using public ip

[john_usc]

I have a static ip and I can connect to the GUI fine if I use my local intranet addess. However when I try to use public ip, I can not get connect. My router is set to send all the requests to ip address of my server which is 192.168.2.2

is there anything I am missing? Does apache need to be configured to allow outside connections for vicidialnow 1.1
Thanks

[williamconley]

However when I try to use public ip, I can not get connect.

When you are "using the public ip" are you doing so from inside your firewall? Have you tried a proxy server (I've had this issue with a few Belkin routers that would not allow outside surfing that points back into the firewall from inside the firewall, belkin didn't see the need and i had to take the router back!). A place like megaproxy.com/freesurf will give you a quick way to check "what the world sees" vs what Your computer can see.

My router is set to send all the requests to ip address of my server which is 192.168.2.2

Can you list the port(s) you have forwarded and the method (DMZ vs port forwarding, etc.).

Have you verified your external IP address by pinging your router from outside?

[john_usc]

Today I tried pinging the server from outside. I din't get any reply. My DMZ is setup up to forward any incoming requests to my server whos local ip is 192.168.2.2 on port 80 for http.

I had windows server running with same settings for DMZ and it was working fine. Now since I replaced my server with vicidialnow, it is just not letting me access.
Thanks

[williamconley]

Try changing the setting in your router to allow pinging, and then verify that you actually are hitting your IP address. I've wasted an hour a few times troubleshooting only to find out that by sheer coincidence, the IP address changed at the moment i was moving servers. I thought I hooked something up wrong and began troubleshooting feverishly, only to find ALL the settings are correct, but the IP was wrong. Since I was using dynamic DNS, it reset itself a few minutes later and just "started working".

Another method, of course, is to attempt SSH local and from the net, at least that would finish the "is it the right IP".

[john_usc]

Ok I got it figured out.
First of all, I had to change the ip address in
/etc/sysconfig/network-scripts/ifcfg-etho0

I also needed to enter gateway. Here is a sample

DEVICE=eth0

BOOTPROTO=none

BROADCAST=192.168.1.255

IPADDR=192.168.1.105

NETMASK=255.255.255.0

NETWORK=192.168.1.0

HWADDR=00:50:FC:4B:B8:98

ONBOOT=yes

TYPE=Ethernet

USERCTL=no

IPV6INIT=no

PEERDNS=no

GATEWAY=192.168.1.1


then I changed /etc/resolv.conf

I was missing Primary DNS

here is sample

nameserver 192.168.1.37
nameserver 192.168.1.36
nameserver 192.168.1.38

(you may need a public ip there instead of local)

that did the trick for me

Thanks. Hope this helps someone