Network Not Yet Reachable

Posted: Thu Oct 21, 2004 9:41 pm

Is your network reachable? "Not Yet"
Are you using a port-forward? I believe so
Is your console being detected? Yes
Brief description of your network setup: NETGEAR WGT624 Wireless router wired to two computers (one running Xlink), NETGEAR WGE101 wireless ethernet bridge connected to PS2.
Do you use a software firewall? What brand? Have you made any changes to it? No
Operating System? Windows XP
Problem description? I'm trying to play Armored Core: Nexus through this setup, but Xlink says my network is not yet reachable. Everything seems to be setup correctly except for a static IP address. I'm not sure how to get this all working as the number of text fields to fill and the number provided are different. I read this topic and everything there seems to be set up correctly on my computer (except for the mentioned static IP). I also looked into the "Wireless" window in kai config, but the MAC addresses listed on my computer are too long for the boxes in the config. So, far I've been having debug errors trying to post this thread as a help request, so i'm posting as a normal topic as dfunked told me to. Help seems to be entirely beyond my reach, as nobody's taking notice.....

[KaiUserConfig]
kaiUsername=pererrit
kaiPassword=********
kaiPort=30000
kaiDeepPort=0
kaiAccept=LOCAL
kaiTimeout=NOUI
kaiNIC=0
kaiLaunch=BOTH
kaiHomebrew=OFF
kaiPAT=OFF
kaiAutoLogin=ON
kaiWireless=
kaiUI=Default

Posted: Thu Oct 21, 2004 9:46 pm

sorry for doublepost, but this is slightly separate... I looked up at the Xlink screen just now and it says my network is reachable. I didn't do anything. Is there something wrong?

*edit*
now, it's not yet reachable again

Posted: Fri Oct 22, 2004 1:04 am

OK, take a screenshot of your port-forwarding screen. I smell an error there.. also.. to make sure you get a correct reading in "Network Reachable", switch between messenger and arena modes. This will initiate some traffic to the Orbital servers, which will then give you a more accurate response as to whether your network is reachable or not..

If your console is being detected and configured successfully, then you don't need to mess with the wireless settings in Kai Configuration Tool.

Posted: Fri Oct 22, 2004 1:26 am

The Port Forwarding Screen:

The Custom Service Screen:

*note: 192.168.0.201 is the IP for the ethernet bridge

Posted: Fri Oct 22, 2004 1:39 am

hehehe..

You forward to the PC'S IP address. NOT THE BRIDGE.

Posted: Fri Oct 22, 2004 1:52 am

okay... so then it's not .201? That would make a bit of sense, now that we've done of bit of debugging on our router. I'm really not sure where 201 came from, we now have .2, .3, and .4

That leaves me with trying to figure out which IP addy goes to which... We've got three different "attatched devices" that aren't named, or named with only "--".

Posted: Fri Oct 22, 2004 1:54 am

If you run XP on your PC, just go into network connections, and have a look at the 'Support' tab that you get when you double click the correct connection.

Alternatively, go to Start - > Run. Type in

ipconfig /all

and you'll get your network address from that.

Posted: Fri Oct 22, 2004 2:26 am

the ip for the computer running xlink is 192.168.0.3

i point the custom service to that?

just for clarification, here's a diagram of my setup:

Posted: Fri Oct 22, 2004 2:54 am

Yes, point it to the PC that runs Kai.

As long as the PC remains HARD-WIRED to the router, you will be OK.

Posted: Fri Oct 22, 2004 3:36 am

alright, that's what I did and that's what worked. thank you very much!