Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[torano]

Hey all. I have been using the default Gamefuel settings for World of Warcraft until I needed to add another PC on my network that needs the same settings. Should I abandon Gamefuel and use something that just opens the WoW ports for all computers? Or what do I do? Gamefuel seems to only work for one PC.

[FurryNutz]

Did you add the 2nd PC to the GameFuel rule and give it a different priority? I haven't done this as I haven't used multiple PCs online for gaming in a long time and usually just did a LAN party the last time I did.

I presume that just adding the 2nd PC to the Gamefuel rule should work as it does for multiple game consoles. Just make sure you assign a static IP to the 2nd PC and give it a different priority number. All other ports for WoW should remain the same.

Let us know if this works.

[torano]

Ugh. Just looked at my router and it's actually just the Gaming settings I used. It had WoW auto populated so I used that for one IP. So, I assume I can't set another one up there for WoW for another IP. Gamefuel looks a bit complex - do I need to use that? When is it better to just use virtual server, special apps, etc?

[FurryNutz]

Ya you could try using Virtual server. Input the same information as you see in Gaming. You could try gamefuel, it's really not that complicated.

[torano]

This is frustrating. I just want to open TCP and UDP Port number 3724, 6112, 6113, 6114 and 4000 for all systems on my network. Seems like I can only do this for one static IP.

Gamefuel isn't the solution, I don't think. I'd love to be able to use the Gaming option but that is only for one IP - not more than one.

EDIT: Ok, I think I got it. This will open the necessary ports for WoW for all computers on your network. Found that port 3724 is the trigger port - so when this port is triggered, it will open the others for inbound.

Under Advanced --> Special Applications --> "Application Rules"
Trigger ports: Both 1119,3724,4000,6112-6114
Firewall ports: Both: 1119,3724,4000,6112-6114

Will test more and report back with problems.

Edit2: Didn't work. Only seems to open the ports with the WoW launcher up if at all. Not while in game. No idea what to do here. Seems only ports can be opened for one static IP and no more on the d-link.

Edit3: This is not an issue specific to d-link. Found this thread with similar problems: http://forums.whirlpool.net.au/archive/1115164 -- I'll just deal with it.

[FurryNutz]

Try setting up the Gamefuel rule for each. It works will for 2 consoles and I bet it will work for PC gaming too.

[torano]

Try setting up the Gamefuel rule for each. It works will for 2 consoles and I bet it will work for PC gaming too.

I can figure out the LAN ports and IPs, but what do I put for WAN?

[FurryNutz]

try using the Remote IP range I put in the sticky. Thats a global setting. See if that works.

[Hard Harry]

Try setting up the Gamefuel rule for each. It works will for 2 consoles and I bet it will work for PC gaming too.

Well it could be a little different. A console is built to run games, so the games have direct access to any connection the console has. PC games run inside the PC, so there is a added layer of complexity. Not saying your wrong.  Your probably right, but I have seen differences between the two. It too bad, if it was all P2P standardized, PS3 COD could vs PC COD. Epic!

[FurryNutz]

Oh I do understand it could be different. What makes helping others and giving information so much harder. Trying to figure how best to get it connected and have it work well on all platforms. Ya, It would be nice if it was all standardized. Can you imaging? PS3 vs Xbox vs PC COD? Even more Epic. LOL

OP, I would try various settings, try them all and see. Let us know what you find out.