Author Topic: build requirement command and WSAECONNRESET issue  (Read 1009 times)

Herron

  • VM-68
  • Posts: 235
build requirement command and WSAECONNRESET issue
« on: September 10, 2007, 07:16:34 AM »
two questions:

1.  i thought there was a settable server command to require client versions ### and up (i.e., build 19)... am i incorrect? if not, what's the command?

2.  any clue how to fix this?
[06:24:17] Sending heartbeat to 192.246.40.37:27900
[06:24:17] Sending heartbeat to 70.85.9.178:27900
[06:24:17] Sending heartbeat to 207.38.11.34:27900
[06:24:17] NET_GetPacket: WSAECONNRESET from 192.246.40.37:27900
[06:24:17] Heartbeat acknowledged from 70.85.9.178:27900

* Dns resolved 192.246.40.37 to satan.idsoftware.com
it's been going on for a week, but i've been too lazy to address it until now.  i use:  setmaster dplogin.com master0.gamespy.com

KiLo

  • Autococker
  • Posts: 2086
Re: build requirement command and WSAECONNRESET issue
« Reply #1 on: September 10, 2007, 07:30:18 AM »
1. Hm I believe it is cvar_set minclientbuild <build # here>.
     There is also a place in the server config to set it.

2. Does the server still appear on the list? If so it really doesn't matter.
     Also I'm going to search around the forum because I posted a topic with the same error.

Herron

  • VM-68
  • Posts: 235
Re: build requirement command and WSAECONNRESET issue
« Reply #2 on: September 10, 2007, 07:39:47 AM »
good call, it's sv_minclientbuild -- thanks

yes, the server still shows up in the list (for the dp browser at least) -- i don't know about all-seeing eye, as i got impatient and added the ip manually since ASE only seems to completely update the server list once a day for me

jitspoe

  • Administrator
  • Autococker
  • Posts: 18802
Re: build requirement command and WSAECONNRESET issue
« Reply #3 on: September 14, 2007, 01:11:28 PM »
The id master server is hard coded.  I guess I need to take that out if it's not working.