okay, so here's what happens.
i setup my raven shield dedicated server on window 2003. nobody outside of my LAN can connect to it, or see it for that matter (they just get a 'server is not responding' error). so i copy the .ini files from the 2k3 box, to my xp box and run the dedicated server there... works fine (people can connect, play, etc). i checked my router settings and they are exactly the same for both the 2k3 and the xp stuff.

so my question is, is there some setting in 2k3 i have to change or something (i have the software firewall disabled)? because i can connect to it fine via LAN, but the people on the WAN cannot connect. which is really annoying, anyway, thanks.

http://forums.ubi.com/messages/overview.as..._ravenshield_ts


thats the ravien shield forums maybe it can help

yeah i looked there, but seeing as how 2k3 isnt really out yet i figured id ask here since the problem seems more os related as oppose to game.

sry but if i do come accross an aswer or any more info i will post it asap


Edit:
#1- did u apply the patch
#2- Does it work when u dont have it dedicated?

http://groups.google.com/groups?q=raven+sh...04ax.com&rnum=2

It seems people are getting other bugs in Raven shield while running 2k3

thats the beta 2003

this bug that they talk about has nothing to do with what the topic at hand is.

I tried to search google and nothing even close to the topic comes close but

try this
|
|
\/
Edit:
did u apply the latest pacth.....does raven shield even run online on the 2003 system?

yes, the newest patch is on it. i can play it fine on the lan, and it connects fine to the key-checking server. im damn near 100% sure this is a 2k3 setting i have to change, which is why i posted it in the windows family forum.

i dont have server 2003 yet but like i said before i will help ya out if i pass by some info concerning this...also if u do plz post

I know, thats why i said people were getting other bugs in 2k3 (beta)

well im running the RTM

ah i c, well i do remember at teh win serv 2k3 launch that Ballmer said there were new security defaults, so there may be something in the network you may need to correct

Video as a source: http://news.com.com/1601-2-998253.html

yeah thats what im thinking, i hope i get it sorted out :S

ack, nevermind i got it sorted out, turned out the router didnt like opening the same ports on different internal ip addresses.