Ventrilo Tech Support - View Single Post

Prog-Rocker · 10-04-2008, 07:19 PM

perform a traceroute to the server and post the results:

start > run > cmd
tracert serverhostname(found in server setup)

try the telnet test:

start > run > cmd
telnet serverhostname port#

(where serverhostname={the server ipaddress or hostname of the server you’re trying to connect to (found in vent client server setup)} and port#={port associated with that server}
(example: “telnet 75.125.43.51 3784” or “telnet www.myserver.com 3784” without the quotes)

If telnet can't connect then vent won't either as telnet is a function of the tcp/ip stack which is a part of the operating system. If it can't make a tcp connection then something is preventing the connection on that specific port#.

10-04-2008, 07:19 PM	#4
Prog-Rocker just tryin to help Join Date: Jul 2006 Location: Local Space/Time Continuum Posts: 23,463	perform a traceroute to the server and post the results: start > run > cmd tracert serverhostname(found in server setup) try the telnet test: start > run > cmd telnet serverhostname port# (where serverhostname={the server ipaddress or hostname of the server you’re trying to connect to (found in vent client server setup)} and port#={port associated with that server} (example: “telnet 75.125.43.51 3784” or “telnet www.myserver.com 3784” without the quotes) If telnet can't connect then vent won't either as telnet is a function of the tcp/ip stack which is a part of the operating system. If it can't make a tcp connection then something is preventing the connection on that specific port#.