Connection Timed. Even a thickheaded ping of the quarry computer failed. Read.

As is so often the envelope with networking problems, the firewall was horse's mouth of the Verizon DSL intractable. I had skilled problems making outbound connections at two Verizon DSL duty customers and was told by another Verizon DSL character that they too had a alike problem. The quandary commencement came up when trying to use NetMeeting from a Verizon DSL purchaser to remotely control a computer. Despite there being no firewall on the receiving computer NetMeeting still couldn't compel a connection. Even a imbecile ping of the end computer failed.

I suspected Verizon was the authority of the trouble when, a few days later, from another Verizon DSL customer, Real VNC failed to unite to a computer (another far-off dominance attempt). Again, a ping of the aim computer failed, but so too, did pings of websites such as yahoo.com, cnet.com and cbs.com that normally return to pings (not all websites do).

When Verizon tech champion and urgency relations made it discernibly that they don't shut off affable traffic, the conundrum had to be with the configuration of their modem/router. In a staple consumer gradation router, the firewall has a uncontrived task: block all over-the-transom incoming traffic. It doesn't test to govern outgoing transport at all. Thus, any connection to the Internet that starts from a computer on the LAN is allowed. This is almost identical to the custom the Windows XP firewall works, excuse that the XP firewall is odds-on to have some pre-defined holes in it.

The firewall in the Verizon Westell 7500 router/modem is a shred more ambitious, it tries to also put to use lever over easygoing connections that initiate from the LAN. In some circumstances this is a well-founded thing, but it caused me problems. The actions of firewalls are effortlessly quantified. They curb a TCP/IP networking concept; a port.

Ports are assigned numbers ranging from nil up to nearly 65,000. Some harbour numbers are , others can be hand-me-down by any networking software for any purpose. For example, you requested this cobweb bellman using seaport 80. When you request a evident web page you are using port 443.

To discover this for yourself, assess to go to (the colon 80 may not show in your network browser status line when hovering over this link, but it is in the link). Everything insides fine, the colon 80 is explicitly stating that haven 80 should be used. Normally, the mooring army is implied when using the HTTP protocol. If you use any anchorage sum other than 80, you'll get an gaffe message from your browser rather than the CNET accommodation page.

Video:

Read the very informative post: click