I take forever to connect to my friend! HELP PLEASE!

[UTCollector88]

Hi All

I am trying to connect to my friend so we can play online. He is hosting a campaign server game and I am connecting to the server. The problem is it is taking forever to connect, I mean it just sits there. Whether he connects to me or I connect to him the same things still happens.

Help would be appreciated ASAP. This online problem is annoying me.

[UTCollector88]

I have new news. I upgraded to the latest patch for UT3 to try and fix the problem. Now I have a different problem. I get an error when I try to host a UT3 multiplayer game. It says 'Your network connection may not be compatible for hosting matches. Please check your routers manual for port forwarding or setting up a DMZ server.' So I looked up how to set up port forwarding for UT3 in your router and I did it and it still comes up with the error. Grrrrrrrrrrrrrrrrrrrr!!!!!!!

[NickG]

forward the additional range(s) of ports listed here. http://www.brainstormwarning.org/200...-campaign-play

[UTCollector88]

Okay, I'll try that. If that doesn't work I will try the STUN server solution workaround I found on youtube. I have a netgear CG814WG.

[UTCollector88]

I have done the port forwarding in my router. Now I need to add a rule for my PC antivirus firewall. I wasthinking of adding a rule to my antivirus firewall from Kaspersky. Can you please confirm if this is right?:

My firewall Rule;

Action: Allow

Name: (Make up)

Protocol: UDP

Direction: Inbound/Outbound

Remote Ports: Not sure

Local Ports: UT3 ports I forwarded in router. (or are they remote ports?)

Address: Not sure.

[NickG]

No I can't, I don't use antivirus.

[UTCollector88]

I have tried hosting again with the port forwarding set up. Once with my antivirus client firewall disabled and once with the rule I mentioned above. It still came up with the same error message when going to host a campaign game. It didn't work.

[NickG]

I have tried hosting again with the port forwarding set up. Once with my antivirus client firewall disabled and once with the rule I mentioned above. It still came up with the same error message when going to host a campaign game. It didn't work.

Your router has a SPI firewall which may be what is slowing you down, you can disable it: http://forums.whirlpool.net.au/archive/990173
You may have to setup other stuff in your router for the nat transversal (end-point filtering), I have no idea, as I do not have that router. (My router has it's own peculiarities: for example, I must re-apply the port-forwards if I've reset my PC, when I am using DHCP rather than a static IP, despite the internal address remaining the same.) My previous router would not work with ports forwarded from the more common guides, so I just used to put it into DMZ while hosting. The port-forwarding is probably safer, since you can specify protocol, and not all ports are open. I did the run-your-own-stun workaround before with my old router; and, while it offs the message, I am not convinced that it truly helped hosting ability. (people still joined my game, and others have reported the same)

[UTCollector88]

My previous router would not work with ports forwarded from the more common guides, so I just used to put it into DMZ while hosting.

I'd rather not put my PC into a DMZ, that would have to be the last of the last of resorts and if I am desperate. I will look around again for NAT transversal for my router for UT3. By the way when did this whole online issue start? I know it started with the joining issue like me and then Epic released a patch to fix that issue but created another multiplayer issue in the process. I use to be able to play UT3 online when I first got it before they released or the patches or updates.

[RattleSN4K3]

Verify if you're able to connect to the server:
If you want to connect to a server, get his external IP and check if you're able to ping it with the ping application in a Command prompt (clientsided)

ping IP

If it does not work, try to check if the ports are open (serversided). Go to any site with a port check and check every port listed on the site NickG mentioned.
If you can't get a connection to the specific ports, try to port.forward (serversided).

I got this message about a bad DMZ setting as well, but it worked for me. It have the ports listed on the website portforwarded.

If the server is behind the mentioned router, follow the instructions of this site on that server machine.
http://portforward.com/english/route...urnament_3.htm

[NickG]

Just a caveat about using port checker apps, your ports should be forwarded with udp, and will only respond to the correct data, so using basic port checker apps may return false negatives.

[UTCollector88]

Verify if you're able to connect to the server:
If you want to connect to a server, get his external IP and check if you're able to ping it with the ping application in a Command prompt (clientsided)

ping IP

If it does not work, try to check if the ports are open (serversided). Go to any site with a port check and check every port listed on the site NickG mentioned.
If you can't get a connection to the specific ports, try to port.forward (serversided).

I got this message about a bad DMZ setting as well, but it worked for me. It have the ports listed on the website portforwarded.

If the server is behind the mentioned router, follow the instructions of this site on that server machine.
http://portforward.com/english/route...urnament_3.htm

I already used the port checker to check the ports NickG mentioned and it said they are open. Also I forgot to mention as well as the error in UT3 about hosting no servers showed up for my friend when I was hosting a campaign multiplayer.

[RattleSN4K3]

What's your (and your friends) setup? OS, installed version, etc.

A hosted server would not always show up in the lists as there are options to disable that (and you need to port-forward the specific ports, the one for the master server and the one for gametracking, maybe more). The command for connecting to any server would be better (to be used in the F10 console):

open IP

or with a port

open IP:PORT

As you said something about a Firewall you're using, did you try to disable it for once? Generally, you'll always to allow incoming/outcoming connections for an internet gateway. E.g. Win7/Vista will block these connections in general. And the ports should be configured as Remote and local ports.

I would suggest to setup your DHCP so you're always getting the same local IP for the PortForwarding of ports (e.g. like MAC based). In addition if you're trying to use a Listen server (the one who's hosting the server will play as well; differently to Dedicated server where it's only a server and no player), start the UT3 instance with "-log" (or use the "showlog" command in the F10 console) to see direct feedback of incoming and ending connections. At the time any client will try to connect to the server something you'll see something like this:

NetComeGo: Open TheWorld IP:PORT

A brief explanation of all the steps you (and your friend) were doing would be helpful.

[UTCollector88]

What's your (and your friends) setup? OS, installed version, etc.

My setup is Windows Xp service pack 3 and my friends is windows xp service pack 3. And we both have the regular version of UT3 with the latest patch, patch 2.1(5). I mentioned what router I have on page 1, not sure what router my friend has though. I will have to check with him. Anything else?

The command for connecting to any server would be better (to be used in the F10 console):

open IP

or with a port

open IP:PORT

Are you referring to the console in UT3?

As you said something about a Firewall you're using, did you try to disable it for once? Generally, you'll always to allow incoming/outcoming connections for an internet gateway. E.g. Win7/Vista will block these connections in general. And the ports should be configured as Remote and local ports.

Yes I have disable the firewall to see if it was causing the problem but it wasn't.

I would suggest to setup your DHCP so you're always getting the same local IP for the PortForwarding of ports (e.g. like MAC based).

Yes I have changed my IP to a static IP address through network connections. I have done certificate 4 in networking in tertiary school so I know some network stuff and how to configure some things.

In addition if you're trying to use a Listen server (the one who's hosting the server will play as well; differently to Dedicated server where it's only a server and no player), start the UT3 instance with "-log" (or use the "showlog" command in the F10 console) to see direct feedback of incoming and ending connections. At the time any client will try to connect to the server something you'll see something like this:

NetComeGo: Open TheWorld IP:PORT

Yeah, I use a listen server when hosting a game not a dedicated server.

[UTCollector88]

Your router has a SPI firewall which may be what is slowing you down, you can disable it:

The routers SPI feature for the firewall is disabled. No change.

[RattleSN4K3]

Are you referring to the console in UT3?

Yes.

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

Do you have another PC? You can try if you're able to connect to your server on LAN.

Short checklist for online accessibility:

Server's Machine is behind a Router. The machine has a local IP of 192.168.1.2. The external IP of the Router is like 123.45.67.89. Since you're both using WinXP, the it shouldn't be a problem with a HomeNetwork.
Server:
- Configure the ports to forwared the data to 192.168.1.2
- Allow connections in the Firewall for the application for every port.
- Start UT3 instance. Once you hosted a game, press Alt+Enter (for a windowed mode).
- Open up the console (by pressing F10) and type in:

showlog

- Check the new black/white log window for connections of a client

Client:
- Ping 123.45.67.89 (to check for connection). You have to get a response.
- If you're able to play UT3 online, you don't have to configure anything else.
- Start UT3. Once you logged into your account, press F10 for the console and type in:

open 123.45.67.89

- Check the firends server PC in the log window for a connection.

Generally, UT3 is working fine. It's always some sort of bad network settings (/not configured). The main problem is always the server. The server has to have a proper router setup and a working internet accessibility.

[UTCollector88]

Sorry my second computer isn't powerful enough to run Unreal Tournament 3. But I can test it with my friend. If I host a game with the log showing and my friend opens his WAN IP with the UT3 console, will that be ok?

But how do I make sure he connects to me and not another server when he types the open IP command in the console?

[RattleSN4K3]

The 2nd PC does not have to be able to run UT3 efficiently. It's just a computer to check the server in a LAN wether to know if there's something wrong with the UT3 server itself or the general network setting (like routing, portforwarding etc.).

But how do I make sure he connects to me and not another server when he types the open IP command in the console?

You have to report him your external IP. You can get your external by visiting a random site like (whatsmyip-somthing.bla; just google "my ip"). Your friend has to connect to this IP. Normally, your friend will connect to your PC if you gave him the correct IP (it's like a phone number).

But I can test it with my friend.

You can be faced many problems while testing the server over the internet. (software Firewall, routing, hardware firewall, unaccessable ports, ...). It is more efficient to test the easiest way first, then you can filter possible problem derivation.

If I host a game with the log showing and my friend opens his WAN IP with the UT3 console, will that be ok?

Your friend has to "open" your WAN IP not his own.

[UTCollector88]

Okay. Also I tried pinging port 7777 and the associated IP address and the request times out all the time. I tried port 6500 and 13000 and the same thing occurred.

I rechecked the ports through the same online port checker site and the ports 7777, 6500 and 13000 status has now changed to stealth which explains why the packets time out.

Should I change their status to open? If so how without it changing back to stealth? Or are they alright in stealth mode?

[RattleSN4K3]

You can't ping a port. You (as a server) do not need to "ping" anyone. Ping has the purpose to let clients (or any machine) know wether they able to "connect" to the destination IP.

If you're trying to check wether a port is open or closed, verify if the application is running. In this case, start the UT3 instance as a server. Now get you WAN IP and use different tools to check wether the port is open (like online tools).

[RattleSN4K3]

Should I change their status to open? If so how without it changing back to stealth? Or are they alright in stealth mode?

The stealth mode has something to do with the firewall (software, hardware or both.)

You are the server:

• Check your software firewall, if it's blocking any connection (allow UT3 on every port for incoming and outgoing data)
• Get your local IP by looking in to your Router (or retrieve the the IP with "ipconfig"). Lets say this is IP-A
• Verify if the ports of UT3 (or any other port you want a connection to be accessable) are forwarded. For any listed ports of UT3, the local and the remote ports has to be equal. As the remote IP use a masked IP (to allow all incoming IPs) (differs from router to router; you may check "use all" or somthing similar). Set as local ip for any forwarding setting your IP-A.
• Retrieve your external/WAN IP with a online tool (or look into your router terminal). This would be IP-ex.
• Start a instane of UT3. Create a Internet server, open up the log window.
• Use a tool to check if the ports are open. (like http://ping.eu/port-chk/). Enter IP-ex and any listed port of UT3 in the textfields and run the process of checking.
• If you got "port closed", seomthings wrong with your portforwarding settings.
• If all is working and the ports are open (some ports are not important like 6500; this port is for the MasterServer of UT3.), tell your friend your ip of IP-ex.
• Wait for connection and look into your log window and watch out for incoming connections (NetComeGo thingy)

Your friend as a client:

• Verify software Firewall settings for incoming/outgoing data. Allow UT3 for every port.
• Run UT3.
• Once logged in, open console (F10) and type in "open IP-ex". (IP-ex should be replaced by the 4 numbers and the dots).

Once it's working, you can close the log (by re-typing "showlog") and play with your friend.

[UTCollector88]

I used http://ping.eu/port-chk/

And it said the ports are closed from my WAN IP address. I turned of my antivirus firewall so it is definitely not that.

[RattleSN4K3]

Either there is no application for that port who's listening on that port or you have problems with the Firewalls (Windows Firewall, Antivirus Firewall, SPI Firewall, NAT Firewall, ...).
Or there's something wrong with the portforwarding.

It's quite hard for me/us to guess your problem but i bet it has something to do with a general network setting. Screenshots, direct examples and brief explanation would be helpful.

[UTCollector88]

It is definitely not the Windows firewall cause I turned it off.

doc1.jpg


It is not the antivirus firewall cause I have it disabled when I play. But here is the firewall settings anyway.

doc2.jpg

[UTCollector88]

It is not the SPI firewall on the router cause I turned it off and here is the port forwarding so you can check if it is configured right.

doc3.jpg

[UTCollector88]

While you are looking at doc 1, 2, 3 I used the netstat -anb command in the command prompt while I hosted a game in UT3. What I came across was interesting. I did see the ports I forwarded there but they are on the address 0.0.0.0. This is for both UDP and TCP protocols. The only difference is with the TCP the ports status are established while I hosted but with UDP there is no status. Also there is no foreign IP address listed for these connections.

I can attach another image/screenshot of the netstat result if you like?

[UTCollector88]

While you look at doc 1, 2, 3 I thought I'd share something else useful. I used the netstat -anb command in the command prompt while I hosted a game in UT3. What I came across was interesting. I did see the ports I forwarded there but they are on the address 0.0.0.0. This is for both UDP and TCP protocols. The only difference is with the TCP the ports status are established while I hosted but with UDP there is no status. Also there is no foreign IP address listed for these connections.

I can attach another image/screenshot of the netstat result if you like?

[UTCollector88]

There is a double post above this post just ignore post 26. I had some trouble with this site speed and traffic wise and accidentally posted the same post twice

[RattleSN4K3]

0.0.0.0 is normal.
http://support.microsoft.com/kb/175952/

Does your PC have the IP of 192.168.0.4?
Otherwise i don't see the current problem.

[UTCollector88]

Yes it does have the IP of 192.168.0.4. Have you looked through the files yet? I am going to test out a game with my friend on the weekend with the UT3 console to see what happens.

[UTCollector88]

I have tested hosting a campaign online with my friend and it didn't work. I had the log open when my friend tried to connect to me. The connection opened then closed, open then closed, open then finally closed according to the log which resulted to a connection failed for my friend who tried to connect to me. The same thing happened if he hosted and I tried to connect to him.

What I did after that instead was have a stun server/client setup on my computer and have it running through the command prompt while I hosted matches. I still had the necessary ports forwarded and needed to change the STUN SERVER code line in the UTEngine.ini file. After I did that my friend was able to connect to me and play without any problems.

[TKBS]

@ UTCollector.
- I tried for approx 3 years to get a server running; ever since UT3 pacthed the PS3 soundtools. - and i never could - epic truly made it hard.

-Usually with UT3, if something is not working, it is because of some really stupid + simple thing you must do;
* chances are that noone on the planet has told you how to do it. - but its not their fault- its UT3's for being such a nightmare.

** i read here ;
http://forums.epicgames.com/threads/...9#post30553879
^^ that you have Skype + a headset.

- send me you Skype name in PM- add me - and ill try to fix your connection.