Resistance ded server

[zinco 0]

same thing happens with 1.92

[zinco 0]

Radish did u ever find a solution?

[GhostX 0]

on linux run :

./server -config=server.cfg -port=2302 >> out.txt 2>> err.txt

and check err.txt

[zinco 0]

i did that on windows 2000 in the bat file and it will create err.txt but does not report an error. the file is empty. flashpoint.rpt also does not report an error.

[GhostX 0]

on win, u should, at least, try to set correctly your DNS setting(once this was the problem)

be sure to have server.cfg file something like this:

passwordAdmin="12345";

hostname="Testing Server.";

motd[]=

{

"Welcome.",

"Bla bla - edit as u like it"

};

MaxMsgSend=128;

MaxSizeGuaranteed=512;

MaxSizeNonGuaranteed=256;

MinBandWidth=131072;

MaxBandWidth=512000;

voiceOverNet="false";

maxPlayers=6;

kickDuplicate="true";

motdInterval=3;

voteThreshold=0.33;

reportingIP="";

voteMissionPlayers=0;

class Missions {

};

This is the minimum, that config file should contain.

Later u can use more precise config file .. search this forum - it has been discussed many times here.

[Dutchie 0]

Dit you edit your .bat file ?

sample.cfg has to be edited to .cfg whatever you call it

[zinco 0]

server -config=server.cfg -port=2302 >> out.txt 2>> err.txt

that i added to the bat file.

reportingIP="";

this i do not think i have in server config.

i have searched the forums and this is the only thread that seems to address the not working with sockets problem i did not see a resolution for sure. we are going to uninstall the pci 3com card and take it out and use the onboard intel card only and see if that works.

[zinco 0]

Nm reporting ip is in there.

the bat file and server config are all correct and everthing worked before. the ip is stactic and dns settings should be ok. the problem occured after rebuilding the server with new mobo and dual procs. the same NIC is being used with the onboard card disabled. it has to be a problem with having both cards even though the software is disabled on one.

[benu 1]

The testing server i set up yesterday did not start at first (2302 error) because the internal hostname did not match the external (what you get when asking dns servers about the ip of the external interface). When i changed it the server worked. Afaik the 2302 error is network related most of the times. Check for firewalls, correct routes, dns, hostnames...

[zinco 0]

I am not sure what u mean by the external and internal hostname. I am not that familiar with the ded set up and i did not install it, although i do have remote access to it.

I am assuming the external host name is the one in the server.cfg. Where can i check the internal?

[zinco 0]

Also it works in directplay so i would think hostname and dns are correct. it will not work with sockets as radish described.

[zinco 0]

well we gave each card its own ip.  unistalled and reinstalled tcp/ip. to no avail yet.

[zinco 0]

Have reinstalled game. Have removed software and hardware 3com pci card. Have reinstalled drivers and tcp/ip on on intel onboard card. still to no avail.

[zinco 0]

It would be nice to get some support on this we just bought a brand new mother board and dual procs and now can't run a server.

Server specs:

Mobo: Gigabyte GA-7DPXDW+

CPU: 2 x AMD MP2400+

Memory: 1GB PC3000

Hard drive: 40Gb Maxtor ata133 7200 rpm

NIC: Onboard Intel PRO/100 Server adapter

O/S Windows 2000 Pro

Connection: Dedicated T3

DirectX 9

All other internet functions work fine including a VietCong server.

[zinco 0]

Its fixed. Changed the host name or computer name and dns suffix. will post more later.

[GhostX 0]

as I told u ... OF server MUST have correct DNS settings.

This is the first thing that should be checked if the server is unable to start.

But post your settings .. that may help someone in the future.

[zinco 0]

I am not a network guy and to be honest alot of this i am not sure how to do alot of this stuff. So me and another guy were trying to fix something we did not know how to fix. Thus looking for support in here.

*** fidelity.faynet.com can't find 65.113.133.112: Non-existent domain

i think the host/computer name had a space in it or something so was not being recognized. I will post the solutions for dummies here for future reference. What you guys don't realize is that when u say check your dns settings alot of us may not even have a clue what dns settings are.

[zinco 0]

This from ZAP:

*********************************************

OK, in a nutshell:

1st off, don't put a space in computer names because the DNS RFP doesn't support spaces even if windows does. i.e. you can't have a web address like www.one space.com.

I changed the computer name to match the DNS name of HOTEL and added the 1-8th.com dns name to the DNS suffix in the TCP/IP config.

Crossed every finger and toe I have and rebooted.

I also set up all the batch files and processor affinity so each process claims it's own CPU and set evrything to autologon and start minimized.

Moral of the story:

Make sure the WINDOWS name of your server is a valid INTERNET name. (no spaces)

----------------------------------------------------

edit: At this point on a NT system do start/run type cmd hit enter. then type ipconfig /all press enter

--------------------------------------------------------

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : HOTEL

Primary DNS Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : 1-8th.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : 1-8th.com

Description . . . . . . . . . . . : Intel® PRO/100 Server Adapter

Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx (edit)

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 22.888.873.444

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 22.888.873.2

DNS Servers . . . . . . . . . . . : 22.888.873.3

22.888.873.7

C:\>nslookup

Default Server: fidelity.faynet.com

Address: 22.888.873.3

> hotel.1-8th.com

Server: fidelity.faynet.com

Address: 22.888.873.3

Non-authoritative answer:

Name: hotel.1-8th.com

Address: 65.113.133.112

>

C:\>netstat -a

Active Connections

Proto Local Address Foreign Address State

TCP HOTEL:epmap HOTEL:0 LISTENING

TCP HOTEL:microsoft-ds HOTEL:0 LISTENING

TCP HOTEL:1025 HOTEL:0 LISTENING

TCP HOTEL:1030 HOTEL:0 LISTENING

TCP HOTEL:1073 HOTEL:0 LISTENING

TCP HOTEL:4899 HOTEL:0 LISTENING

TCP HOTEL:netbios-ssn HOTEL:0 LISTENING

TCP HOTEL:xxxx xx.xxx.xxx.xxx:http CLOSE_WAIT

TCP HOTEL:4899 xx.xx.x.x:61472 ESTABLISHED

TCP HOTEL:4899 xx.xx.x.x:62976 TIME_WAIT

TCP HOTEL:4899 c-xx-xxx-xx-xxx.we.client2.attbi.com:4777 ESTABLISHED

UDP HOTEL:epmap *:*

ip's changed or xx

this check will tell if things are working or maybe what is not working.

like this was not working:

C:\>nslookup

Default Server: fidelity.faynet.com

Address: xx.xxx.xxx.x

> 65.113.133.112

Server: fidelity.faynet.com

Address: xx.xxx.xxx.x

*** fidelity.faynet.com can't find 65.113.133.112: Non-existent domain

> server xx.xxx.xxx.x

Default Server: fidelity.faynet.com

Address: xx.xxx.xxx.x

[R.E.M.F 0]

I have just had exactly the same problem.

For me it was nothing to do with ip's or DNS or anything along those lines. The computer name included a hyphen, renamed & it fired up first time

Check your pc name, anything other than letters, try renaming

[zinco 0]

you know Zap said it was a space but i could swear it was a hyphen and no space.  name your computer only with letters i would say ie. hotel

it does have to do with dns because the dns server is not recognizing the name with hyphen or space.

[Elvis666 0]

it works THX zinco

[m16a2m203 0]

Great. After a year I finally get an answer as to why I could never host a sockets game and now the community has grown smaller in size... Wished I had seen this sooner as well but stilll a long time to wait even if I first saw it when the answer came out.

Let's see...

I like Veronica Z,

I like OFP,

I hate Czech support techies.

I quess 2 out of three ain't bad.

[DOA 20]

I have the exact same issue now with three machines two workstations and one laptop. They are all less than a year old and well equiped.

I will try renaming the machines but they contain no special characters in the names : 18002k  3000xp 15002k

they are named after their CPUs and OS...18002k is a 1.8Ghz Cpu running Win2k etc...

I too can host or run a dedicated server in directplay but not in sockets...I am sure it is a sockets issue...dn

Here are the two posts I have working the same issue:

http://www.flashpoint1985.com/cgi-bin....;hl=doa

http://www.flashpoint1985.com/cgi-bin....t=36285

[m16a2m203 0]

Had the same thing as noted above. My computer name was 2400AMD or some such. I changed it to say APLHA and now everything works fine. Possibly it doesn't like numbers as well as spaces?

[DOA 20]

I too have struggled with this issue of not creating dedicated servers or hosting multiplayer games. It would work in direct play, but not in sockets, etc etc. This name thing finally resolved my issue.

My server was named 3000xp (3.06 Ghz CPU with WIndows XP) I renamed it to "server" and it worked, I named it 1server and it stopped working again...I did a couple of tests and determined this to be my fix. Thank you very very much.

I had this issue a long time ago and resolved it by wiping the hard drive and starting over, now I realize that my rebuild was not what fixed it. When I rebuilt my server I must have changed the name...

I recently had this issue again with two servers and a laptop... All were named after their cpu speed, their name started with a number(15002k, 1800xp, 3000XP)...Changeing the names to ofp1 ofp2 and ofp3 worked first time every time...

Operation Flashpoint is the best military simulation ever, it has no peers that even rank a comparison...DOA