Connection Failed

Newbie Spellweaver
Joined
Jan 30, 2008
Messages
5
Reaction score
1
Guys, in my life I have already made three perfectly working Priston Tale servers on my old computers, but now I simply CAN'T MAKE THIS WORK.
No matter which combination of server/client files I use, I'll always get "Connection Failed" when I enter my ID and click Login.
I've extensively searched for answers for the past whole week and I have gotten nowhere so far.

My computer is running Windows 7 Ultimate (which I just reinstalled), I'm using SQL 2005 SP3 and I'm sure I'm doing everything right, having tested many repacks, like FusionPT, the original backup_carten files and even my old backups.

I won't post my hardware for I believe it's irrelevant.

I ask you for help, if possible. Thank you in advance.
 
That won't work... Windows 7 comes with SQL 2008, you can't DOWNGRADE it to SQL 2005. SQL 2008 is quite difficult to get to work with PT.

Also... if you are running the x64 version of Windows, you can't run the server on that... My advise is, set it up in a Win2k / 2k3 server VirtualMachine.

PT (in all) really doesn't support OS over Windows XP, the client can work in Vista or Windows 7 (with XP compatibility mode) and many of the UAC breaking DEP crashing and memory snooping code and missing security manifest can be "fixed", but it really isn't designed for it.

The server just isn't going to be happy. It still runs sweet on NT4... That's the system it's built to target. But that's not great if you run the ASP.net on it, and if you can find hardware that NT4 supports available that isn't second hand you will be doing well. (Up to 8 single core CPUs below PII / K6, ISA or PCI without Plug'n'Play, jumpered ISA / VLB PATA / SCSI2... not easy to do.) Windows 7 is really pushing it.

If you have a copy of NT4 Server, (or Workstation) you can set that up on a VM, and run the ASP on your Windows 7 machine... NT4 install is smaller than 2k or 2k3, and it runs really fast and stable under a VM, your only using it as a single Virtual Appliance.
 
Yes, I use Windows 7 Ultimate x64... Thank you for the info. I'll work on downloading one of the mentioned versions them I'll get back to you. Thank you very much, bobsobol.
 
You can run on Virtual Machine under x64... if the WOW64 system is sufficient to run x86 version of SQL server then you may well get away with it... (my experience of WOW64 prior to Vista was poor, but MS SQL is an MS product so YMMV there)

If you run Windows XP / Server 2003 x64, then you can install the x86 version of SQL 2005... You could possibly create a cut-down Windows 7 as an OEM installation (via WIAK or such) without the SQL 2008 x64/.net that is usually built into Windows 7 to aid it's new file search engine and work around it that way... but you would loose most of what makes 7 different to Vista.

You can run the server on Vista / Server 2008 x86, and therefore should be able to run it on Vista x64 if you install the x86 version of SQL Server 2005 (or lower) as opposed to the normally recommended x64 version.

It's not the OS version that is the problem, it's the SQL version... it only becomes an issue in Windows 7, because a limited version of MS SQL is included in that OS which is already too new, and (if you use the x64 variant of the OS) running on a different platform to the x86 virtual machine that the PT server runs in.

So moons' response is an over-simplification, and would possibly be moderated to "PT server + 64bits OS = VERY HARD TIME Hacking you OS to force it to work" but that is likely to promote unfounded hope... Kinda like the cancer patient who is offered a 10% survival probability from treatment.

The simple answer is, use an older OS, and stick to x86 to make your life 100% easier. :wink: If you think about it, WOW64 (the sub-system in x64/AMD64 builds of the Windows OS which allow you to continue to run x86/32-bit applications) is a VM anyway, why not complete the job, separate your main OS from your Server system and save your self a hell of a lot of headache? Just my humble opinion.
 
Last edited:
now, i am using Windows 7 Ultimate 64
AND WITH Sql express 2005
running well with pt...
check all of ur configs ^^
dont have any away to it be wrong, for me is working ^^

@bobsobol , u can use win7 with SQL 2005

see :
Volcano - Connection Failed - RaGEZONE Forums
 
Last edited:
And it didn't work here. I downloaded a virtual Windows 2003 Server R2, updated it, installed SQL 2005 then the Studio and updated both to SP3, redid everything and I still can't connect.
 
@microamazing
Hmm... I got MS-SMS 2005 running on MS-SQL 2008 when I tried it. The older Management Studio worked on the newer SQL server... still x64, and that seems to be the problem for a lot of people. I suspect that if you only access via ODBC, (no clan and SOD scores) and you don't have the "too fast a CPU hitting the ODBC connection" issue, then you are probably okay... of course the PT sql.dll is 32-bit, and cannot communicate with 64-bit APIs, but ODBC can connect via TCP / named pipes (though the later is still rather more flaky) which should be fine.

I have no practical experience in attempting this, but my understanding suggests it should be possible.

Anyway, it's nice to see that it is still possible to run a PT server on Win7 x64. I managed on Vista x64, but I know others who have had to give up on 2003 x64... so mileage will vary, but it definitely gets more pitfalls the further you deviate from Win2K Server, which IMHO is about the ideal for PT.

@Volcano
If you still cannot connect with a VM server, then your problem is different. Assuming that you remembered that you have to use the LAN IP of the virtual machine and not localhost (127.0.0.1), and the LAN link is working on the VM... Bridged / NAT or even host only if you are only playing on the VMs host.

So now you are down to the usual simple things... check the ports of the client and server are the same, check they use the same protocol (encryption), check the firewall, check the router, check the SQL.dll and ODBC setup, and the usual settings in the registry and ini files.
 
Back