[SQL / AUTH] Issue

Joined
Oct 21, 2006
Messages
1,165
Reaction score
29
Well, me and blazin want to open a server, blazin has all the requred things for the server, box, site, files blah blah blah... but we want to mod some shit, we have both run into a problem with the "Log In" button...

now im trying to make a server on my comp for 127.0.0.1 to make and test files, no online shit..

i have used 4 differant DB/AUTH and. vladi / kalmax / ceph files, reinstalled sql with and without passwords, followed guides to making it to see if i missed anything.. but i cant see it.

now, after installing all correctly, by following tutorial step by step guild, i boot up db/auth/main, all runs smoothly, i can connect Local Server.. type in my id pass, hit enter.. bam, doesnt do anything

some have said this is to do with "kocp"
i used files b4 aylen had thought of this protection and still same issue.

Could this be something to do with SQL?
Could this be something to do with IP settings?

oh and all are unblocked through firewall, had network cable out, all protection off/snoozed, nothing could of blocked it, still wont allow me in.
i also allowed ports 29999 ~ 50999.. same problem, im sure the answer would be written somewhere between the lines of a thread, but i cant find it.

Thanks
Stup
 
btw this problem happened to me
the server was running on the root normally
then without changing any thing when i hit the log in button nothing happens so
i was so depressed and stopped the server although it was about to be online
but many ppl say it is kocp problem but i have the old kocp which was running without license
 
Upvote 0
try this on you pc ,
install a second instance of the sql2005 with password and give it a name,
then when you setup the odbc where you would put the (local)
put YOURCOMPUTERNAME\YOURKALSERVER ,same as it shows in the sql manager
then for the ip's
make the client not going to 127.0.0.1 , but insted make it going to you isp ip
now routing ,
1st right click your network connection and see what local ip your router is giving it
then
(in this example im assuming your local ip is 192.168.1.100 and mainserver port is 30001)

in router on the port forwarding page, make
|app name mainsvr | in - from 30001 to 30001 | ip 100 | activate (and a check box)

that will send incoming coections looking for port 30001 to your pc
there should be another page for port triggering ,
on that page you can set incoming on 1 port
and make it direct you to another port b4 your ip
more secure to use but client will come in to different port to what server is on

ppl will tell you to turn of the firewall in router and
there may be a check box for "Block annonomose incoming blaa blaa"

dont turn of the firewall but if all else fails uncheck that other thing and see if it works


if this dont help post again
as for your ded/root svr i dont know, why pay more



.
 
Upvote 0
Back