Author Topic: Ventrilo conflict  (Read 298 times)

Offline Benny Moore

  • Silver Member
  • ****
  • Posts: 1439
Ventrilo conflict
« on: January 17, 2007, 07:34:18 PM »
I was able to host Ventrilo until I configured my router to be able to host Aces High II.  Here's how it looked before that, when Ventrilo worked:

Name: Ventrilo    Port: 3784    Forward to: (my internal address)

Now, after configuring my router to host Aces High, here's how it looked:

Name: Ventrilo    Port: 3784    Forward to: (my internal address)
Name: Aces High II    Ports: 2000-6000    Forward to: (my internal address)

Under those settings, I was able to host Aces High, but not Ventrilo (even when Aces High was not running.  From my limited understanding of firewalls and networking, I should be able to host Ventrilo even if I were to delete the Ventrilo entry, since 3784 lies between 2000 and 6000.  Can anyone see anything I'm missing, any reason why Ventrilo will not host?

Offline Benny Moore

  • Silver Member
  • ****
  • Posts: 1439
Ventrilo conflict
« Reply #1 on: June 04, 2007, 01:02:20 PM »
I'm still having this problem.  I tried reducing the ports to the two that Gpa3 recommended, which would allow Ventrilo to work, but now Aces High II won't host.

Offline Benny Moore

  • Silver Member
  • ****
  • Posts: 1439
Ventrilo conflict
« Reply #2 on: June 05, 2007, 09:24:05 PM »
The problem has been solved.  Removing the redundant entry for 3874 has fixed the error.  It now just has the Aces High II entry of 2000-6000, and both Aces High II and Ventrilo can host simultaneously, since Ventrilo's port falls under that range.