Sign in with
Sign up | Sign in
Your question

Unable to Join Game on IPX LAN-StarCraft

Last response: in Networking
Share
March 16, 2006 3:36:18 PM

Here is the situation. 2 years ago I created a LAN in my home for gaming. It consisted of 4 computers networked using a Linksys Etherfast Wired Router with a 4-port switch. It worked great and all computers could play networked games as well as share other resources such as files, printers, internet, etc. Later I added a Linksys Etherfast Wired 8 port switch to the mix so when friends came over they could join in the gaming. That also worked very well and using this set-up we daily used 4 or more computers and played several network capable games such as StarCraft, Mechwarrior, Diablo II, etc. using the IPX protocols with no problems or glitches. I custom built each of the computers on my 4 computer LAN. Some of the specs are these: Computer 1-Pentium 4-2.8ghz-2gb ram-256mb nVidia video card-SoundBlaster Live sound card-Dlink PCI Ethernet card-XP Home Edition SP2, Computer 2-Same, Computer 3-Pentium 4-2.4ghz-1gb ram-128mb ATI video card-SoundBlaster Pro sound card-Dlink PCI Ethernet card-XP Home Edition SP2, Computer 4-AMD Athlon 1800+-1.4ghz-512mb ram-64mb nVidia video card-onboard sound-Dlink PCI Ethernet card-XP Home Edition SP2. This worked great for my entire network gaming and other needs with no problems. Recently I remarried and moved into a new home which is significantly bigger than my old home. My new wife did not want me to string network cables all through our new home so I decided to go wireless. I stuck with Linksys because it has served me so well in the past. I purchased a Linksys WRT54GX4 with SRX400 Wireless G Broadband Router/Switch/Access Point. I also purchased 3 Linksys WMP54GX with SRX Wireless G PCI cards. I hard wired Computer 1 to the Router since it was going to remain in the same room. Computer 2 received a wireless PCI card and at that point I tested the small 2 computer LAN and it worked fine. I was able to network StarCraft over the IPX and play with no problem. Computer 4 received the next wireless PCI card and instantly found the network and registered itself using the shared Internet connection and printed on the shared printer but when it came testing time with StarCraft I got the error message “Unable to Join Game”. It could see the game but not join it. If the game was created on Computer 4 then the other two computers on the network could not even see it. I did the forum search as well as checking Blizzard (makers of StarCraft) and Linksys web sites. I have tried all the tips I have found on these sites including switching to 802.3, creating the unique 8 digit IPX network Identifier, use of TCP/IP, turning off firewalls, NetBios, NetBui, etc. to no avail. None of these things did I have to do when it was a wired network. It always auto-detected the settings and worked perfectly. I am using the same version of StarCraft on all machines as I did when it was a wired network. My puzzle is it worked as a wired network on these 4 machines but it is not working as a wireless network. What am I missing? All 3 machines were set-up and configured the same and two work fine but the third does not. As a curiosity test I used an old laptop I had laying around with an old wireless card and it was able to network and game using StarCraft with the other two but not the third. In the next day or so I am going to add the Wireless PCI card into the last machine and see if it has the same problem or if it works error free. Meanwhile does anyone have any suggestions on what I can try or check to get the outcast computer to join my gaming loop? TIA, Lost.
March 17, 2006 3:47:03 PM

For me, windows xp has had the tendancy to enable the firewall on new network cards installed in a system. Check and make sure the windows firewall is off (or any other firewall for that matter). Or have the apropriate ports opened for starcraft, I believe it is just port 4000 TCP.

Man I love starcraft, it is good to hear someone else out there is still playing it :) 
I wish they would make a new one sometime. Keep all the game play the same but slap a new shiny graphics package on it, lol. If starcraft had AOEIII graphics it would be ridiculously awsome.
March 22, 2006 1:19:17 PM

Yup, i've been there done that one with C&C RA. What I think fixed it for me was some of the pcs needed to be 802.3, and others set to auto.

Another problem that I had is that if you have more than one nic, it gets pissed off about it. If you disable all other ways out, like a second nic or a built in 1394 lan interface, that will most likely help as well. I know that in C&C RA2 it gave me the option to choose which card to use, and it listed a few even though only 1 worked.

You can try the network thing again, I think you need to set them up as 10000001, 10000002, 10000003 to make that part happy. I'm not sure if I had to mess with that though, it probably wouldn't hurt.

If none of that solves the problem, I'm not exactly sure what else causes it, but I've had the same thing happen. You may even be able to get the game to launch if you switch who is hosting it, as some computers can see each other, and others can only see certain ones. Good luck though.
Related resources
March 22, 2006 9:27:35 PM

I too have had wierd problems with certain machines not being able to see others on Windows XP using IPX game (RA2).

The way I eventually solved it was by creating a VPN with Hamachi (www.hamachi.cc) and adding the IPX protocol to that :/ 
March 22, 2006 10:37:08 PM

What about doing udp instead of ipx? I'm pretty sure starcraft has that option, been a while since I did a network game though.
July 24, 2006 12:20:25 PM

if it helps i've used ethernet II as the frame type

and i've got a wireless laptop, and two wired desktops in a successful starcraft LAN .. all running win XP

I've given each pc the same external network number and unique internal numbers. In my case i've used
10000002
10000003
10000004 .. for the internal numbers

and

22222222 as the external number on all pcs

I've tried 802.2, 802.3 and autodetect, all of which i can't get working with the wireless laptop


this was the only help i could find on the net, so hope i've made a useful contribution

cheers
October 19, 2006 4:32:54 AM

Quote:
if it helps i've used ethernet II as the frame type

and i've got a wireless laptop, and two wired desktops in a successful starcraft LAN .. all running win XP

I've given each pc the same external network number and unique internal numbers. In my case i've used
10000002
10000003
10000004 .. for the internal numbers

and

22222222 as the external number on all pcs


IT DOES HELP!!!!!
I spent about 6 hours yesterday and 2 hours today trying stuff to get Command and Conquer: Red Alert 1 to work over IPX/SPX in Windows XP and this is the first time it's worked! I haven't tried wireless yet, but thank you so much!
October 21, 2006 10:20:13 AM

no worries, buddy
i've been playing starcraft on a laptop ever since, works like a charm :D 
June 2, 2007 6:22:01 PM

I had the same problem like the rest of you guys.

This is what I did to make my wireless connection on laptop and cable connection with desktop using wireless router connect thru IPX.

Game used : Starcraft
OS: WINXP
Router: Linksys WRT54GC
Laptop: wireless connection wifi
PC Desktop: direct lan connection cable

It took me awhile and tweaked the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol properties here and there and resulted to this configuration that worked well with IPX games using wired and wireless connection.

DESKTOP CONFIGURATION:
I've setup the Internal network number to: 10000001
Then change the Adapter(Frame type) to : Ethernet II
Then change the Network number to: 22222222

LAPTOP CONFIGURATION:
I've setup the Internal network number to: 10000002
Then change the Adapter(Frame type) to : Ethernet II
Then change the Network number to: 22222222
August 12, 2007 10:35:38 PM

I had the same problem as everyone else here, except I was trying to get Diablo 1 going on a LAN using IPX / SPX. Mikaztro's solution worked perfectly on my two laptops, which are both wireless. One laptop is running XP and the other is running 2000, both have different brands of network cards.

All the laptops can see and join any Diablo 1 LAN game, no matter who created them. Thanks guys, you saved me a bunch of time! :D 
October 10, 2008 2:27:57 PM

thank you bman212121 - disabling the other NICs worked on Windows 2003. yay

January 1, 2009 7:12:01 PM

Quote:
if it helps i've used ethernet II as the frame type

and i've got a wireless laptop, and two wired desktops in a successful starcraft LAN .. all running win XP

I've given each pc the same external network number and unique internal numbers. In my case i've used
10000002
10000003
10000004 .. for the internal numbers

and

22222222 as the external number on all pcs

I've tried 802.2, 802.3 and autodetect, all of which i can't get working with the wireless laptop


this was the only help i could find on the net, so hope i've made a useful contribution

cheers


aourus, thanks a lot!!!
May 24, 2009 9:24:36 PM

THIS WORKS FOR Me To!!!! (quoted below)

(I tried so many other things with my new Linksys WRTGL router and McAfee firewalls and more and it wasn't until I tried this IPX internal and external #'s with the Ethernet II that I found success. I'm running XP Service Pack 3, McAfee has been configured to trust the wifi network, and Strarcraft has full access to the network through the McAfee manage programs)

bickelj said:
Quote:
if it helps i've used ethernet II as the frame type

and i've got a wireless laptop, and two wired desktops in a successful starcraft LAN .. all running win XP

I've given each pc the same external network number and unique internal numbers. In my case i've used
10000002
10000003
10000004 .. for the internal numbers

and

22222222 as the external number on all pcs


IT DOES HELP!!!!!
I spent about 6 hours yesterday and 2 hours today trying stuff to get Command and Conquer: Red Alert 1 to work over IPX/SPX in Windows XP and this is the first time it's worked! I haven't tried wireless yet, but thank you so much!

June 6, 2009 4:03:28 PM

Guys,

Following solves this problem of "unable to join..." in Starcraft:

Only tested on Windows XP so far:

Goto LAN Properties and then goto IPX/SPX properties, then assign any non-zero "Internal Network number" in the given column.
The "Frame Type" can remain at the default "Autodetect" option.

However on each PC, a different non-zero "Internal Network number" under the IPX/SPX would have to be assigned.

The above definitely solved the problem of "Unable to join game" in Starcraft


June 28, 2009 12:35:51 PM

aurorus said:
if it helps i've used ethernet II as the frame type

and i've got a wireless laptop, and two wired desktops in a successful starcraft LAN .. all running win XP

I've given each pc the same external network number and unique internal numbers. In my case i've used
10000002
10000003
10000004 .. for the internal numbers

and

22222222 as the external number on all pcs

I've tried 802.2, 802.3 and autodetect, all of which i can't get working with the wireless laptop


this was the only help i could find on the net, so hope i've made a useful contribution

cheers

June 28, 2009 12:37:34 PM

hi bro, every1 seem to know how to did what "aurorus" said, but i dont know how to do that?. can any1 here show me how to set it up like u guys saying. i m new, i dont know how to do that, so show me step by step if u can.
January 12, 2010 8:20:07 PM

Guys, if you don't set "network-> properties-> tcp/ip->advanced->WINS->allow netbios on tcp" this will not work.
Greetings.

Luca
February 23, 2010 7:40:52 PM

What about the same issue with Command&Conquer 3 on one machine running XP x64 and the other running Windows 7 64-bit. The Windows 7 machine can see games made on the XP machine as well as the XP player in the chat room and the messages that player sends, but the XP machine can not see games, the player, or messages from the Windows 7 machine. When Windows 7 tries to join the games made by the XP machine it either times out, or flat out fails to join. There is no firewalls of any kind running, all AV has been turned off during game play, and we have tried over 10, 100, and 1000 wired Ethernet, G wireless, and N wireless. No difference.
The computers can see each other just fine for file and print sharing both directions. Just no games will work over the network. Same problems with all C&C games, SC, all Diablo games, and about 15 other games ranging from the Windows 95 era through games that have came out in the last 2-3 months that are fully Windows 7 capable.
July 21, 2010 11:01:48 AM

Reading all of the above tells me that i need a router to play STARCRAFT 1 with laptops.

how about playing it with 3 laptops?? no router needed.. is this possible? i mean that we just open up our own wifi network. everyone connects and we play!!!

this works with warcraft frozenthrone but it doesnt work with SC1.

can someone please help me out?
March 18, 2011 10:33:23 PM

> Control Panel
> Network Connections
> Local Area Connection/Wireless Network Connection
(Depending on the type of network you have)
> Properties Tab
> "General" Tab
> NWLink IPX/SPX/NetBIOS Compatible Transport Protocol

Here is where you find and modify the internal and external network numbers, and the network frame type previously mentioned.
July 11, 2011 4:31:16 AM

This is the solution to playing old ipx games over a wireless xp network.Command and Conquer,warcraft 2,starcraft,diablo,etc...

Step 1: Install the IPX protocol thru network properties on every cpu.

Step 2: Open the properties of the IPX settings.

Step 3: Use different internal network numbers for each cpu.10000001,10000002,10000003,etc...

Step 3: For computers connected by wire set the frame type to Ethernet II and for wireless computers use Ethernet SNAP.

Step 4: Set ALL external numbers to the same address.like 22222222 or something.

Step 5: Play your LAN game and have fun!

If the steps above don't work perfectly you can use wireshark on each nic to help you troubleshoot all the settings correctly for your network.
!