Quote:
Originally Posted by syko
Config your firewall to let paticular ip's connect, not very intelligent are you? lol
Printable View
Quote:
Originally Posted by syko
Config your firewall to let paticular ip's connect, not very intelligent are you? lol
I think all of above have some good parts, but nobody tells it all!
1) You have to make sure, that SP4 for SQL2000 is installed!
2) You have to configure your SQL server for remote access.
Its not the best idea to use port 1433. Many attacks which have nothing to do with MU are active on this port!
You can use port 2433 and HIDE your server. You have to configure this with the Server Network Utility from SQL 2000. Keep in mind to configure the TCP/IP Properties ^^!
3) After that, restart your sql server.
4) Start your Enterprise Manager and create a strong!! password for the sa login!
5) Create a new login, i.e. MuBoss, with a strong!! password and grant public and ownership to the db Muonline and Ranking.
6) Don´t use the sa user for any part of you muserver. Use the new "MuBoss"!
After that, restart your sql server.
Now you server is prepared for secure remote access to your sql database.
Client side:
Here you have 2 options:
A)
If you have sql client tools installed you can create a server alias with the Client Network Utility, i.e. MU-remote.
Rember, you have to configure the TCP/IP not named-pipe, etc...
(See picture), Unmark dynamic port detection and put port 2433 here.
This gives you the advantage to register your remote sql server, and you will gain access to you database with the enterprise manager and the query analizer.
You have to create a ODBC to access your remote server with MUEditor.
If you don´t know how to create an ODBC - check out the attached screens .....
Rember: User is "MuBoss", xxx.xxx.xxx.xxx is your global IP or in case of no-ip (Dyn.DNS) or similar, put your Dyn.DNS here. Check the client options and replace server name with your global IP or Dyn.DNS. Ckeck the port: make sure its 2433!
Finish the steps for creating the ODBC (checkout that you are connecting to the MuOnline database, and finish the ODBC.
Last thing: modify your ini file of the MuEditor, using your new created ODBC instead of MuOnline , MuBoss as user, and the databases Muonline and Ranking.
B)
If you dont have SQL client tools installed, just create the ODBC as discribed above. In this case MuEditor works fine, but you dont have the enterprise manger and query analizer remotely!
Now release port 2433 for TCP at you router (firewall). Blocking MS-SQLserver by your firewall make no sense. SQL needs to broadcast on your LOCAL network.
Some comments: Who says that you have to grant access to your sql server for everyone??? You will do this only for 1 or some special persons.
You will no publish your remote access, do you?? Not knowing the access and the strong!! password on a hidden SQL server, who will "hack" this??? Now you understand why NOT using the sa account!!
If your staff is not reliable, and giving secret informations away, this can be hardly controlled by an operating system. But this has nothing to do with attacks from hackers, lol!
-Element I'd like to inform you that your link for the mu editor download is dead and you should fix it.
i tought this guide never worked i tryed it right now and it didnt get some odcb error
Great Guide Man, im going to try it and see if it works with my data source problem...LOL
link dead how can i try this one.
hehehhe