Octopus 1.3.8a - .NET / C++ Hybrid Boxing Software

[RogueLover]

ahhh. thanks!!

[bbailey_23]

OK, the next person to make a writeup on anything needs to double space.. my eyes are bleeding now from reading the above install guides.

[bbailey_23]

alright im not sure where to even begin to ask for help here.. iv been over bother user guides and im still at a loss here. 3 hours of messing with this thing and still nothing

from what i can tell iv got all my info in right to get started up here but i still am having troulbe connecting to locallhost.. any advise here?

[Ughmahedhurtz]

Tell us about your system configuration. Need more info to even begin to guess where your problem is.

[skarlot]

if localhost is dropping when you start the server then it's something that has been reported (once) but I havn't the time to solve it yet.. pretty much nothing will work. Basically its looking for a ping response every second, and drops after 10. If you have 2 PC's.. well you shouldn't be connecting the client to localhost... but to the server IP/hostname instead. localhost is a loopback reference to the local machine.

[eagleeyee]

oh how do I upgrade from 1.3.5 to 1.3.5f I have saved all my variables in 1.3.5



*update nevermind got it updated with all my settings*

[VlyZy]

I can't connect via Octopus on either PC.

The network name is one of my issues, and I think having one PC being wired, while the other wireless.



I followed the instructions to a "T" (minus the other settings for more than two computers), also I didn't use "Work", but "Alt" (no quotes) and I got the error message on both PCs:

Failed to connect with localhost : 7612.



I skimmed through the instructions again and changed them to the SSID. Both computers have the same SSID, so when I clicked "Connect" in the "Status" tab (mind you I replaced localhost to the SSID name here too) I got:

Failed to resolve Belkin... : error 11004


Mind you Belkin is just part of the SSID name (the "..." is not part of it).


What am I doing wrong? Could it also be due to the fact that one computer is wireless and the other is not? Also I have two XP versions (Home on Desktop, Media Center on Notebook).

[skarlot]

Firstly, it should accept IP addresses (ie 1.2.3.4) in the connect field.

If you try to use "localhost" on the 2nd PC to connect to the server, it will try connect to itself instead. Localhost is a reference to 127.0.0.1 which is the loopback address, and it's defined under c:\windows\system32\drivers\etc\hosts.

Any other name you add to that file also resolves into an IP address, it's like windows own DNS... which is useful to use sometimes when Windows inbuilt auto resolving stuff just fails. Vista seems a bit smarter at it than XP.

The SSID is just a wireless identifier and unrelated.

Usually you can connect to the PC name as you would see it under network neighborhood (this name is defined in control panel/system config or something). Software firewalls may get in the way.

If that fails, the quickest way to see the IP is to open up cmd, type ipconfig and look for the right adapter. That IP will work, but it changes if your using DHCP on the router. Routers usually also allow fixing MAC addresses (uniquely identifies the network adapter) to specific IP addresses. Then if its troublesome, you just add it to the hosts file and never have any problem with it. Using the ping command in cmd will indicate whether a hostname is resolving... and hopefully if your network is ok. Using telnet can indicate whether one PC can connect to a certain port on another.. in this case 7612.

Theres a few pointers.

[VlyZy]

My bad on the first part, I didn't realize until this morning that when the "Connect" button it greyed (trying to connect) it keeps making the list longer, which is why I never saw the first six lines.

Connected to localhost : 7612.
localhost (127.0.0.1) connected.
Broadcast paused.
Removed hooks.
localhost removed.
Server closed connection.

Then after all that it repeats "Failed to connect with : 7612".

Not sure why server closed the connection.

The only firewalls I have are from XP and the Belkin router.

So if I'm reading the post right, "localhost" (w/o quotes) should only be used on the MAIN PC to connect? Then on the 2nd PC, I should type in MAIN or the name I gave the PC when I installed XP?

Thanks for the reply.


EDIT: I closed down Octopus and re-opened it and now it says:

Connected to localhost : 7612.
localhost (127.0.0.1) connected.
Broadcast paused.

It makes all the sounds for the broadcast keys too ("Pause/UnPause...)

I NEVER went into my router settings either, should I still add this program to the router to be safe (so it doesn't lose connection during gameplay)?

Also still not sure how to have the second computer connect. The MAIN computer only lists localhost, and nothing else. I typed in the MAIN PC name that I gave it when installing XP into the 2nd PC, but it gives me an error 11001.

[skarlot]

First of all error 11001:

"Host not found.No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database."
The first list of log entries looks like you started then stopped the server and it is ok. Then once its stopped, the client shouldn't be trying to connect any more. The start button is a toggle button!
You don't need to use localhost on the server, it will put it in automatically and then connect.
I'm not sure where MAIN is coming from, any hostname must resolve into an IP address. If MAIN is used in a tutorial, its the name of someone elses machine


When I said about using the router to lock IP addresses, it's not because it will break mid session, but rather DHCP (on the router) will probably issue a different IP each reboot (or re-enabling the network adapter). It's not the only way to create a static IP, it can be done via network config anyway for the network adapter.

Ok so if you can't use your PC name like you tried, you might need to mess with this stuff.... that's all. I've given lots of info but you need to read it. You need to use an IP or valid hostname on the 2nd PC to connect, and no firewall must be in the way. I can't make it more clear. Ie, the PC name works under ideal circumstances, but in my experience as well it just doens't work neccessarily, especially with XP.