|
|
 |
|
|
Pages: 1
Unable to Host WC3 Game
(Click here to view the original thread with full colors/images)
Posted by: WarZombie
Hello,
I used to be able to host games without a problem but now I no longer can on RoC battle.net. I create a custom game but it seems no one can join.
- W2k SP4 all hotfixes
- Firewall shut off
- Antivirus shut off
- disabled all unecessary services
- Comcast cable modem, no router
- Tried changing to port 6113
- Tried hosting different maps
- Powercycled the cable modem
Any ideas?
Thanks in advance.
Posted by: C-Money
Suggestions...
1. Make sure you have a registered Bnet account.
2. Download & apply the latest patch.
3. Try ports 6112-6119, TCP & UDP.
4. Shut down the MS firewall & any other firewalls. (i.e. Norton, ZoneAlarm,ect.)
5. Reset your server list...
 Quote:
Steps to reset your server list:
Click on Start, and then select Run
Type "regedit" and click Ok
Click on the + icon beside the "HKey_Local_Machine" branch
Click on the + icon beside the "Software" branch
Select the "Battle.net" branch and press the delete key
Click on the + icon beside the "HKey_Current_User" branch
Click on the + icon beside the "Software" branch
Select the "Battle.net" branch and press the delete key
|
6. Run a Tracert.
Goto Run
type cmd
type tracert.exe Your Realm.BATTLE.NET (i.e. USWEST.battle.net)
Open C:\tracert.txt, & post contents.
NOTE: This won't fix your problem, but it will help us determine any connectivity problems.
Posted by: WarZombie
tracert to USWEST
1 * * * Request timed out.
2 15 ms 16 ms 16 ms 12.244.114.81
3 16 ms 16 ms <10 ms 12.119.124.17
4 <10 ms 16 ms 15 ms gbr2-p50.dlstx.ip.att.net [12.123.16.238]
5 <10 ms 15 ms 16 ms tbr1-p013301.dlstx.ip.att.net [12.122.12.61]
6 31 ms 47 ms 47 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50]
7 31 ms 47 ms 47 ms gar4-p300.la2ca.ip.att.net [12.123.28.202]
8 47 ms 63 ms 62 ms idf26-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.142]
9 47 ms 63 ms 172 ms mdf2-bi8k-2-eth-1-1.rwc1.attens.net [216.148.209
.18]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
strange... how far should the tracert make it?
Posted by: C-Money
Quote:
|
Originally Posted by WarZombie
strange... how far should the tracert make it?
|
It's capped at 30.
Well, there is definately a problem. It's timing out on the very first hop.
What ISP do you have? (i.e. AOL, NetZero, ect)
You need to contact your ISP. Ask them why the connection times out on the first hop.
Just give them your tracert info, & they should be able to tell what is wrong with the connection.
Posted by: WarZombie
Quote:
I know tracert is capped at 30 hops, what I meant is how far should the tracert make it to USWest before it starts timing out. I assume blizzard blocks ICMP at some point.
Quote:
|
Well, there is definately a problem. It's timing out on the very first hop.
|
Not really. 1st hop 100% packet loss just means that the piece of equipment is set up to ignore ping requests and to not reply at all. Many ISP's do this.
Quote:
|
What ISP do you have? (i.e. AOL, NetZero, ect)
|
Comcast
|
|
|
|
|
