MuADMINS
Mga Solusyon
Maiikling fix para sa mga karaniwang problema sa MU Online server, client at website, bawat isa ay may source at petsa. Ang ibig sabihin ng “Kinumpirma” ay sinabi ng nagtanong na gumana ang fix.
21 solusyon para sa “tcp/ip” · I-clear
After enabling TCP/IP in SQL Server for the web, DataServer, JoinServer and GameServerCS lost the database connection. How was it fixed?
1. In SQL Server Configuration Manager keep Named Pipes and TCP/IP enabled for the instance. 2. Open the ODBC DSNs used by the server files. 3. Change the Server field from the LAN IP to...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2020-05-23WebEngine CMS on a web host cannot reach the SQL Server on a VPS: 'Could not connect to database (1)', even after opening port 1433 in the firewall and enabling TCP/IP.
1. Check the usual items first: inbound rule for TCP 1433 in Windows Defender Firewall on the VPS, TCP/IP enabled in SQL Server Configuration Manager. 2. If it still fails, test whether t...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2025-02-12MuMaker 1.12: "No connection could be made because the target machine actively refused it, error 0" or "error 40" when connecting
1. Open SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for MSSQLSERVER. 2. Set TCP/IP to Enabled. 3. In TCP/IP Properties, IP Addresses tab: set Enabled t...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2017-08-08IGC.EssentialTools crashes after the first-run notice although SQL named pipes and TCP/IP are enabled (crash dump in CrashDumps)
1. Symptoms: the first-run notice pops up, then the tool crashes on every start; compatibility mode and run as admin do not help; a dump such as IGCN.EssentialTools.exe.5908.dmp appears i...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2020-01-05MuEditor on the host PC cannot connect to the SQL Server that runs inside a local virtual machine
1. In SQL Server Configuration Manager inside the VM enable TCP/IP (and Named Pipes), restart the SQL service and allow port 1433 in the VM firewall. 2. In the editor config fill both blo...
✓ Kinumpirma ng nagsimula ng topicTUServerMU · 2019-11-24IGCN Season 12: DataServer is not responding although TCP/IP is enabled in SQL Server
1. Open DataServer.ini and check SQLServerName. 2. When SQL Server runs on the same machine use SQLServerName = (local) or the exact PC name as shown in SQL Server Management Studio (for...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2020-01-08MuEmu S4: the server and MuMaker do not see the databases on SQL Server 2008 R2 even with remote connections and TCP/IP enabled.
1. Check how SQL Server was installed: it had been set up as a named instance. 2. The files and MuMaker expect the default instance, reached as (local) or the PC name. 3. Reinstall SQL Se...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2017-11-11IGCN Essential Tools (S9 E2 repack) shows an error pop-up as soon as it is opened.
1. Open SQL Server Configuration Manager > SQL Server Network Configuration > Protocols. 2. Enable Named Pipes and TCP/IP. 3. In TCP/IP properties > IP Addresses set TCP Port 1433 (IPAll)...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2018-06-18MuMaker: cannot connect to SQL Server 2005 Express (SQLEXPRESS)
1. Open SQL Server Configuration Manager, then Protocols for SQLEXPRESS. 2. Right click TCP/IP, Properties, set Enabled to Yes. 3. In the IP Addresses tab set Active and Enabled to Yes fo...
Remote tools or the web cannot reach a SQL Express or named instance on port 1433. How do I make SQL listen on a fixed port?
1. Named instances use dynamic ports by default; only the default instance uses 1433. 2. SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for your instance...
WebEngine on shared hosting cannot reach SQL on my VPS. Port 1433 is open and MuMaker connects from home, but the web install still fails.
1. The hosting company may block outgoing traffic to port 1433. 2. In SQL Server Configuration Manager > TCP/IP > IP Addresses > IPAll set TCP Port to another free port and leave TCP Dyna...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2020-05-23Two servers (x100 and x10) on two different VPS: the client only shows one of them in the server list
1. Let one ConnectServer (on VPS 1, the machine that runs the full server) send the server list for both: add both GameServers to its server list with their server code, IP and port. 2. G...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2024-12-10MuMaker 1.13: "Format of the initialization string does not conform to specification starting at index 30" when connecting to SQL
1. Check that SQL Server has TCP/IP enabled on port 1433 and that port 1433 is allowed in the Windows firewall; check the ODBC source and the MuMaker config. 2. Make sure .NET Framework 3...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2025-04-30X-Team MuEmu S8E3: players cannot get in because Mu Hack Protection shows an error, even with the usual ports open.
1. Open the MHP port 55999 TCP in the firewall and router, besides 44405 (ConnectServer), 55901 (GameServer) and 55919 (GameServer CS). 2. Port 55557 does not need to be opened. 3. Check...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2017-04-21MuEmu S6 on a VPS: the client works inside the VPS, but from home it shows the antihack logo, says it could not connect and closes.
1. When it works on the VPS itself but not from outside, the Windows Firewall of the VPS is the usual cause. 2. On the VPS, create inbound TCP allow rules for the ConnectServer port (4440...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2018-11-18MuCore on a web host cannot connect to the MuOnline database on a Google Cloud VPS (Connection with MuOnline Database Failed), although 1433 is open in Windows.
1. Enable TCP/IP and Named Pipes for the instance in SQL Server Configuration Manager and restart SQL. 2. Open TCP 1433 in the Windows firewall of the VPS. 3. Also open TCP 1433 in the cl...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2019-03-17MuCore 2.2.0 installer stops with 'SQL Failed' at the connection step.
1. Open TCP port 1433 in the Windows firewall. 2. In SQL Server Configuration Manager enable Named Pipes and TCP/IP, set IPAll TCP Port 1433. 3. Restart SQL Server and run the installer a...
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2019-07-27MuCore on XAMPP on the same VPS as SQL Server cannot connect to the database.
1. Easiest: in the MuCore config.php change the connection type from MSSQL to ODBC. 2. Or open SQL Server Configuration Manager, enable TCP/IP and Named Pipes, and restart SQL Server. 3....
✓ Kinumpirma ng nagsimula ng topicTuServerMU · 2017-12-27WebEngine CMS install keeps saying 'Could not connect to database (1)' with SQL Server 2008 and XAMPP (PDO ODBC), even though SSMS connects fine.
1. The thread found a conflict between SQL Server 2008 and WebEngine's connection. 2. Install a newer SQL Server (2012 worked for the topic starter; another user had 2019 working). 3. Res...
✓ Kinumpirma ng nagsimula ng topicRaGEZONE · 2023-10-06WebEngine on web hosting says "Could not connect to database (1)"
Shared web hosting often blocks outgoing connections to port 1433, the default SQL Server port, so the website cannot reach the database on your VPS even when tools on your own PC can. 1....
✓ Kinumpirma ng nagsimula ng topicTUServerMU · 2021-02-07