Thanks for the reply.
After you replied, I confirmed that as well. I then started eliminating parameters and I was finally able to get it to work. Turns out that the server executable behaves differently when started by FireDaemon. If I start the server with FireDaemon, the netlog doesn't get created or written to, but if I start it with a batch file or straight from cmd, it works just fine.
After that, I figured it had to be a permissions issue since FireDaemon starts services as LocalSystem by default. Once I added it to run it as the Administrator account, it logged the netlog just fine.
Are there any plans of allowing that to be moved in the future? I would much rather have it in the server folder somewhere. Especially since boxes with multiple servers are going to be hard to determine which is which..... Especially for ARMACon, that I'm working on. It's going to be impossible to determine which file to use since the files are distinguished by PID, which can't be determined by FTP or even HDD access for those running locally.....
Maybe you can do what the RPT file does and use the profile that is being used as to where it should put those files.
Either way, thanks for your help on this one.