LAN / Firewall problem? M2

[neo123]

I'm using a Linksys WRT55AG and Comodo Firewall.

I can host and people can join but people who are on the same network as me (use same router) cannot join, it keeps saying fw. It works when we use tcp/ip (other) but it doesn't work on marius.net. Can anyone help me out here on what is causing the problem and how to fix it?

[vinylrake]

I'm using a Linksys WRT55AG and Comodo Firewall.

I can host and people can join but people who are on the same network as me (use same router) cannot join, it keeps saying fw. It works when we use tcp/ip (other) but it doesn't work on marius.net. Can anyone help me out here on what is causing the problem and how to fix it?

I am not very technically network savvy but I think I know what your problem is from a high level - network experts pls correct me if I have misrepresented anything.

UNless you are talking about a network with it's own domain or subdomain where each user has an individual internet-wide (e.g. not just a local) IP address I think your problem is caused because you only have one 'real' connection to mariusnet - Mariusnet uses the IP address of the person logging on to know who to send info to. e.g. One account per IP address. When you share a router and more than one person tries to connect to Mariusnet from the same (to mariusnet) IP address then the server (mariusnet) has no way of knowing 'which' computer connected to the router to communicate with (and it already has a user connected from your IP address (the first person on your network to logon)). Since it uses your IP address and to the outside world (mariusnet) your router/network is a single IP address it only lets one session be open from any given computer at a time.

You can have multiple players playing Myth where some are sharing a router and some are outside of the network the router is part of (over Myth's TCPIP multiplayer option) but the only way I've heard it work is when the host is on the router and everyone on the router connects to the host, then other people connect to the host directly using the host's IP address instead of through a myth game server (mariusnet).

ps. I think the reason the Host/IP-router solution above works is because when the host machine is the one with the primary IP address for your internet connection you play directly with other computers via TCP/IP (skipping mariusnet completely) - Since the host is a computer on the local network, players on the local network (router) can communicate with the host machine using their 'local' IP addresses, AND the host can communicate with people outside the router (over the internet at large) because they connect from their own IP addresses which are seperate from the IP addresses the internal network players have. The host is the only computer that needs to know where everyone is. When Mariusnet is used, even though it doesn't actually host games, it has to know where everyone is (their IP#) so that it can pass all that information to the host when the game starts.

[Doobie]

I think Vinyl summed it up pretty well.

There may be ways around this depending on our provider, your hardware, and what compromises you are willing to make. I know for example my internet provider actually provides me with two IP addresses, so if i configure one machine to use an external IP address, and and set my router to use a second i can have my internal network behind a router, and an exposed machine sitting outside the network that everyone can connect to. There may be other work arounds but that's the first that comes to mind.

[neo123]

So does mnet handle it differently then the other servers (I remember it working on pm.net and bungie)?

I kind of get what you are getting at though.

[Doobie]

nope, this restriction has plagued us since the days of bnet.