Getting disconnected from server

Hi, When I try to connect to a server which already has users, I always get disconnected after a few (5-10) seconds, even if there is only one user there. However, if I connect to a server which doesn't have any other users, and then other users join in, then I do not get disconnected. I had a successful session with 4 other users. So why do I get disconnected when joining a non-empty server?

Sounds like your IP connection can't keep up with the amount of data being received.

Yes, but why does it only happen when I join an existing session, and not when others join my own session. Also, I'm not sure if it makes any difference, but immediately unchecking all the users' "Receive" check box upon connection doesn't help (does it stop the server from sending me the user's data?) Besides, it says: "The NINJAM client requires a fair amount of CPU power, a moderate amount of inbound bandwidth (192kbps for a typical 4 person jam, 512kbps for an 8 person jam) and less outbound bandwidth (100kbps typical)." I have a 5 mbps connection. According to the above, there shouldn't be any problem (and I'm talking about a 3 person session).

Are you on wired or wireless to your internet connection?

Thanks for your reply. Unfortunately, it didn't help. I tried a few combinations in the audio settings (including WaveOut), but to no avail. Any other ideas? Even if I uncheck the "transmit" check box, I get disconnected. This is really strange... Is there a log or anyway to know what the cause is? I'm running NINJAM after closing most applications, so that it can use as much available bandwidth & memory as possible. However, the anti-virus (AVG) is still running. Should this pose a problem? Are there any known applications which may cause NINJAM problems? By the way, I wonder why the number of participants in a jam affects the upload bandwidth demand, since in any case I'm only uploading my own recording. What am I missing here?

OK, how about a traceroute (tracert on windows)? (It starts failing around 204.11.106.90 for me, but that's close to test.ninjam.com [204.11.104.240] anyway). I get ~174ms.

I get 250 ms for 204.11.106.90. Is that not good enough to use the server?

Hmm. Not sure, really... It doesn't sound too bad: I know people from Oz and Japan use test.ninjam.com, and I'd expect them to have higher network latencies than that. More random thoughts: How much (free) RAM have you got? It might be that you can't allocate enough in one big chunk when joining a full-ish server whereas you can allocate it bit by bit... (I'm clutching at straws now...)

I don't think that's the issue. I have 2 GB of RAM, and I closed every program before using NINJAM. :-\ Edit: Do you think debugging the client application will give me any more information?

That is a pretty high Latency, but then your not transmitting and still have the prob. When it counts the first interval does the line increase correctly? Also I'll throw out some other possible issues, do you share your internet? If so does the router have QOS, does it make a difference with this on or off? Are you connected wireless to your internet? Do some speed tests online, try some here, you can select different locations, but also google speedtest and try some others, see what you max up and down is. If your on Wireless aim the antenna's on pc and router towards each other. Turn off firewalls and test (don't forget to turn them back on). Don't setup routes in the router firewall for NINJAM when using as client only. Try possibly putting your computer temporarily on a DMZ with in your router if you are going through one. But this leaves you bare on the net and I only recommend trying for test purpose, if it turns out it's ok on a DMZ it helps point to where the problem lies then how and what to fix. Take yourself off the DMZ once tested. If all this isn't working then I can always do a remote session with you using teamviewer, this doesn't need installing, meaning you stop the software and it no longer can be networked with. If ya need to get hold of me a bit quicker then try