Author Topic: Ouka - Trouble connecting (Read 8589 times)

LisaDee · « **on:** June 05, 2008, 05:05:50 pm »

Hi, was wondering if someone could give me a little advice on what i am doing wrong,,,I dl'd the Ouka chat server, set my ports in router and firewall, but doesn't seem like I'm able to connect,,,the pull down menu never gives me the option of 'Connect to WPN' or the management situation option,,,,Thanks

reef · « **Reply #1 on:** June 05, 2008, 07:46:40 pm »

Hi LisaDee.... if your talking about this latest version of ouka that was just released recently,i just ran it to check it out and had the same problem at first. What i did was remove all the ouka files and unzip them again,and changed the port number in the "Server Configuration Settings file" to the port i forwarded in my router. I then ran the server and it did connect.... closed it down and made other changes and it worked ok after this. Not sure why it wouldnt connect the first time around,but ya might want to give this a try and see if it works for you also. If not post back and somebody will have a solution for you i'm sure.

LisaDee · « **Reply #2 on:** June 05, 2008, 09:23:56 pm »

Thanks reef,,,yes it was the latest version that I dl'd,,,I'll give your suggestions a shot,,,,thanks again for your help,,,,I'll post back if i have success, or if not,,,,,

LisaDee · « **Reply #3 on:** June 05, 2008, 10:12:47 pm »

Hi reef, I did what you suggested,,,,and still, not connecting,,,,may I ask what port number are you using,,,,I have mine set at TCP 6690,,,,if anyone else has any suggestions, please help,,,I've been hosting a room on winmx with wcs and when the cache went down the other day, it stopped working for me, so i decided it was time to give Ouka a shot, but needless to say, I'm not having any luck with any chat server,,,,PLEASE help

reef · « **Reply #4 on:** June 05, 2008, 10:17:26 pm »

i dont use ouka i was only checking it out and was running it on port 56698.... i use WCS 1.8.3 and have been running it on this cache for about 6 months WPNCaches=caches.winmxworld.net that should fix yer wcs probs

Bearded Blunder · « **Reply #5 on:** June 07, 2008, 04:23:12 am »

currently that config entry will make no difference whatsoever as the dns for caches.mxstuff.org is a CNAME to caches.winmxworld.net making it a totally redundant entry as it resolves the same in either case..

this is the case at this moment, should i decide to alter it you may rest assured it'll still point to live caches afterward

GhostShip · « **Reply #6 on:** June 07, 2008, 06:21:40 pm »

I see no reason why it should have to route through mxstuff at all, I would use the community address Reef suggested, that is after all not likely to disappear overnight.

Bearded Blunder · « **Reply #7 on:** June 07, 2008, 08:49:53 pm »

i see no reason why ppl need to mess with their config.. since the mxstuff domain has been transferred to myself it's hardly likely to vanish overnight either...

GhostShip · « **Reply #8 on:** June 07, 2008, 09:57:11 pm »

I get the idea your politics are not in alignment with my own Bearded, its a simple peice of advice I give and no one will suffer from taking it, some folks have had problems over the last few days connecting, I note you didnt mention that here.

Lets be clear your only real reason for wanting folks to use the "stuff" domain is so they have to connect via yourself, yet another little fiefdom instead of helping the entire community is all I see going on.

Bearded Blunder · « **Reply #9 on:** June 08, 2008, 02:52:06 am »

that's because that would be your motivation..
had it been mine ask yourself why i didn't *instantly* change it back to point at my own cache & some others

i've seen enough mistyped config entries in various help rooms to merely be interested in obviating the risk of such..
and of course time wasted on pointless (in terms of function) excercises

I'm sure there were some breif connection difficulties in some cases where dns took longer to update my point in posting was to point out these were (or should be) resolved now & that caches wouldn't be the issue if someone's wcs had issues...

whatever our politics may be they wern't involved in it.. at least not on my side.. you drag yours into everything.. but that's another issue... you see empire building everywhere solely because it's your motivation in everything yourself

GhostShip · « **Reply #10 on:** June 08, 2008, 08:08:21 am »

Not content with calling me names in the Host section where an identical discussion is going on you continue to make more claims here of things you do not and cannot understand it seems.

Lets let the folks decide for themselves what they want to do, here is a diagram to demonstrate the issue at hand and the lower solution is the one we propose.

Also lets be clear on one further matter I no longer run this "Empire" as you call it, I havent however left the community nor left folks unable to connect, and I havent threatened to leave the community either regardless of impact, unlike some.

This is a no brainer for most, use a simple solution or use one thats not so simple, the choice is yours folks and the reason this discussion even got rolling was that people where having problems connecting and a working solution was suggested, what more is there to say on the matter ?

Bearded Blunder · « **Reply #11 on:** June 08, 2008, 08:31:38 am »

it's up to you folks..

you either decide wtf.. there's no point messing with what ain't broke...

i took in a domain i truthfully didn't really want responsibilty for simply because i like & use both WCS & WCB i don't want to see the drop in userbase likely to result from widespread connection issues & required config mods with either...

i'm motivated to keep both online & connecting because i USE both....

or you can all rush off & modify your config for WCS .... just because Quicks (who uses neither) thinks you "ought to"....

i'm sure that's massive motivation for him to keep things running smoothly for you...

and a final check you can all duplicate should you wish

Quote

C:\Documents and Settings\Beardy>nslookup caches.winmxworld.net

Non-authoritative answer:
Name: caches.winmxworld.net
Addresses: 78.47.24.173, 78.105.170.174, 90.207.168.54, 74.208.71.148

alternatively:

Quote

C:\Documents and Settings\Beardy>nslookup caches.mxstuff.org

Non-authoritative answer:
Name: caches.winmxworld.net
Addresses: 78.47.24.173, 78.105.170.174, 90.207.168.54, 74.208.71.148
Aliases: caches.mxstuff.org

so off you all go & mess with your config.. as you can clearly see from the two responses above.. it's going to make a HUGE difference getting the same cache ip addresses back....

on a personal note i did not (if you read CAREFULLY) call you a knob in the hosts section.. i said you were ACTING like one on this issue.. a point plain to anyone looking closely...

GhostShip · « **Reply #12 on:** June 08, 2008, 09:26:42 am »

Its been explained to you simply why advice was given and why that is the advice of this site if you want to rant off-topic about me then be clear about it.

You have threatened to leave this community before and I for one would rather folks used the community umbrella to connect with rather than rely on someone who may or may not leave at any time leaving others in trouble, if you continue to give reassurances that you will stay to support the affected software I am happy to hear that, but that does not affect this sites view on whats best in the long run in terms of keeping solutions simple.

We shall agree to disagree on this matter, the rudeness you deliver is perhaps a sign of unresolved issues that have no place in this thread.

Bearded Blunder · « **Reply #13 on:** June 08, 2008, 10:12:10 am »

i've been fed up as we all have at times with all the stupid fighting about in many cases non-issues (such as this one)....

the only things i've actually left though is groups which i've perceived to have become corrupt & self-serving...

the fact that this covers most major groups within the community is unfortunate & has at times made me wonder if it's worth bothering.. as indeed i know very many others have wondered...

nevertheless i've remained part of the winmx community as a whole & have no serious intention of that changing.. though i wouldn't be surprised if i make remarks to the effect it hardly seems worth it again...

your attitude being exactly the type of thing that makes people wonder in fact.... after all look at the way my efforts to support the continued use & development of wcs have been greeted by you here......

GhostShip · « **Reply #14 on:** June 08, 2008, 10:21:43 pm »

Quote

i've remained part of the winmx community as a whole & have no serious intention of that changing

I,m happy to hear this, but and I ask you this again, what would you propose in our boots ?
I ask this after seeing sites come and go whilst not a lot of effort goes into ensuring it cant happen again and with the best will in the world even you must admit routing all the connections via the stuff site fits the bill of a single point of failure, this is and will continue to be my only concern.

I,m also happy to hear you are interested in supporting WCS, I can accept that as something positive for the community to take on board, please dont let them down Bearded, I shall say no more.

Bearded Blunder · « **Reply #15 on:** June 08, 2008, 10:54:32 pm »

if i say, i dunno, get hit by a truck, & then can't look after the mxstuff dns, ppl are suddenly in the position they would have certainly been had i sat back & done nothing.. i.e. obliged to make config changes or get a recompiled version (in the case of wcb) in order to connect...

meanwhile for the majority who don't read this site, i've done my bit & there's been little or no disruption..

for those who do, they then have the choice.. either alter their config now.. or, since everything works, leave it be & make that alteration in the event it *should* prove needful...

meanwhile, as was the real point to posting here, if someone is *currently* experiencing connection issuse with wcs, while making this config change won't do any harm, it's also *no longer* going to cure it & they'll need to find the actual issue...

in your boots? i *might* accept there's no cause to alarm ppl or put them to any bother.. since things *are* being looked after... theoretically the wmw dns could also go haywire, owing to something unforseen, or even a disgruntled individual with access wrecking the settings (also a single point of failure), personally i don't think it's likely for either domain, if it did.. those who've made your mod would have to wait till you fixed it, those who hadn't would be waiting on me corrcting it, & depending purely on who noticed first, one would see a correction faster than the other...

i see no big deal here, i'm damned if i see how you see enough of one to make a huge thread out of... whole point is.. the short interruption to service has been dealt with by a change of domain ownership.. hopefully when those who have the data & files sort things out the site will also return, meanwhile things should be running at least..

Me Here · « **Reply #16 on:** June 09, 2008, 01:26:14 am »

I'd like to point out that this discussion started because someone was infact having problems and low and behold adding the entry to the config file for WCS fixed the issue, which tells me it was a dns problem (being resolved or not). This person was even capable of copy and pasting that entry correctly ( something you seem to have doubts that a host is capable of doing correctly)

If you had let users know here or in the host section (where we post things hosts might need to want to know) to let someone know ownership was being transferred then we might not have posted anything. The fact is I posted the information for users in the host section, Reef read it and posted it here for this user. If I wanted to *alarm* ppl I would have posted 'Its Time To Panic' on the front page and in the news section.

By your reasoning I should have 'known' it was all being resolved and 'handled' and should ignore the users i did encounter having problems and told them 'I have no idea what you should do or whats wrong, maybe close your rooms or move to a different chat server maybe you should leave winmx all together' I mean come on Merlin we're not psychic and your initial post in reply to my instructions had your usual sarcastic tone about being a waste of time and useless, when in fact we had no idea what you and KM are doing, it was a simple procedure for 'those having issues' it was never mentioned that we should have everyone in the world changing the config if they had no problems. Your reaction to those instructions is frankly alarming to me, that your so bent against anyone changing the config.

Frankly Im glad KM didnt leave everyone in the lurch again, and left this up to someone, Im also glad to hear you plan on keeping it pointed at the dns although using the chatpcs.winmxconex.net would be better as those caches are configured for optimal chat server connections.

I absolutely see NO harm in anyone adding this simple entry to the config of wcs for optimal connection, I would have much rather learned that mxstuff was indeed changing hands to you and not just being shut off in an appropriate thread and in an appropriate time, not after the fact, and not in some sarcastic reply to me trying to help hosts keep things running smoothly.

reef · « **Reply #17 on:** June 09, 2008, 04:03:31 am »

I think it's great that you decided to take on the mxstuff domain Bearded,even though you mention you didn't really want to.As a WCS and WCB user myself i'm glad to hear that things are back to being stable and should be stable well into the future (unless ya get run over by a truck) lol .But in the end WinMXWorld is a help site and there were a handful of hosts experiencing connection issues while the mxstuff domain was being transferred over to you and we simply mentioned an alternative cache to get them back up and running,its not like there was a massive wmw campaign effort to get all WCS Hosts to change their configs. Not long ago when you were a main figure here on this site (and a well respected 1 by many, "myself included"...and still well respected by many... "myself included") i have no doubts that you yourself wouldn't have suggested a quick fix method to help people get back up and running. It's not a big deal and if those hosts choose to enter the mxstuff cache back into their configs, it takes a matter of 10 seconds.I don't think any of this is helping "LisaDee" the person who was inquiring about some help, so lets all move on to doing something we enjoy doing and let this 1 rest peacefully

Bearded Blunder · « **Reply #18 on:** June 09, 2008, 08:56:41 am »

Quote from: Me Here on June 09, 2008, 01:26:14 am

I'd like to point out that this discussion started because someone was infact having problems and low and behold adding the entry to the config file for WCS fixed the issue, which tells me it was a dns problem (being resolved or not).

You are undoubtedly correct, however, i didn't respond on either thread till after sufficient time had passed that the DNS propagation delay that was undoubtedly at the root of it would no longer have been an issue, the point being that you had IN NO WAY done anything wrong, or harmful, merely that the need for that solution had passed, maybe my initial response was poorly worded, but the point really is anyone *now* experiencing a difficulty will have a different root cause for it, merely intended as information so helpers could more accureately target their efforts.

GhostShip · « **Reply #19 on:** June 09, 2008, 02:16:08 pm »

I had expected you to stop with this inane posting Bearded but it seems your words are more important than those of any one elses here.

Thank you for confirming you took no action for some days when you where aware there was an impending problem.

This is half the reason I was not wishing the community to rely on you, is this going to be how you continue to go on, ranting on about something trivial and yet refusing to understand that the fact is we where asked for help and gave it, you sat by and did nothing.