MSG: Contacting Server - Page 3

wadesworld · 11-18-2007, 09:49 PM

Did you try deleting the receipt package in /Library/Receipts?

apinchofhope · 11-20-2007, 05:08 PM

Quote:

Originally Posted by dontpanic

They took them down for the same reason any other company would. To phase out one version and phase in another. They know that people are going to stick to 2.3.0 for fear of upgrading. This thread is proof of that

. This I'm sure is also the reason they did not make them backwards compatible; to prevent people from being scared to update. In short, they want people to use their new product

it would be really super if their new product worked like their old product!

fwrightson · 11-21-2007, 11:08 AM

yes, I received the same msg "connecting to server" with 3.0.0 so, fortunately, I still had the 2.3.2 installer so I reinstalled that and connection worked fine. So, there is something wrong with 3.0.0 (I do see that 3.0.1 is coming soon)

fwrightson · 11-21-2007, 11:10 AM

does installing the new server "fix" the connection problem with 3.0.0?

wadesworld · 11-21-2007, 11:55 AM

Quote:

o I reinstalled that and connection worked fine.

If the server you're connecting to is still on 2.3, then you need to stay with 2.3 until it changes.

Ezmerella · 11-21-2007, 01:33 PM

anyone know where i can download 2.3? can't find it anywhere.

Nirvana Soleil · 11-24-2007, 01:29 PM

Reloaded 2.3 since i got the error message with 3.0.0. Now I can't connect to the servers because they are all running in 3.3.0. Help!

Dragonstar · 11-24-2007, 09:29 PM

I currently have the same problem, I used 2.3, it worked perfectly as long as the server was setup for speex.

Downloaded 3.0 and it just doesn't work, it can't contact the server, i downloaded 2.0 prototype and it at least knew there was a server there to be contacted.

jakeisawesome · 12-01-2007, 02:18 AM

So I've done everything they've told me to do. I've opened up udp port 6100.
I've taken ventrilo off of MSconfig. Before I took it off of MSconfig it couldn't find the tcp packet...whatever that means. But now, it says "ready." But when I try to connect using my external IP, it still says contacting server.

So what else do I try now?

wadesworld · 12-01-2007, 02:49 AM

You don't connect using your external IP (assuming that you're talking about connecting to your own server). You connect using the internal IP of your server.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

11-18-2007, 09:49 PM	#21
wadesworld Senior Member Join Date: Nov 2005 Posts: 2,934	Did you try deleting the receipt package in /Library/Receipts?

11-21-2007, 11:08 AM	#23
fwrightson Junior Member Join Date: Nov 2007 Posts: 2	yes, I received the same msg "connecting to server" with 3.0.0 so, fortunately, I still had the 2.3.2 installer so I reinstalled that and connection worked fine. So, there is something wrong with 3.0.0 (I do see that 3.0.1 is coming soon)

11-21-2007, 11:10 AM	#24
fwrightson Junior Member Join Date: Nov 2007 Posts: 2	does installing the new server "fix" the connection problem with 3.0.0?

11-21-2007, 01:33 PM	#26
Ezmerella Junior Member Join Date: Nov 2007 Posts: 1	anyone know where i can download 2.3? can't find it anywhere.

11-24-2007, 01:29 PM	#27
Nirvana Soleil Junior Member Join Date: Nov 2007 Posts: 1	Reloaded 2.3 since i got the error message with 3.0.0. Now I can't connect to the servers because they are all running in 3.3.0. Help!

11-24-2007, 09:29 PM	#28
Dragonstar Junior Member Join Date: Nov 2007 Posts: 1	I currently have the same problem, I used 2.3, it worked perfectly as long as the server was setup for speex. Downloaded 3.0 and it just doesn't work, it can't contact the server, i downloaded 2.0 prototype and it at least knew there was a server there to be contacted.

12-01-2007, 02:18 AM	#29
jakeisawesome Junior Member Join Date: Nov 2007 Posts: 9	So I've done everything they've told me to do. I've opened up udp port 6100. I've taken ventrilo off of MSconfig. Before I took it off of MSconfig it couldn't find the tcp packet...whatever that means. But now, it says "ready." But when I try to connect using my external IP, it still says contacting server. So what else do I try now?

12-01-2007, 02:49 AM	#30
wadesworld Senior Member Join Date: Nov 2005 Posts: 2,934	You don't connect using your external IP (assuming that you're talking about connecting to your own server). You connect using the internal IP of your server.