Dedicated stand alone server sockets problem.

[DOA 20]

On two of my spare machines, which I would like to NAT through the firewall and run as internet servers, I am unable to start a new MP server using sockets; but, I can start one using direct play. (I am aware of the issues with direct play. I just used it for testing this issue).

I copy my OFP game folder (known good and working) to these machines and when I try to run a dedicated server I get "server creation failed :2302" in the title bar of the server window. When I build the OFP game folder up from scratch (Wipe the hard drive, install Win 2000 or Win XP, and then install OFP <gold>, patched to 1.46, and then Resistance, patched up to 1.94) I can't start a MP game in the MP game window. When I click "new" in the MP window, for internet or LAN, I get a brief screen "Creating Client" and then it kicks back to the MP screen. I never see creating server or "Player name connecting". These machines are well equiped Dell workstations. Dimensions, 1.8 and 2.5 Ghz CPUs, at least 512 MB RAM, 3com 3c905-tx NICs, nVidia 3d cards Geforce ti4200 64MB, etc. Firewall and anti-virus is not installed on the test machines yet. I don't see anything in the event viewer on any of the system logs. Is there an error log created by OFP and if so where may I find it?

The game folder is good, it works on several other machines. I do not think anything is wrong with my OFP game folder build. I now believe it is an issue with the OS, networking settings or maybe even a hardware issue. I have tried differient NICs and moved them to different PCI slots. I have removed and re-installed all the network connection settings, Client for Microsoft networking, TCP/IP, File and printer sharing, and QoS. I give them static addresses, gateway, DNS, etc.

I am now wiping the hard drive and roling back to Windows ME to try that. (Just kill me now) :-)

I have another post working on this subject. I am sorry for the duplication. I incorrectly stated the problem on the other post.

Thanks in advance for your help.

[benu 1]

I am not sure if it will be possible at all to run an ofp server behind nat. The 2302 error often pops up when there are dns inconsistencies. And as you forward the ofp from the computer with the inet address you would have to use that computers name on the computer running the server too afaik (internal and external(=dns) hostname have to be the same).

[DOA 20]

Thanks for the responce. I can't start the server even when it is not connected to a network. You can start a MP game anytime in the MP window by selecting LAN or internet then clicking "New" in the MP window. I do this all the time to test custom MP missions I am working on.

When I reach the MP window and click on "New" it will not create a server and the "<Playername> connecting" never happens, you get kicked back to the MP window.

About the firewall and NAT

Heres what I do:

Give the OFP server machine a static internal LAN address, like say: 10.10.10.186.

Then on the Firewall

Create/add a service. I name it ofp1 and allow UDP 2302 for the game.

I create another service, ofp2,  UDP 2303 to report the server to the game browsers/gamespy.

Create rules allowing the two services I created, ofp1 and ofp2, to machine 10.10.10.186.

Last thing is to NAT the internal address 10.10.10.186 to an available outside (public) IP. I go to "Advanced Settings", "One to One NAT" tab, and set up 10.10.10.186 to 198.143.xxx.xxx. This NATs the internal address to a public address.

(I'm sorry about the xxx.xxx I'm not ready to publish the public address yet). If you do not know the range of public addresses allocated to your company network, your carrier (ISP) will provide them for you. We have 10 public addresses of which we only use 2 for business.

Thanks again for helping out. I will make the custom missions and the servers public address available as soon as I get these issues resolved. I hope this will be fixed before the relase of OFP2 which I plan to immediately implement. (Hey BIS/Codemasters: Send me a beta copy of OFP2 any old time! I will test it to death! LOL). I'm sure it is something in the networking settings or OS on the server machine. Thanks again...DOA.

[benu 1]

This bug is evil

Can you start ofp on a maschine without any kind of firewall?

This does not seem to be a hardware issue, as there were admins who had this bug with linux and got the server running with windows and win admins with the bug who got it working with linux on the same machine.

And all the hints to solve this (install nscd, check dns settings and hostname) indicate that ofp seems very picky about network/dns settings.

I started a local server too and had no problems (after getting the hostnames right ), but in my lan the names for all boxes are defined on all machines with host.txt.

[DOA 20]

Here, in brief, is a status report.

Here is what I have been trying:

The problem machine is well equiped with CPU and RAM and video card, etc. 1.8 Ghz CPU, 512 MB RAM, Geforce ti 4600 128 MB, Soundblaster Live, 3c905 nic. Clean install of windows XP, or 2000 or ME, and nothing else loaded except OFP.

Fdisk the hard drive, starting from scratch each time, I have installed WindowsXP, Windows 2000, and even Windows ME. Not at the same time, I have tried all this stuff in windows and NT. (I have too much free time)

TO start I don't do any windows updates except to install the latest nvidia drivers and directx 9.0b, then I gradually add the updates testing at each step.

I install OFP Gold and patch to v1.46. Then I install Resistance and at the 1st install of Resistance v175 I can not start a MP game using sockets. Host or Dedicated. I continue to 191 and then 194 with no joy.

I have tried differient NICs in differient PCI slots, I have updated the bios, I have used earlier versions of directx, I have tried it after the windows updates and patches, I have moved known good OFP game folders to the hard drive and still the same issue.

I have removed and reinstalled all network and tcp/ip options and manually configured the NIC ( I knew I would use all that A+ stuff some day! :-) Static addresses, DHCP, LMHosts files, etc etc... all with the same issue...no server in sockets but works fine in the dreaded hard drive eraseing "Directplay". I am beat. I am setting fire to the machine and claiming it was an accident. LOL

I can repeat this procedure on similar machines and it works fine with no issues. This PC is cursed and should be destroyed and recycled.

Thanks for all your efforts on this and my first posts on this issue. I am sorry to give up without a resoultion but I am not getting any younger and I have other spare machines I can use.

Thanks again...DOA

[DOA 20]

GOT IT ...

Your servers "computer Name" can not start with a number or contain special characters. My porblem machines were all named after their cpu...1500 2k 1800xp, 3000xp... I renamed them and my sockets server issues dissapeared. I added a number to the begining ov the name and my sockets server crash reappeared... This worked for me. I hope it works for you...

Here is the post that resolved this issue.