windows server's
- Matt?
- Private First Class
- Posts: 281
- Joined: Sun Jan 09, 2005 10:15 pm
- Location: st. john wa
- Contact:
windows server's
ok i heard and tested that with windows you can only have a certain number of flags. now is that bzflag related or is it just windows. thanks
- Matt?
- Private First Class
- Posts: 281
- Joined: Sun Jan 09, 2005 10:15 pm
- Location: st. john wa
- Contact:
are you...
are you 100% sure, cause theme(he has number's here but i dunno them) is runny a server on xp pro(like me) and he had 48 flags in and was running a public server successfuly. hmm
There was a patch bought in with XP SP2 that limited you to 10 TCP connections.Win Xp wrote:its open source software, it seems to have something to do with the connection limit of windows for some reason, at least thats what my examinations show.
This can be bypassed illegally by disabling Windows File protection and installing a patched tcp.sys.
If you look in your error log you will see a TCP warning when you try and go over your connections limit.
Matt, either use Windows Server or install linux on a spare machine
Win Xp's problem was bandwith and server funk, not an actual limitation in the code.
The windows server supports the SAME number of flags as any other OS. It's the same code.
Non server versions of the windows OS have a connection limit of 10 users by default. There are ways to change it.
if you flood your bandwith then the messages for things get droped, like flag updates, and player updates, hence why it's "sporatic".
The windows server supports the SAME number of flags as any other OS. It's the same code.
Non server versions of the windows OS have a connection limit of 10 users by default. There are ways to change it.
if you flood your bandwith then the messages for things get droped, like flag updates, and player updates, hence why it's "sporatic".
JeffM
It can be passed legally, too.
Let me search the Introduction for this...
It needs Windows XP SP2
1) open windows registry editor. (Start->run and type regedit)
2) Goto:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3) create a new DWORD-entry with that name: "TcpNumConnections"
and give him the value "fffffe"
Now, you can have up to 16.777.214 simultaneos connections open.
Let me search the Introduction for this...
It needs Windows XP SP2
1) open windows registry editor. (Start->run and type regedit)
2) Goto:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3) create a new DWORD-entry with that name: "TcpNumConnections"
and give him the value "fffffe"
Now, you can have up to 16.777.214 simultaneos connections open.
JeffM2501 wrote:Win Xp's problem was bandwith and server funk, not an actual limitation in the code.
The windows server supports the SAME number of flags as any other OS. It's the same code.
Non server versions of the windows OS have a connection limit of 10 users by default. There are ways to change it.
if you flood your bandwith then the messages for things get droped, like flag updates, and player updates, hence why it's "sporatic".
Please xaplin while then when I am in linux I can have 100 flags and 20 players?
also, alex135 can only have 10 flags on his T1 connection.....
hard to say with out debuging the exact problem.
I'm just saying it's NOT something that is in the code ( like a limit ). It could have been problems on your windows system, or your nic driver, or some other system process screwing it up.
if you realy want to find out why, then it it needs to be debuged, not you guessing that it's just "something windows does sometimes". All things happen for a reason.
I'm just saying it's NOT something that is in the code ( like a limit ). It could have been problems on your windows system, or your nic driver, or some other system process screwing it up.
if you realy want to find out why, then it it needs to be debuged, not you guessing that it's just "something windows does sometimes". All things happen for a reason.
JeffM
- Tropican8
- Private First Class
- Posts: 312
- Joined: Fri Mar 18, 2005 11:51 pm
- Location: As close to the grove as you can get
I can say for sure its not a b/w issue, and it is also not the 10 connection limit in SP2 (I've had the problem in SP1, plus I am almost positive the 10 connection limit is only on lan networking, not HTTP or UDP internet connections). If it helps, in the server console output logs I have of the problem I get EAGAIN errors. Also I do not remember the problem occuring before 2.0.2, making me think Windows doesn't like a bzflag server code change made from that time. (Not saying its not a bug in Window's code that doesn't like something newer in BZflag)JeffM2501 wrote:hard to say with out debuging the exact problem.
I'm just saying it's NOT something that is in the code ( like a limit ). It could have been problems on your windows system, or your nic driver, or some other system process screwing it up.
if you realy want to find out why, then it it needs to be debuged, not you guessing that it's just "something windows does sometimes". All things happen for a reason.