Holyblablabla
Member
- ServUO Version
- Publish 57
- Ultima Expansion
- Endless Journey
In recent days, I have tried various methods to connect to the LAN pub-57.4 ServUO server, but failed. The server host OS is Win 11.
The settings on the server host include assigning a fixed IP,192.168.3.90, to a server host in DHCP settings, adding inbound and outbound rules for 2593 port, turning off the Windows Defender, etc. Other computers in the LAN have successfully tested the connectivity of port 2593 using the test-NetConnection command in PowerShell. The ServUO.EXE runs smoothly and I can connect the server on server host by using Razor, "server 127.0.0.1 port 2593". However, my family members in LAN cannot connect by using Razor, "server 192.168.3.90 port 2593".
The Server.cfg is edited to
# The displayed name of the shard
Name=My Shard
# The internal IP address to listen on.
# You can leave this value as default to listen to all available IP's.
@Listen=0.0.0.0
# The public IP address to broadcast with the server list packet.
# If running from home, you can leave this value as default and connect locally.
# If your server is behind a DDoS shield provider, use the IP they assigned to you.
Address=192.168.3.90
# The Port to bind the Listener to.
# Default: 2593
@Port=2593
The story does not end. I downloaded, unzipped and compiled the Pub-master ServUO from github today. Without any modifications applied to the server.cfg file, I run the Compile.WIN - Release.BAT file and SerUO.EXE file. People in LAN connect this Pub-master server successfully!
Does anyone know what causes this difference? Is there anything I can do for people in LAN to connect the Pub-57.4 server? Thanks for any advice.
The settings on the server host include assigning a fixed IP,192.168.3.90, to a server host in DHCP settings, adding inbound and outbound rules for 2593 port, turning off the Windows Defender, etc. Other computers in the LAN have successfully tested the connectivity of port 2593 using the test-NetConnection command in PowerShell. The ServUO.EXE runs smoothly and I can connect the server on server host by using Razor, "server 127.0.0.1 port 2593". However, my family members in LAN cannot connect by using Razor, "server 192.168.3.90 port 2593".
The Server.cfg is edited to
# The displayed name of the shard
Name=My Shard
# The internal IP address to listen on.
# You can leave this value as default to listen to all available IP's.
@Listen=0.0.0.0
# The public IP address to broadcast with the server list packet.
# If running from home, you can leave this value as default and connect locally.
# If your server is behind a DDoS shield provider, use the IP they assigned to you.
Address=192.168.3.90
# The Port to bind the Listener to.
# Default: 2593
@Port=2593
The story does not end. I downloaded, unzipped and compiled the Pub-master ServUO from github today. Without any modifications applied to the server.cfg file, I run the Compile.WIN - Release.BAT file and SerUO.EXE file. People in LAN connect this Pub-master server successfully!
Does anyone know what causes this difference? Is there anything I can do for people in LAN to connect the Pub-57.4 server? Thanks for any advice.
