Viewing Article

No StarNo StarNo StarNo StarNo Star | Jun 25 2009, 10:23 PM | Print
Network Connectivity Issues
Network Connectivity Issues

Diagnosing network connectivity issues can be difficult, but there are some basic troubleshooting steps. Error codes 90, 91 and 106 always indicate a problem with internet connection. For a list of error codes and a technical description, please see the end of this article; otherwise, please continue reading for trouble-shooting tips.

Network Check
Please see the following KB article for instructions on how to perform a network analysis and report:
https://support.istaria.com/index.php?act=article&code=view&id=80

Wireless Networks
  • Wireless routers that are very close to cable modems and / or your computer can cause irregular signals resulting in dropped connections.
    • the wireless router should be as far as possible from the cable modem, with a minimum of three feet (1 meter)
  • Your wireless router and computer should be at least 3 feet (1 meter) from any other wireless device (this includes Wifi cell phones, wireless routers, Skype phones, other computers, etc.).
  • If your computer is greater than 100 feet (30 m) from the wireless router, try moving them closer together.
  • Ensure that there are no very solid objects between you and the wireless router. For example, concrete floors and iron safes could cause problems.
  • Ensure that there are no highly reflective surfaces, such as mirrors, windows, metal, and steel close to your router. These surfaces can cause signal reflections which greatly degrade your signal.
  • Try using a wired connection; if doing so resolves all issues, you have confirmed the problem is the wireless connection.
Firewall Configuration

Please see this Knowledge Base article for settings and help troubleshooting firewall setup.
https://support.istaria.com/index.php?act=article&code=view&id=40

Spyware and Other Applications
  • Some applications can interfere with Istaria connection to the servers - SpyWare and Ad dishing programs can cause problems. Ad-Aware does a great job checking for problems: www.lavasoftusa.com
  • Close all other programs that access the internet.
  • Malware, adware, some firewalls and other software can hook into the Windows communication layer (WinSock) and cause connection problems. Make sure that all network related applications, such as firewall, instant messaging, and browsers are up-to-date. If the problem still persists, you can attempt to diagnose and repair the problem manually.
Specific Error Codes and their Meaning
Error ID:  90
Enum:  DisconnectReason::REQUESTED_DISCONNECT
Message:
The client has been disconnected because it requested the connection be terminated.
Details:
This is a normal termination. The client asked to be logged out.

Error ID:  91
Enum:  DisconnectReason::COMM_FAILURE
Message:
The client has been disconnected because of a communications failure. Please wait a few minutes and try again. If you are still unable to connect, please open a case at https://support.istaria.com under the category "Connectivity."
Details:
This is 'link death.' It could be the result of a communication problem, firewall configuration, or the player server crashed. In addition, any other id besides 90 may end up becoming this one.

Error ID:  92
Enum:  DisconnectReason::FORCED_DISCONNECT
Message:
The client has been disconnected by the accounts database. Please wait a few minutes and try again. If you are still unable to connect please open a case at https://support.istaria.com.
Details:
The accounts database is allowed to disconnect a current connection when it authenticates.

Error ID:  93
Enum:  DisconnectReason::DISCONNECTED_BY_PEER
Message:
The player server has disconnected the client. The most likely reason is a communications failure. Please wait a few minutes and try again. If you are still unable to connect please open a case at https://support.istaria.com.
Details:
The player server has disconnected the player terminal for some undefined reason. The most common reason is because the player server encountered a communication failure attempting to send messages to the player terminal.
 
Error ID:  104
Enum:  DisconnectReason::CS_FORCED_DISCONNECT
Message:
An administrator has disconnected the client. 
Details:
Someone used cs_admin to terminate this connection.

Error ID:  105
Enum:  DisconnectReason::DISCON_DUE_SHUTDOWN
Message:
The client has been disconnected because the player server has been shutdown. Please wait a few minutes and try again. If you are still unable to connect please open a case at https://support.istaria.com.
Details:
The player server was shut down.

Error ID:  106
Enum:  DisconnectReason::MAX_RESENDS
Message:
The client has been disconnected because of a communications failure. Please wait a few minutes and try again. If you are still unable to connect please open a case at https://support.istaria.com under the category "Connectivity".
Details:
This error only occurs if a reliable message could not be sent. It separates the most common communications failure from the general case. This solves the problem that while all network problems appeared as a communications failure, not all communication failures were the result of a network problem.

Error ID:  108
Enum:  morley::DISCONNECTED_BY_SIMULATION
Message:
The client has been disconnected at the request of the simulation. Please wait a few minutes and try again. If you are still unable to connect please open a case at https://support.istaria.com.
Details:
The simulation has requested that the connection be terminated. The simulation's explanation may be available if the message arrives before the disconnection.
 
Error ID:  109
Enum:  morley::DISCONNECTED_BY_SERVER
Message:
An error occurred while thawing the requested biote. Please wait a few minutes and try again. If you are still unable to connect please open a case at https://support.istaria.com.
Details:
The user's biote caused an exception on the server while thawing. When this happens the biote is frozen, and the terminal disconnected. The most likely cause for this is a callstack in the simulation code. This will be logged, and a world administrator should be able to retrieve the necessary information.