Search found 8 matches
- Wed Nov 26, 2008 5:55 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
Sorry, I would, but that's not how this router works. :P You don't actually type in a rule like you would on a command-line system, it's all menu-driven. You basically create a rule for a port (or multiple ports), specify TCP or UDP, then after the rule's created, you assign it to a computer. Like I ...
- Wed Nov 26, 2008 1:37 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
Nope, in this case it's external. It's basically listing for that specific server, which ports on <IP address> forward to it. This is just from the routing overview page listing all the forwards.
- Tue Nov 25, 2008 10:07 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
it's the router's external IP, it has nothing to do with the functionality though, that's just how my router displays the info. it's basically saying all of those ports are forwarding to my server.
- Tue Nov 25, 2008 8:57 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
yeah, like I said before, from inside my home network it seems to work fine, but outside it doesn't...and I'm absolutely positive the ports are forwarded correctly.
Home IRC IRC (Internet relay chat) server
TCP 6667
<home IP>
UDP 6667
<home IP>
TCP 6697
<home IP>
UDP 6697
<home IP>
TCP ...
Home IRC IRC (Internet relay chat) server
TCP 6667
<home IP>
UDP 6667
<home IP>
TCP 6697
<home IP>
UDP 6697
<home IP>
TCP ...
- Tue Nov 25, 2008 8:41 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
I think this is what you're referring to:
listen *:6697;
listen *:7029;
{
options
{
clientsonly;
};
};
listen *:8067;
listen *:21090;
listen *:7029;
listen *:6667;
I put it in both sections just now to try it, and it still does nothing. "Connection refused", and no new entries in the log ...
listen *:6697;
listen *:7029;
{
options
{
clientsonly;
};
};
listen *:8067;
listen *:21090;
listen *:7029;
listen *:6667;
I put it in both sections just now to try it, and it still does nothing. "Connection refused", and no new entries in the log ...
- Tue Nov 25, 2008 8:00 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
ok, I got it to try to connect now, but it's failing with "Connection refused". The log file has nothing useful:
[Tue Nov 25 10:22:22 2008] - Connect - steve!steve@localhost [VHOST rox-1F3914C]
[Tue Nov 25 10:22:53 2008] - Disconnect - (0:0:31) steve!steve@localhost [VHOST rox-1F3914C]
It started ...
[Tue Nov 25 10:22:22 2008] - Connect - steve!steve@localhost [VHOST rox-1F3914C]
[Tue Nov 25 10:22:53 2008] - Disconnect - (0:0:31) steve!steve@localhost [VHOST rox-1F3914C]
It started ...
- Tue Nov 25, 2008 3:30 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
Ok, I know the server works, I was able to connect directly on the server using the loopback, so I just created a new IRC rule, adding for ports 6667, 8067, and 6697 (TCP and UDP, just in case), but I still can't connect externally, so I don't think it's a router issue, but it also doesn't seem like ...
- Tue Nov 25, 2008 3:03 pm
- Forum: Unreal 3.2 Support
- Topic: Connection problem
- Replies: 22
- Views: 11804
Re: Connection problem
Sorry to hijack this thread, but I'm having the exact same problem at home. I have the same listen block (copied right out of the example.conf), and my router's firewall (crappy little 2Wire DSL router) has a bunch of built-in firewall exceptions to choose from one of which is for IRC (it forwards ...