Print

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

[Helmaroc]

I know, these are the Bay12 forums, yadda yadda, but I can't seem to log in to the Battlenet forums and I know there are some Warcraft players here.

Anyway, no one can join games I host. I have ports 6112-6119 forwarded (set to Both). I have firewalls turned off. For a month or so I could host just fine, then all of the sudden I couldn't anymore. Any ideas?

[Jay]

DHCP leases last around a month.
Did you not set your internal IP up to be static?

[Helmaroc]

Thanks for the quick reply.

I tried, but I don't think it worked...I'm pretty sure I couldn't connect to the internet at all after I messed with my IP so I reset to default settings. I will try to setup a static IP again. Could it be anything else?

[Heron TSG]

Did you make sure to get someone to join a hosted game? Nowadays they might have just been in the bot games instead of yours. Try putting 'DOTA' in the name.

[Helmaroc]

Did you make sure to get someone to join a hosted game? Nowadays they might have just been in the bot games instead of yours. Try putting 'DOTA' in the name.

I've set up copycat games (Risk for instance), I'm sure that people can't join. My friend tells me the game hangs, buttons turn grey, and says game cannot be found.

[debvon]

Yeah, warcraft 3's battle.net has been FLOODED with shitty hosting bots, and the game has almost literally been deserted. At least there's not as much dota spam anymore.. but it's probably even worse now, every damned game is autohosted. Even when I use the ghost++ bot to host a game (which you should use too, but don't autohost) it's really difficult to get any players to join. So who knows, you may actually be able to host but people aren't joining?

edit: Ahh, well it looks like you can't host then. Again I suggest getting the ghost++ bot, once you get it configured correctly you'll be able to host from LAN and it's really easy.

[Helmaroc]

I might look into ghostbot++, debvon.

I followed this to set up a static IP, and I didn't fix the problem. Here is a screenshot of the configuration.

Before I made any changes, 'Obtain an IP address automatically' was selected. If I check 'validate settings upon exit', I seem to lose connection and Network Diagnostics starts to run (does not find any solutions). If I just click 'Ok' without checking validate, I don't seem to notice any difference.

Spoiler (click to show/hide)

[Jay]

Can you give me a shot of the ipconfig -all output?
I've never seen two separate DNS servers on the same octet before.

EDIT: Also, you're probably trying to assign yourself an IP within the DHCP coverage.
I never saw any problems when I tried that, but nowadays, I have it set to start at .105, and my IP is static at .101
No problems with internet coverage until something causes the DNS servers to change.

[Helmaroc]

There you go. I am a noob at anything network related, so if I have made some dumb mistake or something I apologize.

Spoiler (click to show/hide)

[Jay]

That's what you get when you're obtaining an IP automatically?
Odd..  it should be using DHCP...
If the internet works while it's displaying that for ipconfig -all, it should work with how you set it before.
As what you're doing is just setting it to keep those settings, rather then have your IP change when the DHCP lease expires.
Very strange.

If nothing else, you can continually change the IP it forwards to to match your new dynamic IP.
But that shouldn't be necessary.

[Helmaroc]

If nothing else, you can continually change the IP it forwards to to match your new dynamic IP.
But that shouldn't be necessary.

How would I go about doing this?

[Jay]

Same way you forwarded it the first time, but change the IP on the old listing to the new IP.