OK...if I setup PCHelpware with just my computer...works fine. I connect it thru my Netgear router, works fine....HOWEVER, I have a VOIP router, GrandstreamHT502 that is giving me a FIT...I cant get it setup thru it....
My Grandstream is directly connected to my cable modem...so it has my modem IP, the Grandstream has an IP of 192.168.2.1 as a base IP for LAN
My Netgear is connected to the LAN port of the Grandstream and gets an IP of 192.168.2.100. The LAN port of my Netgear is 192.168.0.1 which gives my computer an IP of 192.168.0.2...I have the same port fowarding inside the Netgear...but PCHelpware cant get thru.
After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Weird setup...cant figure it out
Re: Weird setup...cant figure it out
So you're double NATting. Unfortunately I have no idea whether UltraVNC, let alone PCHelpware, can deal with that.
I assume that you have it set as follows?
a. Grandstream says forward port 5900 from publicIP to 192.168.2.100.
b. Netgear says forward port 5900 from its "fakepublicIP/192.168.2.100" to 192.168.0.2.
c. All unnecessary firewalling, SPI, VoIP QoS, etc. turned off in both routers.
d. ICMP passthrough (pinging) enabled on both routers.
From an outside address, can you telnet in to port 5900? (Or use ShieldsUp to determine whether the port shows as open?)
The first question is whether the port is really open to the world through both routers.
The second question is whether VNC is bothered by the double NATting.
You might consider "DMZing" the Netgear as far as the Grandstream is concerned.
Also, can't you just use the Grandstream INSIDE the network, attached behind the Netgear? That would certainly simplify things.
Alternatively, if you need the Grandstream as the first router and it doesn't have enough switch ports, consider chaining it to a switch and letting the VNC target receive a 192.168.2.x address....
I assume that you have it set as follows?
a. Grandstream says forward port 5900 from publicIP to 192.168.2.100.
b. Netgear says forward port 5900 from its "fakepublicIP/192.168.2.100" to 192.168.0.2.
c. All unnecessary firewalling, SPI, VoIP QoS, etc. turned off in both routers.
d. ICMP passthrough (pinging) enabled on both routers.
From an outside address, can you telnet in to port 5900? (Or use ShieldsUp to determine whether the port shows as open?)
The first question is whether the port is really open to the world through both routers.
The second question is whether VNC is bothered by the double NATting.
You might consider "DMZing" the Netgear as far as the Grandstream is concerned.
Also, can't you just use the Grandstream INSIDE the network, attached behind the Netgear? That would certainly simplify things.
Alternatively, if you need the Grandstream as the first router and it doesn't have enough switch ports, consider chaining it to a switch and letting the VNC target receive a 192.168.2.x address....
Re: Weird setup...cant figure it out
You need to have the port forwarding at the GrandstreamHT502 too.JediKnight2 wrote:My Netgear is connected to the LAN port of the Grandstream and gets an IP of 192.168.2.100. The LAN port of my Netgear is 192.168.0.1 which gives my computer an IP of 192.168.0.2...I have the same port fowarding inside the Netgear...but PCHelpware cant get thru.
According to your provided information, you should setup a rule (at GrandstreamHT502) of forwarding 5500 to 192.168.2.100; and a rule (at Netgear) of forwarding 5500 to 192.168.0.2
Yes, I think this a better approach rather than having two routers in your network, or unless you want it to be intentionally -- like separate some computers into two network segment.B wrote:Alternatively, if you need the Grandstream as the first router and it doesn't have enough switch ports, consider chaining it to a switch and letting the VNC target receive a 192.168.2.x address....