ISBoxer Not Communicating With Other PC's

Hellbound · Post by **Hellbound** » Sun Nov 15, 2009 4:03 pm

After the initial setup, I was able to run 4 characters on the same computer. What I would like to do is run multiple computers. I have two Windows 7 64bit machines, and 2 Windows XP 32bit machines. My main is a Win 7 machine and it can communicate with the other Win 7 machine.. I'm doing this through the ISboxer suite Computer "Start Multiple Computer Helper". The problem I'm running into is I cant seem to connect to my Win XP machines, nor can the Win XP machines see each other. Could I be missing something?

I have manually opened ports 10101 and 10102 on both the XP machines. Still not working.

Hellbound · Post by **Hellbound** » Sun Nov 15, 2009 5:52 pm

Also, is there a specific service in winxp that needs to be running to make the connection?

eqjoe · Post by **eqjoe** » Sun Nov 15, 2009 11:03 pm

You might have to enable uplink networking and restart from the IS configuration menu.

-j

Post by **Lax** » Sun Nov 15, 2009 11:27 pm

It's ISBoxer, not Inner Space. ISBoxer is using .NET remoting over TCP on port 10102, and IS is using proprietary TCP over port 10101. The issue is something with .NET remoting not working on his PCs.

Hellbound · Post by **Hellbound** » Mon Nov 16, 2009 3:09 am

When I use the "Start Multiple Computer Helper" I can see all three computers..

But when I try and connect to PC1 or PC2, I get this...

The only PC I can connect to is PC3

The main PC and PC3 are on Win 7. PC1 and PC2 are Win XP. I cant connect PC1 or PC2 to any machine, including each other. So something is missing on my end. Just need to figure it out..[/b]

eqjoe · Post by **eqjoe** » Mon Nov 16, 2009 4:05 pm

After you try to make that connection, do a "netstat -a" from a command prompt on both systems. You are looking for that exact connection (IP:PORT) on both systems.

-j

Hellbound · Post by **Hellbound** » Mon Nov 16, 2009 5:22 pm

This is what I got..

MainPC

PC2

Not sure what it all means.

eqjoe · Post by **eqjoe** » Mon Nov 16, 2009 10:49 pm

I would say that the netbios name Charles-PC is not the same as Charles-PC1.

-j

eqjoe · Post by **eqjoe** » Mon Nov 16, 2009 10:50 pm

That and Charles-PC is not listening on port 10101.

-j

Post by **Lax** » Tue Nov 17, 2009 2:36 am

For the ISBoxer connectivity step, 10102 is the only thing necessary (IS does not need to be running)

The screenshots show the Uplink Name on Charles-PC3 is Charles-PC. This is an Inner Space setting stored in InnerSpace.XML -- did you copy the IS folder over to your other PCs? You may need to delete that file and start clean with ISBoxer. It's possible that this is the problem here

Hellbound · Post by **Hellbound** » Tue Nov 17, 2009 3:43 pm

Lax wrote:For the ISBoxer connectivity step, 10102 is the only thing necessary (IS does not need to be running)

The screenshots show the Uplink Name on Charles-PC3 is Charles-PC. This is an Inner Space setting stored in InnerSpace.XML -- did you copy the IS folder over to your other PCs? You may need to delete that file and start clean with ISBoxer. It's possible that this is the problem here

On PC3 when I changed the name so I could easily see which pc was which, I forgot to change it in Innerspace. All PCs were originally Charles-PC..

Hellbound · Post by **Hellbound** » Tue Nov 17, 2009 4:13 pm

Its day 4 and I'm still at a loss connecting a Windows 7 machine to a Windows XP machine via ISboxer. The expensive solution is to update the XP's to 7.... But cant do that atm. But why cant I connect both XP machines together? Like I mentioned.. There is something missing. Something I havent been using that those who are connecting xp machines together are... Who is the developer of ISboxer. I may need to email him/her/they. Surely they know exactly whats needed to make a connection be it XP/7/vista...

eqjoe · Post by **eqjoe** » Tue Nov 17, 2009 4:25 pm

Lax is your guy. He wrote InnerSpace and ISBoxer.

Post by **Lax** » Tue Nov 17, 2009 5:25 pm

As I explained to you in e-mail, you could take a few extra seconds to do copy/paste and not have to worry about getting ISBoxer itself to do this part for you.

This thread is not helpful to your issue because eqjoe doesn't understand the issue any better than you do, and the only thing I have to add besides what I told you in my original e-mail is pointing out that the issue is not related to what's being discussed in this thread...

It's something to do with .NET remoting, and it's not the port itself. I don't know what it is, only that for a handful of people, they can't connect. So there are instructions provided for those people to do it the way it was done before the multiple computer helper was added.

Hellbound · Post by **Hellbound** » Tue Nov 17, 2009 9:35 pm

What you dont understand is I've gotten things to work between the Windows 7 computers.. I did exactly as explained in your original email, but still cant get the XP machines to launch.....even if I copy the files manually, using a flash drive to each machine. The XP computers are just not getting the signal from the win 7 computers to launch. I have no idea why.

I tell you whats helped me greatly on dealing with ISboxer and Innerspace, thats the video tutorials.. If only someone would make a video tutorial on connecting multiple computers, even with trouble shutting issues, would be awesome.