@nephilim: not tempted to re-install now there's the opportunity to re-buy old cod4 maps at silly prices - that said i was hovering over the 'buy' button last night...
Sounds worth a visit, will have to see if I can convince the better half that its a worthwhile investment (rather than squander the cash on kids shoes etc...)
haha - "medic who can revive recently-killed comarades," isnt that called a witch doctor?
Hi Brett,
Strange - If when you ran dbupgrade and the server and database names weren't populated it means it hasn't been able to get the details from your 'central' connect.ini. (even on a re-direct it should pick them up).
But then again it must be finding something when you run sims.net or you'd get a 'incorrect connect.ini error' rather than a reason 0. (just tried it out)
Might be worth trying to take the 'connects' out the equation and copying the [sIMSCONNECTION] details out of the central connect.ini so that the copy local to SIMS .net contains the 'ServerName' and 'DatabaseName' values.
Then try juggling round with IP/machine names in the connection details.
Something to try that might help diagnose the problem would be running the copy of dbupgrade that sits in the SIMS.net folder.
If the SQL Server details are being read in correctly from the connect.ini then they'll be filled in on the login screen so they can be checked.
DBUpgrade will also let you enter your sa user name and password so you can check if its just a problem with the SIMS logins as well.
It might help take a few other things out of the equation.