|
|
 |
 |
 |
 |
|
 |
 |
|
 |
 |
|
 |
|
Support::Windows Servers Support forum for Windows EQEMu users. |

09-30-2008, 11:49 PM
|
Hill Giant
|
|
Join Date: Jan 2007
Posts: 124
|
|
Oops, come to think of it I have always setup minilogin first then attempted to setup the public afterward. I guess my ports have already been open.
What server is it, Skizoke? I'll try to login and see what happens.
__________________
Syl
"The significant problems we have cannot be solved at the same level of thinking with which we created them."
Albert Einstein
|

10-01-2008, 12:08 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
Skizoke Test Server
|
 |
|
 |

10-01-2008, 12:10 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
Here is the way my eqemu_config file currently looks:
<?xml version="1.0">
<server>
<world>
<shortname>Skizoke</shortname>
<longname>Skizoke Test Server</longname>
<!-- Only specify these two if you really think you need to. -->
<address>74.185.XX.XX</address>
<localaddress>192.168.1.68</localaddress>
<!-- Loginserver information. -->
<loginserver>
<host>eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver>
<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>some long random string</key>
<!-- Sets the ip/port for the tcp connections. Both zones and console (if enabled). Defaults are shown -->
<!-- <tcp ip="localhost" port="9000" telnet="disable"/> -->
<!-- Enable and set the port for the HTTP service. -->
<http port="9080" enabled="true" mimefile="mime.types" />
</world>
<!-- Database configuration, replaces db.ini. -->
<database>
<host>localhost</host>
<port>3306</port>
<username>root</username>
<password>******</password>
<db>peq</db>
</database>
</server>
|
 |
|
 |

10-01-2008, 12:24 AM
|
Hill Giant
|
|
Join Date: Jan 2007
Posts: 124
|
|
Skizoke, This was in my Titanium log file.
Code:
2008-09-30 23:07:33 Networking: Connection Established [1]
2008-09-30 23:08:33 *** WorldAuthenticate. Error connecting to 74.185.XX.XX:9000 [client:DisconnectReasonConnectFail,server:DisconnectReasonNone]
2008-09-30 23:08:33
2008-09-30 23:08:33 Networking: Connection Closed [0] with 0 pending bytes.
2008-09-30 23:08:34 *** ERROR: WorldAuthenticate has failed after attempting to connect.
First try commenting these lines in your eqemu_config file:
<address>74.185.XX.XX</address>
<localaddress>192.168.1.68</localaddress>
Second try this, note I don't even have this line in my eqemu_config file:
Try uncommenting this line from your eqemu_config file:
<!-- <tcp ip="localhost" port="9000" telnet="disable"/> -->
__________________
Syl
"The significant problems we have cannot be solved at the same level of thinking with which we created them."
Albert Einstein
|
 |
|
 |

10-01-2008, 12:29 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
I made the changes, currently looks like this:
<?xml version="1.0">
<server>
<world>
<shortname>Skizoke</shortname>
<longname>Skizoke Test Server</longname>
<!-- Only specify these two if you really think you need to. -->
<!-- <address></address> -->
<!-- <localaddress></localaddress> -->
<!-- Loginserver information. -->
<loginserver>
<host>eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver>
<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>some long random string</key>
<!-- Sets the ip/port for the tcp connections. Both zones and console
(if enabled). Defaults are shown -->
<tcp ip="localhost" port="9000" telnet="disable"/>
<!-- Enable and set the port for the HTTP service. -->
<http port="9080" enabled="true" mimefile="mime.types" />
</world>
<!-- Database configuration, replaces db.ini. -->
<database>
<host>localhost</host>
<port>3306</port>
<username>root</username>
<password>******</password>
<db>peq</db>
</database>
</server>
I don't know how to actually restart the server. I have just been closing the two dos windows. I am just now thinking, maybe changes to my config file are not taking effect if I am not restarting correctly?
|
 |
|
 |

10-01-2008, 12:35 AM
|
 |
Developer
|
|
Join Date: Aug 2006
Location: USA
Posts: 5,946
|
|
Ya, you are restarting it correctly for Windows. It should be taking effect.
Try running an "ipconfig /all" from your command prompt and post that here if you don't mind.
|
 |
|
 |

10-01-2008, 12:38 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
Here you go:
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Howard>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Howard-Main
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
it Ethernet NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1D-7D-E6-C3-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::880d:1656:1fd7:30f2%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.68(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, September 30, 2008 9:53:12 PM
Lease Expires . . . . . . . . . . : Wednesday, October 01, 2008 9:53:12 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 134225277
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Hamachi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 7A-79-05-FF-58-F2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 5.255.88.242(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Lease Obtained. . . . . . . . . . : Tuesday, September 30, 2008 9:53:12 PM
Lease Expires . . . . . . . . . . : Tuesday, September 30, 2008 11:36:57 PM
Default Gateway . . . . . . . . . : 5.0.0.1
DHCP Server . . . . . . . . . . . : 5.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 6:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{734CDEE7-51F1-4667-B432-C91DAB389
B7E}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::200:5efe:5.255.88.242%12(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : isatap.gateway.2wire.net
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.68%10(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 10:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Temporary IPv6 Address. . . . . . : 2002:5ff:58f2::5ff:58f2(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Users\Howard>
|
 |
|
 |

10-01-2008, 12:52 AM
|
Hill Giant
|
|
Join Date: Jan 2007
Posts: 124
|
|
I am still getting the same error when trying to connect. It seems like port 9000 is blocked. Double check all the port openings in your router with what Trevius suggested earlier.
And even though I don't think this has anything to do with it, I'd turn off Hamachi until you get the server working.
Assuming that the ports are open correctly this could be a routing issue, and Hamachi could interfere.
__________________
Syl
"The significant problems we have cannot be solved at the same level of thinking with which we created them."
Albert Einstein
|
 |
|
 |

10-01-2008, 01:04 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
Quote:
Originally Posted by Sylaei
Skizoke, This was in my Titanium log file.
Code:
2008-09-30 23:07:33 Networking: Connection Established [1]
2008-09-30 23:08:33 *** WorldAuthenticate. Error connecting to 74.185.XX.XX:9000 [client:DisconnectReasonConnectFail,server:DisconnectReasonNone]
2008-09-30 23:08:33
2008-09-30 23:08:33 Networking: Connection Closed [0] with 0 pending bytes.
2008-09-30 23:08:34 *** ERROR: WorldAuthenticate has failed after attempting to connect.
First try commenting these lines in your eqemu_config file:
<address>74.185.XX.XX</address>
<localaddress>192.168.1.68</localaddress>
Second try this, note I don't even have this line in my eqemu_config file:
Try uncommenting this line from your eqemu_config file:
<!-- <tcp ip="localhost" port="9000" telnet="disable"/> -->
|
The titanium log file? Where is it located and what is the exact name?
I see zone logs and debug logs, just not sure which one you are referring to.
|
 |
|
 |

10-01-2008, 01:06 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
Here is a screenshot of the way I forwarded the ports:

|

10-01-2008, 01:18 AM
|
Hill Giant
|
|
Join Date: Jan 2007
Posts: 124
|
|
It is under my Everquest Titanium folder.
Like: c:\games\eq titanium\logs
the file itself is named dbg.txt
In the screen shot you are just opening the ports in your firewall, you need to foward those ports to your eqemu server. If you forward I don't think you need to open them in the firewall.
What is happening without the forwarding turned on is that my request to authenticate is happening at the router not your eqemu server. The router knows nothing of my auth request and is ignoring it.
__________________
Syl
"The significant problems we have cannot be solved at the same level of thinking with which we created them."
Albert Einstein
|
 |
|
 |

10-01-2008, 01:26 AM
|
Sarnak
|
|
Join Date: Sep 2008
Location: Alabama
Posts: 70
|
|
This is what the router page says:
By default, the firewall blocks all unwanted access from the Internet. You can allow access from the Internet to applications running on computers inside your secure home network by enabling firewall pinholes. Opening firewall pinholes is also known as opening firewall ports or firewall port forwarding. To do this, associate the desired application with the computer below. If you cannot find a listing for your application, you can create a user-defined application profile. (To create a user-defined profile, you will need to know protocol and port information.)
To Allow Users Through the Firewall to Hosted Applications...
Select a computer
Choose the computer that will host applications through the firewall: Howard-Main 192.168.1.64 junkonecom-PC shaunda DIRECTV-STB-DF5BF5EA Howard
Edit firewall settings for this computer:
Maximum protection – Disallow unsolicited inbound traffic.
Allow individual application(s) – Choose the application(s) that will be enabled to pass through the firewall to this computer. Click ADD to add it to the Hosted Applications list.
All applications Games Audio/video Messaging and Internet Phone Servers Other User-defined Hosted Applications:
EQEmu
• Add a new user-defined application
Allow all applications (DMZplus mode) – Set the selected computer in DMZplus mode. All inbound traffic, except traffic which has been specifically assigned to another computer using the “Allow individual applications” feature, will automatically be directed to this computer. The DMZplus-enabled computer is less secure because all unassigned firewall ports are opened for that computer.
Note: Once DMZplus mode is selected and you click DONE, the system will issue a new IP address to the selected computer. The computer must be set to DHCP mode to receive the new IP address from the system, and you must reboot the computer. If you are changing DMZplus mode from one computer to another computer, you must reboot both computers.
On the far left of the screenshot is the server name, it is allowing access to the server on those ports. Does it appear to you it is not being forwarded? If so, I am unsure how to fix it.
|
 |
|
 |
Thread Tools |
|
Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -4. The time now is 01:58 AM.
|
|
 |
|
 |
|
|
|
 |
|
 |
|
 |