Tech Support Forum - View Single Post

Mark Krikava · 06-26-2009, 10:53 AM

I disabled AVG and that didn't fix it.

I followed the directions at the Ventrilo web site to open ports and that didn't fix it either. Then again, I'm not sure I have XP Pro firewall, so maybe it's a different port.

Maybe I need to restart for some of this to take affect. I'll try that next.

"Q: Running a server with XP Pro firewall on.

If you are trying to run a server on XP Pro and have the XP Pro Firewall feature enabled then you must explicitly enable port 3784 for both UDP and TCP. Some firewall programs, like those that ship with Windows XP, do not have an option called "Both" or "UDP/TCP". In these cases you must create two entries in the firewall: One for UDP and another for TCP. This is easy enough to do by simply giving each entry a unique name such as Ventrilo TCP and Ventrilo UDP and assigning the appropriate network protocol to each one.

If you are running a local server you must have both UDP and TCP enabled for port 3784."

06-26-2009, 10:53 AM	#4 (permalink)
Mark Krikava Registered User Join Date: Jun 2009 Posts: 13 OS: Windows Windows XP 2002 Service Pack 3	Re: Ventrilo connection "loop" I disabled AVG and that didn't fix it. I followed the directions at the Ventrilo web site to open ports and that didn't fix it either. Then again, I'm not sure I have XP Pro firewall, so maybe it's a different port. Maybe I need to restart for some of this to take affect. I'll try that next. "Q: Running a server with XP Pro firewall on. If you are trying to run a server on XP Pro and have the XP Pro Firewall feature enabled then you must explicitly enable port 3784 for both UDP and TCP. Some firewall programs, like those that ship with Windows XP, do not have an option called "Both" or "UDP/TCP". In these cases you must create two entries in the firewall: One for UDP and another for TCP. This is easy enough to do by simply giving each entry a unique name such as Ventrilo TCP and Ventrilo UDP and assigning the appropriate network protocol to each one. If you are running a local server you must have both UDP and TCP enabled for port 3784."