Hey all,

I am frustrated here.



I want to beat a friend at CODUO, and want to do it on my own LAN.



We have a verizon dsl setup, and back to back cpus.



I have installed CODUO on both cpu's, but I cannot find the other CPU on the list.



I also cannot start a server on the one cpu, i get the error



could not find script 'maps\mp\gametypes\_awe'



what am i doing wrong, and how can i set up a LAN game in my office here like on "the office"

The first place I would check is your firewall. You have to open or create port 28960.

good god i am already lost....

Okay, that's understandable. None of this is made to be plug 'n play.

You might want to take a look here: http://www.codboards.com/archive/index.php/f-7.html

Each of these sections provide questions and answers to all things COD. You should concentrate on the Multiplayer and Server support sections.

Here is one answer that might help you:

Question
How do I set up the game for multiple users behind a NAT firewall?
Answer
The following is unsupported by Activision.

To setup for multiple users:
1) Right-click on the Play Call of Duty Multiplayer icon you use to start the game.
2) Select Properties.
3) In the Target field you'll see a line like "C:\Program Files\Call of Duty\CodMP.exe", add the Quake III net_port command to specify a unique communication port for each system. The complete field should look like this:

"C:\Program Files\Call of Duty\CodMP.exe" +set net_port 28960

4) Click OK.
5) Repeat for each system behind the NAT, adding one to the net_port selected (28960,28961,28962)


While the first player behind the NAT joins fine, adding additional players is problematic in the default configuration. Symptoms include rejected challenges, invalid cdkey, dropped delta packets, and severe "connection interrupted" messages.

By default, Call of Duty clients send and receive data over the same port, causing the server to treat multiple clients as a single data connection.

I can help you with the error message

could not find script 'maps\mp\gametypes\_awe'

This is caused by a copy of the Awe weapons mod or a remade version of it.

Go thru your cod/uo folder and delete any files with awe in the name.



If both computer are attached to the same router you can probably ignore what hamma said as that's more towards enabling other people outside your lan to access the server you setup.

There's no need port forwarding as long as both computer are part of the lan

Process should.

1) Setup computer #1 with the game options you want, start the server ( NOT dedicated mode )
2) Start computer #2, go to the in-game browser, ( I'm not at my game computer right now but the in-game browser should have an option to browser either Internet or Lan ), set to LAN.
3) Computer #1 should be thge ONLY server listed. Double click to connect.



If this doesn't work correctly, let me know the make & model of your router.

they are on the same router/modem (it is a combo)



I am at work, but i know the device is a westell, a versalink i think...



I tried opening those ports and stuff but no success.



I will try to rid the files of the AWE files, and see if that changes my other error.



I did the LOCAL selection in the MP menu, and did not see anything going from cpu 2 to cpu 1,

but after i delete the awe files, maybe i can go from cpu 1 to cpu2

If you still have a problem after removing the file causing the error on the computer you are trying to setup as the server, then reply back with a time (central time) you'll be on vent & I'll walk you thru it.
I can be avalible from 6-10pm central, just be sure to give me an hour notice.

Just to let you know...you need two different copies of UO (diff serial numbers) for both computers in order for two people to play on the same server.



That's all the advise I can offer you, I'll leave the technical stuff to the pro's.

T/A6Pak

but do you need 2 copies if you are on the same lan?



THAT could be the problem.

Yes, you have to have two separate copies with different CD Keys.

Thanks, Druid for straightening this out! You da man!

The Mac environment is different - you do have to open up a port on each machine. Guess this speaks to the security model of the Mac. Just one of those things that helps make it a more secure platform.

The suggestion you need 2 cd-keys is wrong, that ONLY applies when connecting to Internet servers not LAN servers.
Lan servers do not contact Activsion's Master server to valid CD-keys an issue COD GUIDS.
I've ran a 20 man lan all using the same key.

My best bet is if the Host computer doesn't show up in the browser on the 2nd computer it's because it's filted out.
For example,
The browser on #2 might be setup to only show Base assault server but #1 is setup as TDM
Or maybe the filter options on #2 is setup to only show servers with Punkbuster enabled.
In that case, if your server on computer #1 didn't have PB enabled, it wouldn't show up on the in-game browser on #2.


If there is some type of problem getting the in-game browser to see the other computer, you could always do it manually.
Find the local IP address of #1
1) Go to start>Run
2) type cmd, this will open a command promt window.
3) type ipconfig, this will return the IP address the router assigned the computer.
It should be something like 192.168.0.100. This will be listed on the line IP Address.

Now start the server on PC#1, let the map completely load
Start the game on PC#2, open the console window and connect manually to PC#1
Using the example IP address, above it would be
/connect 192.168.0.100

Finally a guy with my kind of knowledge.

This worked thanks!!!!



I still have the awe issue, but i may just reinstall...

You'll need to get rid of all of your mods. And also your mod folders in your C:/Program Files/Call of Duty folder.

A good easy utility to help you with this is Ezekiel's cod multi-fixer. You can get it here http://callofduty.filefront.com/file/;67336

BTW, if don't use this cleaner utility, but instead you decide to reinstall, remember that first you uninstall the game, then you still have to delete out the C:/Call of Duty folder yourself.