problems getting local LAN game of Doom2 going

General help and assistance forum.
Post Reply
thanosazlin
Registered just to make one post
Posts: 1
Joined: Tue Jan 15, 2019 2:17 pm

problems getting local LAN game of Doom2 going

#1

Post by thanosazlin » Tue Jan 15, 2019 2:26 pm

i am trying to setup a local multiplayer deathmatch between 2 computers. i was able to start a server on computerA then start offline doom2 and hit ~ and connect 192.168.44.1 , then hit spacebar etc.. and get in the match... i went to computerB which is also on my home network and started offline within Doomseeker, i got into doom2 hit ~ then "connect 192.168.44.1" and it just states "connecting to 192.168.44.1:10666" over and over, i can't ping 192.168.44.1 from computerB to computerA where the server is running on computerA... i can ping computerA's actual 192.168.1.x address fine... just looking for some help as to what i might be doing wrong here? below is my server config that is running on computerA, i tried disabling nortonAV as well.


=== Zandronum server ===
Running version: 3.0-r170901-1140
Started on 0/15/2019 at 9:19:51.

OS: Windows 8 (or higher) (NT 6.2) Build 9200

M_LoadDefaults: Load system defaults.
Using program directory for storage
Gameinfo scan took 0 ms
W_Init: Init WADfiles.
adding C:/Program Files (x86)/Zandronum/zandronum.pk3, 689 lumps
adding C:/Users/bencr/Desktop/test/DOOM2/doom2.wad, 2956 lumps
adding C:/Program Files (x86)/Zandronum/announcer/ZanACG.pk3, 104 lumps
adding C:/Program Files (x86)/Zandronum/announcer/ZanGeneric.pk3, 105 lumps
sv_maxlives will be changed for next game.
deathmatch will be changed for next game.
I_Init: Setting up machine state.
CPU Speed: 3492 MHz
CPU Vendor ID: GenuineIntel
Name: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
Family 6, Model 63, Stepping 2
Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
Using in-memory database. The database will not be saved on exit.
sv_rconpassword must be greater than 4 chars in length!
sv_joinpassword must be greater than 4 chars in length!
sv_password must be greater than 4 chars in length!
IPFileParser::parseIPList: could not open adminlist.txt: No such file or directory
IPFileParser::parseIPList: could not open whitelist.txt: No such file or directory
IPFileParser::parseIPList: could not open banlist.txt: No such file or directory
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
PWO_Init: Initializing preferred weapon order.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading default status bar definition.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
using alternate port 10666
player 1 of 1 (1 nodes)
Initializing network subsystem.
Server using alternate port 10666.
Winsock initialization succeeded!
IP address 192.168.44.1:10666
GeoIP initialization failed.
UDP Initialized.
NAT discovery error: Fail to find an UPNP NAT.


*** MAP01: entryway ***

compatflags changed to: 0
compatflags2 changed to: 0

User avatar
PirateofPC
New User
Posts: 2
Joined: Fri Jan 18, 2019 12:05 am
Location: Libya, Tripoli

Re: problems getting local LAN game of Doom2 going

#2

Post by PirateofPC » Fri Jan 18, 2019 12:48 am

I had the same issue, I fixed it by doing this:
  1. (in ComputerA): Open Doomseeker, and start server normally.
  2. (in ComputerB): Go to Options > Configure > Custom Server, then click Add, and type ComputerA IP "192.168.44.1".
  3. (in ComputerB): Click Get Servers Button, then you'll see two servers (the first one is Orange and the Second is Green) Right-Click on Orange Server then click Join.
That's it, I hope this fix it for you. :smile:

User avatar
Empyre
Zandrone
Posts: 1316
Joined: Sun Jul 08, 2012 6:41 am
Location: Garland, TX, USA

Re: problems getting local LAN game of Doom2 going

#3

Post by Empyre » Fri Jan 18, 2019 3:00 pm

thanosazlin wrote:
Tue Jan 15, 2019 2:26 pm
i am trying to setup a local multiplayer deathmatch between 2 computers. i was able to start a server on computerA then start offline doom2 and hit ~ and connect 192.168.44.1 , then hit spacebar etc.. and get in the match... i went to computerB which is also on my home network and started offline within Doomseeker, i got into doom2 hit ~ then "connect 192.168.44.1" and it just states "connecting to 192.168.44.1:10666" over and over, i can't ping 192.168.44.1 from computerB to computerA where the server is running on computerA... i can ping computerA's actual 192.168.1.x address fine... just looking for some help as to what i might be doing wrong here? below is my server config that is running on computerA, i tried disabling nortonAV as well.
Why are you trying to connect to 192.168.44.1 instead of computerA's actual address? Also, on computerA itself, why not connect to the loopback IP, 127.0.0.1?

Also, try PirateofPC's idea, but with the actual address of computerA on ComputerB, and 127.0.0.1 on ComputerA. Uncheck Broadcast to LAN when launching the server, then only the custom server you added in Step 2 will show up in Doomseeker.
"For the world is hollow, and I have touched the sky."

Juka
New User
Posts: 2
Joined: Tue Jan 22, 2019 1:16 pm

Re: problems getting local LAN game of Doom2 going

#4

Post by Juka » Tue Jan 22, 2019 1:26 pm

If everything fails, you can also create a public server for 2 and lock it with a password. I found out this is way easier to set up than a lan connection, and me and my brother experience 0 lag while playing a bunch of wads.

Post Reply