Yes, we need to know why you want to ping it. Some configuration solutions may render you PC wide open to attack from everybody on the Internet.
Main Topics
Browse All Topicsi am using a cable modem and Linksys router (WRT54G), and my PC is connected to this router.
i need to ping (from anywhere outside) to this PC, but how to set/configure this router ??
details:
just for info: if i connect my PC directly to cable modem, without the router, i can ping to my PC from outside, becos my PC will acquire a dynamic IP address. But now, when conected to a router instead of a cable modem, how do i set this router to enable my PC to be ping ??
(a) should i set the router to be a bridge/transparent ? quite impossible becos there are a few PCs needing a router
(b) or should i ping to the PC with e.g. xxx.xxx.xxx.xxx:2020 ? but how to configure such ??
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
ICMP is not a port, it is a "layer 4" protocol just like TCP and UDP . Most home and small business type routers don't allow forwarding of ICMP messages. I know that the Linksys provided firmware for the WRT54G does not allow this. One of the open source firmware packages may.
If you really, really need to ping you can go into the WRT54G and setup the computer you need to ping as your DMZ device. The WRT54G will then pass ALL unsolicited traffic from the Internet to that computer. The WRT54G will no longer be protecting that computer and depending on the OS you run and the setup of that computer could become compromised very quickly.
Txs for your comments. Just to explain more:
i am trying to use TightVNC (freeware) on 2 computers, one set as host, and another as viewer. The host is behind a router, so i could not establish the connection (unless i connect the host directly to the cable modem and use its dynamic ip address acquired, right ?)
any solution ?
Read:
http://www.realvnc.com/faq
Basically you need your WRT54G to foward port 5900 and 590x (depending on which display you have the VNC Server configured to use, to the computer that is running the VNC Server.
From the VNC Viewer you need to connect to the public IP address your modem has acquired. The modem, once configured to do port forwarding, will then forward all traffic to that port to the computer running the VNC Server.
I am testing your comments using 2 computers connected behind a same router. After setting port forwarding on the router to 192.168.1.101, i run TightVNC viewer on my dynamic ip address, but got the msg "Failed to connect to server (my dynamic ip)"
Just wondering what could be the careless mistakes one may overlook ?
i tried access my neigbour unsecured wifi and tried TightVNC viewer...it shows the same err msg. (meaning - i just tried also accessing from another network to the host).
also, i noticed the add new client, and wonder is this relevant also ?
any more comments ? i am about to give up, and give away the points. pls help. :) Thanks.
I don't know about SysExpert, but I am starting to get confused on what you setup is that you are trying to test.
So to make it simple:
Viewer <---> VRouter <---> Internet <---> SRouter <---> Server
The SRouter needs to be configured to foward TCP ports 5900 and 5901 (assuming VNC is setup as display :1)
When the viewer tries to connect to the server you need to specify the public IP address of the SRouter and the display number, something like:
x.x.x.x:1
Assuming again that the VNC server is setup to be display :1. Which is the default.
Just to summarise what i learnt from your comments and links given:
..."ip" or "ip:5900" cannot work. "ip:0" will.
...computers with the same network/dynamic_ip cannot work. Should test TIghtVNC via the internet.
...each software uses different (port) number. (e.g. TightVNC uses 5800,5500,5900)
free to comment any mistakes. thxs.
--> ."ip" or "ip:5900" cannot work. "ip:0" will.
correct IF the VNC server is started as display 0. If it is started as display 1 you need to code ip:1
--> ...each software uses different (port) number. (e.g. TightVNC uses 5800,5500,5900)
No. VNC and TightVNC use the same ports. If the server is started as display 0, then 5800, 5500, and 5900 are used. If the server is started as display 1 then 5801, 5501, and 5901.
When you start the VNC server you should get a message something like:
New 'servername:# (userid) desktop is servername"#"
Where servername is the name of the computer you started the vnc server on, "#" is the display number, and userid is the userid that it was started for.
For the port number you would replace the last digit of each port with "#". So if you isssed the command and go a "3" where the "#" is you would use port 5803, 5503 and 5903.
Business Accounts
Answer for Membership
by: sirbountyPosted on 2007-04-21 at 13:41:00ID: 18952556
Perhaps you don't need icmp (ping packets)? What application are you trying to use?
Depending on your router version (I have the same model), you'll want to locate Application & Gaming and enter your application, the port number it uses and the target NAT address (192.168.1.x). This will forward the packets across the router to the target device...