xnet issues - starting xnet error message please help

[aaronb]

I have encountered the following error message when I start Xnet

System.run time remoting exception TCP channel protocoal violation expecting preamble

I am getting the XNET error on the regular PC. Below is a list of what I am running on the machine;



P4 Celeron processor

384 MB

Windows XP

.net 2.0 framework

Latest build of Xlobby

Linksys wireless G router with speed booster – recently purchased from Sam’s club

HP IPAQ (also recently purchased directly from HP) setup as a thin client which connects to Xlobby After I start XNET



The computer is setup as a workgroup with another PC that has the same error message. It is not a consistent error. I can connect about 1 out of 3 times. Perhaps it is in my router settings? The IP address of the machine is 192.168.1.101 with port 8000. That is the IP address in Xnet. I don’t know how to consistently start Xnet with out receiving that message. Please help.



Again thanks in advance

mailto:aaronandaimee@adelphia.net

[Jay]

Are you running DHCP or static IP addresses?

That address of 192.168.1.101 looks like it might be dynamically assigned and could change depending upon which machines booted up in which sequence.

I'm not sure an address change would give that error message. I run static IPs and have not seen that.

[aaronb]

I am running dynamic IPs. How do I run static IP addresses? Does it depend on the ISP? Is this something I could set on the router to assign? Please bear in mind I am new at this.

[Jay]

Again, this may not solve your problem but...

I am referring to static IPs within your LAN, not the outside world (WAN).
There will be a configuration page in your router. Usually, a router has an address such as 192.168.1.1 or 192.168.0.1 - that will be in your manual.

To enter your router, point your Web browser at it (like http:// 192.168.1.1). Once into the router-
1. find the current DNS (outside world) address which will prob be in the WAN section. Copy that carefully then tell the router to find it automatically. You're going to use that address in each of your machines.
2. turn off DHCP and tell the router you're going to assign addresses to each machine (static IP addresses).

Next, go to your machines and click on Network Connections, then right-click on Local Area Connection. Go down to Properties then down to Internet protocal - tcp/ip and click Properties there.
You currently have 'Obtain an IP address automatically' selected.
Select 'Use the following IP address'.
Here, you start a sequence of static IPs. If the server addy is 192.168.1.1,
then assign the 1st machine 192.168.1.2 (no http://) and so on. Make a note of each address you're assigning. When you click Subnet mask, 255.255.255.0 will be automatically filled in for you. The next is the default gateway that's the router address. Last is the DNS address you wrote down earlier. Mine looks like 68.87.64.146.
Hit OK and you're done.

Now. You may need to shut down then bring up your LAN to make all this work. If so, turn off all PCs and the router. You shouldn't need to touch your modem.

Bring up the router first and let it settle in. Then, bring up your machines. If you can see the Internet on them, you're good to go.

You can always go back to DHCP if something doesn't work.

A fast test of XL connectivity is turning on XL's Web server and attempting to connect with it in a browser - like http://XL_server_address:port number/setup. I think the default port is (8002?). Anyway, <F2> XNET Webserver will have that.

Let us know.

[aaronb]

I will try that and post my results. Thank you again

[aaronb]

So I called linksys to help me walk through changing to a static IP address for each computer since it was not clear on how to get there from the setup screen on the router. They mentioned there was a firmware upgrade for my router. I have the linksys wrt54gs v 6. The firmware before upgrade was 1.50.6. With the update, I went to 1.50.9. So far after messing with going to static then going back to dynamic along with the firmware update, I can connect with out that error. From my experience with this issue, Xnet will pickup the current IP address, so if the IP address changes because it is a dynamic IP address, Xlobby will correct and connect to the IP address that is present on the computer. Of course I can be wrong, but that is what appears to happen.

I really love this program and my wife is happy as well.

[Jay]

So all is well.
A router issh, but not the one I thought.
Great