autoexec is too late, it's executed after initialization. Put them in a config that is +exec'ed on the command line and it should work fine.
If that's true, then what is happening here?
Command line:
r1q2.exe +exec setnet.cfg +set dedicated 1 +set sv_gamedebug 1 +set game lox +exec testserver.cfg
setnet.cfg:
set ip 192.168.1.50
set port 27913
set public 1
Winsock Initialized
====== Quake2 Initialized ======
R1Q2 build 7322, compiled Apr 10 2007.
http://www.r1ch.net/stuff/r1q2/Win32 RELEASE x86 (r1q2.exe)
exec <filename> : execute a config file
...
Result:
r1q2.exe:2284 UDP 0.0.0.0:27910 *:*
Better off telling them to put it in the command line.
I have been down this road in Linux and Windows and it only works in the command line. All other methods are either ignored or generate error messages.