Community AlphaAlpha MUADMINS
ITItaliano
Accedi
Su MuADMINSConfig ScannerCarica lo zip dei tuoi file: rates, drop, spot, limitiApriSu MuADMINSIncontraci su DiscordChiedi aiuto, condividi quello che stai creando e parla di MU con altri proprietari di server.Apri

MuADMINS

Soluzioni

Fix brevi per i problemi comuni di server, client e siti web di MU Online, ognuno con la sua fonte e la sua data. “Confermato” significa che chi ha fatto la domanda ha detto che il fix ha funzionato.

206 soluzioni per “disconnect” · Azzera

  1. Setup del server

    How to change the ConnectServer port 44405, and login fails after changing it

    1. Use the BoR Team ConnectServer, which has ini files with a port option, and set the new port there. 2. Put the same port in the launcher. 3. If login still fails, open MuServer\Connect...

    ✓ Confermato dall'autore della discussioneDarksTeam · 2010-12-21
  2. Setup del server97d+99i

    GameServer error at start with DarkMaster 97d+99i Beta 13 files, fixed by turning off the EventChip server connection

    1. Open Data\commonserver.cfg. 2. Find EventChipServerConnect = 1 and change it to EventChipServerConnect = 0. 3. Restart the GameServer.

    ✓ Confermato dall'autore della discussioneDarksTeam · 2011-04-23
  3. Sito web

    Website error "Fatal error: Call to undefined function mssql_connect()" (XAMPP 1.7.7, SQL Server 2008, DarksWeb 0.3)

    New XAMPP builds no longer have the mssql_* functions these old sites use. 1. Install XAMPP 1.7.1 (said to be the last one with mssql_*), or add code that defines those functions to the s...

    ✓ Confermato dall'autore della discussioneDarksTeam · 2019-02-07
  4. Sito webany

    WebEngine sidebar shows players online when nobody is connected

    The online count comes from MEMB_STAT, and some accounts stayed marked as connected there. 1. With the game server closed, clear the stuck online flag in MEMB_STAT (for example: UPDATE ME...

    ✓ Confermato dall'autore della discussioneTUServerMU · 2021-05-30
  5. Setup del serverIGCNS9

    IGCN S9 E2 repack: DataServer says 'Login failed for user ...' (SQLSTATE 28000) and 'DATA SERVER CANNOT CONNECT TO MSSQL'

    1. The repack DataServer config came with a SQL login that does not exist on your SQL Server (here a random name like D2a78Rtko0), so the login fails. 2. Open the database settings of the...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2019-07-14
  6. Setup del serverMuEmu / LouisS6

    MuEmu 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...

    ✓ Confermato dall'autore della discussioneTuServerMU · 2018-11-18
  7. Setup del serverAltri file0.99b

    On a 0.99b server the ConnectServer closes by itself when I replace the numeric IP with a No-IP hostname. Why?

    1. Old 0.99b ConnectServer builds only accept an address as long as a numeric IP. 2. Keep the hostname at 14 characters or less including the dots (the length of a full IPv4 address strin...

    ✓ Confermato dall'autore della discussioneTuServerMU · 2021-02-10
  8. Sito webany

    WebEngine 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...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2025-02-12
  9. Sito webS6

    WebEngine 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...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2023-10-06
  10. Setup del serverOpenMUS6

    OpenMU in Docker on Windows: the client sees the server list but is disconnected when joining a server.

    1. Use the client version the server targets (1.04d English, Season 6 E3). 2. Open the ports in the Windows firewall (and allow NAT edge traversal). 3. The connect server hands out the IP...

    ✓ Confermato nella issueGitHub (MUnique/OpenMU) · 2019-11-12
  11. Client di giocoSeason 6

    "Connect Failed" when you start the client on the PC that runs the server (No-IP address)

    With a No-IP (dynamic DNS) name in the client, players outside can connect, but the PC that runs the server often cannot, because most home routers do not route your public address back i...

    ✓ Confermato dall'autore della discussioneTUServerMU · 2021-04-15
  12. Sito webSeason 6

    WebEngine 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....

    ✓ Confermato dall'autore della discussioneTUServerMU · 2021-02-07
  13. Setup del server

    JoinServer and DataServer cannot connect to the database although the backup is restored

    These files had the database name MuOnlineS6 in the server configs while the database was restored as MuOnline, so the servers looked for a database that does not exist. 1. In SQL Server...

    ✓ Confermato dall'autore della discussioneTUServerMU · 2018-09-27
  14. Strumenti

    MuCore install: "Connection with MuOnline Database Failed" and "Extension php_mssql.dll must be enabled"

    1. MuCore needs a PHP that still has the old php_mssql.dll extension: in php.ini find extension=php_mssql.dll and remove the ; in front of it. 2. If your web server package has no php_mss...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2011-03-05
  15. Strumenti

    MuCore 1.08 installer: with the MSSQL connection it cannot get past step 3 (MSSQL 2008 R2, XAMPP 1.7.1)

    1. Use XAMPP 1.7.7 for MuCore 1.08 (XAMPP 1.7.1 with MSSQL 2008 works badly). 2. Install the client DLL that supports your MSSQL version (linked in the reply). 3. Open C:/xampp/php/php.in...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2016-05-26
  16. Strumenti

    MuMaker: "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection."

    1. The error means SQL Server only accepts Windows logins, so the sa login that MuMaker uses is refused. 2. Change the SQL Server authentication to SQL Server and Windows Authentication m...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2008-01-29
  17. Strumenti

    Real MU Launcher (open source): "no connection to the server" and then it does not update the client

    1. ServerURL must be a web address, not a folder on your PC: http://YOUR_WEB_IP_OR_DNS/path_to_update_folder/. A web server is needed (on a VPS or locally on your PC). 2. In Globals.cs se...

    ✓ Confermato dall'autore della discussioneRaGEZONE · 2024-12-29
  18. Setup del server0.97d

    97d GameServer on a VPS says 'Failed to connect to SQL Server' although the SQL login, the MuOnline database and the IPs look correct

    The database and the SQL settings were fine; the IP passed to GameServer.exe in its shortcut was the problem. 1. Right-click the GameServer.exe shortcut you start the server with and open...

    ✓ Confermato dall'autore della discussioneTUServerMU · 2021-02-08
  19. Setup del serverany

    ConnectServer and GameServer drop every few hours with WSASend error 10054 and protocol header errors once many players join.

    1. Check the real player limit of your files: these were built for 250 users, not 1000. 2. Above that number the server falls over. 3. Add a sub server (another GameServer) to spread play...

    ✓ Confermato dall'autore della discussioneTuServerMU · 2021-05-30
  20. Client di giocoOpenMUany

    OpenMU: I start main.exe with the ClientLauncher pointing to 127.0.0.1:44405 and nothing happens, the server never sees a connection.

    1. The original client refuses 127.0.0.1. 2. Use another loopback address instead, usually 127.127.127.127, with port 44405. 3. Set it in the ClientLauncher (or in main.exe with a hex edi...

    ✓ Confermato nella issueGitHub (MUnique/OpenMU) · 2019-02-15

MuADMINS Community Alpha: gratuito, fatto dalla community, in sviluppo attivo.