Setting up a server
I can't find a server setup guide anymore on the site. Any help is appreciated. I have access to a 1.5Mbps/864Kbps Win2k3 server, courtesy Beauty@PK.
Things I've done so far -
1. Installed the normal server pack with register as service.
2. Tried using AGM to setup a public game, it says it cant connect to the lobby.
3. Tried manually starting the service, then using AGM - no dice.
This is the normal server though. I still havent applied the dplay8 exes.
Help?
Things I've done so far -
1. Installed the normal server pack with register as service.
2. Tried using AGM to setup a public game, it says it cant connect to the lobby.
3. Tried manually starting the service, then using AGM - no dice.
This is the normal server though. I still havent applied the dplay8 exes.
Help?
The dplay8 code uses a completely different method of connecting to the lobby, so the regular serverpack won't get you in.
There are problems with the existing serverpack, but the lastest exes are available here: http://fazdev.alleg.net/FAZ/allsrv_md_dplay8.zip
--TE
There are problems with the existing serverpack, but the lastest exes are available here: http://fazdev.alleg.net/FAZ/allsrv_md_dplay8.zip
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
Dang, Tiger beat me to it. But I think ImmortalZ is asking about a live server.
You should keep it registered as a service (allsrvUI has some issues with the latest servers). AGM is outdated, I wouldn’t use it.
The server gets its settings from the registry. The keys are in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0\Server. If you’re using a beta server, it’s in 1.1.
The important values are:
ArtPath: The path of your server’s artwork directory.
CfgFile: The path of the configuration file. For the live servers, it’s http://autoupdate.alleg.net/allegianceserver.cfg. For the beta servers, it’s http://fazdev.alleg.net/FAZ/FAZ.cfg.
EXEPath: The path of your server’s exe file. Server logs will end up here.
Core1: The name of the core file for that game (without extension).
Game1: The name of the game in the lobby.
You can have a core2/game2, core3/game3 etc for multiple games on the server.
You need port 46724 and 2300-2400 forwarded TCP/UDP for the reg server, and 2302-2400 UDP for the beta.
I think I covered it. Hope this helps.
You should keep it registered as a service (allsrvUI has some issues with the latest servers). AGM is outdated, I wouldn’t use it.
The server gets its settings from the registry. The keys are in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0\Server. If you’re using a beta server, it’s in 1.1.
The important values are:
ArtPath: The path of your server’s artwork directory.
CfgFile: The path of the configuration file. For the live servers, it’s http://autoupdate.alleg.net/allegianceserver.cfg. For the beta servers, it’s http://fazdev.alleg.net/FAZ/FAZ.cfg.
EXEPath: The path of your server’s exe file. Server logs will end up here.
Core1: The name of the core file for that game (without extension).
Game1: The name of the game in the lobby.
You can have a core2/game2, core3/game3 etc for multiple games on the server.
You need port 46724 and 2300-2400 forwarded TCP/UDP for the reg server, and 2302-2400 UDP for the beta.
I think I covered it. Hope this helps.
After a lengthy chat with TE, the server is up and connected to the lobby. However, no one cannect to it for some reason. It has a public IP, so I've no idea what is up with it. Suggestions are welcome.
EDIT : This is running in the Dplay8 lobby BTW.
EDIT 2:
Status update :
The server is a gateway server. Hence it has a built in firewall and NAT, courtesy Microsoft. I had to add individually, the 101 ports for forwarding. The funny thing? IT STILL DOESNT WORK!
Ports I have forwarded : 2300-2400 UDP, 47624 TCP/UDP.
EDIT : This is running in the Dplay8 lobby BTW.
EDIT 2:
Status update :
The server is a gateway server. Hence it has a built in firewall and NAT, courtesy Microsoft. I had to add individually, the 101 ports for forwarding. The funny thing? IT STILL DOESNT WORK!
Ports I have forwarded : 2300-2400 UDP, 47624 TCP/UDP.
Last edited by ImmortalZ on Sun Sep 10, 2006 9:49 am, edited 1 time in total.
I don't know how you managed to get that far with the incredibly vague instructions I've been able to find on this subject. The more I read about it the less I understand. /unsure.gif" style="vertical-align:middle" emoid=":unsure:" border="0" alt="unsure.gif" />
So what files exactly do I need to install to run an Allegiance server that shows up in the Lobby? I could care less about the beta stuff. I understand how to edit the registry files and all that but I haven't got a clue what files I should be using and were to install them. What is dplay8, and what does that do? Why can't I use the normal server setup files(AGM) to run a server? I downloaded something that says "Allegiance Server Setup", should I be using that or the dplay8 files, or both? I'm really confused here and any quality help would be appreciated.
So what files exactly do I need to install to run an Allegiance server that shows up in the Lobby? I could care less about the beta stuff. I understand how to edit the registry files and all that but I haven't got a clue what files I should be using and were to install them. What is dplay8, and what does that do? Why can't I use the normal server setup files(AGM) to run a server? I downloaded something that says "Allegiance Server Setup", should I be using that or the dplay8 files, or both? I'm really confused here and any quality help would be appreciated.
It often shows a fine command of speech to say nothing at all.
The Dev Team are trying to get the server to be more user friendly.
What I did for the Dplay8 server:
1. Downloaded server pack.
2. Installed server pack.
3. Unregistered AGC.dll
4. Removed AllSrv as a service (required if you selected register as a service during setup)
5. Got the latest Dplay8 server files from TE.
6. Replaced files in the server dir with files from TE's ZIP.
7. Registered AGC.dll, added AllSrv.EXE as a service.
8. Copied the required core and all .CVH files from my artwork folder into the server's artwork folder.
9. Exported the 1.0 server keys from registry, renamed it (inside) and merged it back to the registry so that it would have a copy of the 1.0 keys as the 1.1 keys. To clarify, I created a clone of the 1.0 keys and named it 1.1.
11. Edited the 1.1 keys to have it point to the FAZ Beta Lobby server and FAZ Beta CFG file.
12. Edited the 1.1 keys' Game1 and Core1 keys to the exact server name and the core I wanted to run (value of the Core1 key is the file name of the core IGC file without the extension)
13. Went to services in Administrative Options and started up the server. Seconds later, it shows up in the Beta Lobby.
14. Spent ~15 hours trying to find out why people cant connect to it. My conclusion from packet sniffing, mucking around inside the server (which is not mine and is on the other side of the globe from me) is that it's a gateway server running the Routing and <don't remember> service which makes the server do NAT and firewalling. It allows port forwards on a per port basis and not on ranges. I individually forwarded 101 ports and it still doesn't work.
15. TE has put up some of his own servers, so we still can play the SG today.
*whew* If you do require for your perusal, the commands for unregistering and re-registering the DLL and the server EXE, ask here and I'll post them for you. I don't have the logs handy right now and my head might asplode if I see the word server again.
What I did for the Dplay8 server:
1. Downloaded server pack.
2. Installed server pack.
3. Unregistered AGC.dll
4. Removed AllSrv as a service (required if you selected register as a service during setup)
5. Got the latest Dplay8 server files from TE.
6. Replaced files in the server dir with files from TE's ZIP.
7. Registered AGC.dll, added AllSrv.EXE as a service.
8. Copied the required core and all .CVH files from my artwork folder into the server's artwork folder.
9. Exported the 1.0 server keys from registry, renamed it (inside) and merged it back to the registry so that it would have a copy of the 1.0 keys as the 1.1 keys. To clarify, I created a clone of the 1.0 keys and named it 1.1.
11. Edited the 1.1 keys to have it point to the FAZ Beta Lobby server and FAZ Beta CFG file.
12. Edited the 1.1 keys' Game1 and Core1 keys to the exact server name and the core I wanted to run (value of the Core1 key is the file name of the core IGC file without the extension)
13. Went to services in Administrative Options and started up the server. Seconds later, it shows up in the Beta Lobby.
14. Spent ~15 hours trying to find out why people cant connect to it. My conclusion from packet sniffing, mucking around inside the server (which is not mine and is on the other side of the globe from me) is that it's a gateway server running the Routing and <don't remember> service which makes the server do NAT and firewalling. It allows port forwards on a per port basis and not on ranges. I individually forwarded 101 ports and it still doesn't work.
15. TE has put up some of his own servers, so we still can play the SG today.
*whew* If you do require for your perusal, the commands for unregistering and re-registering the DLL and the server EXE, ask here and I'll post them for you. I don't have the logs handy right now and my head might asplode if I see the word server again.
Last edited by ImmortalZ on Sun Sep 10, 2006 4:01 pm, edited 1 time in total.
ImmortalZ wrote:QUOTE (ImmortalZ @ Sep 11 2006, 02:00 AM) *whew* If you do require for your perusal, the commands for unregistering and re-registering the DLL and the server EXE, ask here and I'll post them for you.
Yes please. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" /> ...and thank you very much for the help. /cool.gif" style="vertical-align:middle" emoid="
It often shows a fine command of speech to say nothing at all.
Keep in mind that they change stuff daily, so it's better to get in touch with TE for the current EXEs.
for unregistering DLL.
to register DLL.
to remove server service. Make sure you stop the service before removing it.
to register the server as a service.
CFG file link. Regedit that into the 1.1 key. You'll know which when you see it.
All of these are commandline commands. The allsrv command must be performed in the same dir as the server. Make sure you backup all the files you replace.
Code: Select all
regsvr32 /u AGC.dllfor unregistering DLL.
Code: Select all
regsvr32 AGC.dllto register DLL.
Code: Select all
allsrv -regserverto remove server service. Make sure you stop the service before removing it.
Code: Select all
allsrv -serviceCode: Select all
http://fazdev.alleg.net/FAZ/FAZ.cfgAll of these are commandline commands. The allsrv command must be performed in the same dir as the server. Make sure you backup all the files you replace.
Last edited by ImmortalZ on Tue Sep 12, 2006 6:08 pm, edited 1 time in total.
Success!!!
I had to forward port 2351 to the LAN IP of the server instead of localhost. Weird thing is that every other service the server hosts is forwarded to localhost and they all work.
Only port 2351 UDP is forwarded ATM, and people have been playing. Aside from an of 50-90ms increace of normal lag (caused by a couple of crappy Qwest routers upstream that add 50-90ms of cumulative lag), the server's been playing nice. Bear in mind that most college routers now do packet inspection to block P2P traffic and this will add significant numbers to your lag. Aeris' college f.ex., adds 200ms at his router. So he's having more lag than me!
The server name is BeautyServ <core name>. Running PC2 and EoR 6a ATM.
I had to forward port 2351 to the LAN IP of the server instead of localhost. Weird thing is that every other service the server hosts is forwarded to localhost and they all work.
Only port 2351 UDP is forwarded ATM, and people have been playing. Aside from an of 50-90ms increace of normal lag (caused by a couple of crappy Qwest routers upstream that add 50-90ms of cumulative lag), the server's been playing nice. Bear in mind that most college routers now do packet inspection to block P2P traffic and this will add significant numbers to your lag. Aeris' college f.ex., adds 200ms at his router. So he's having more lag than me!
The server name is BeautyServ <core name>. Running PC2 and EoR 6a ATM.
Last edited by ImmortalZ on Tue Sep 12, 2006 6:45 pm, edited 1 time in total.

