[GnomeMeeting-list] Connection attempt rejected without apparent reason

[Marcus Thiesen <marcus thiesen org>]

Hi list,

first of all, I'd like to thank the authors for this magnificent piece of 
work, I really like it.

The reason for me writing is that I've been trying to figure out a connection 
problem far too long by now, I'm running out of ideas, I've been loosing 
sleep and I really don't know what else to do. I'm sorry that I have to 
bother you, but it's .... a Netmeeting problem.

Ok, I started playing with Gnomemeeting a week ago, I'm not an expert but I 
believe me to be fairly competent. I already succeeded in establishing a 
couple of connections to other GnomeMeeting and Netmeetings, either 
configuring network equipment remotely myself or talking people through the 
process. I believe that I know what to do. This makes my current situation 
even more desperate. I have one location I can't call and I really don't know 
why. 

What is happening: I'm trying to call the remote side. The remote computer is 
behind a hardware router, thus the needed ports are forwarded using NAT. I've 
already seen this work on two sites, therefore I don't think this is the 
problem. I can access port 1720. I can't try the other way around, because I 
myself am behind a hardware router and have configured other ports because of 
somebody else in my network is using GnomeMeeting as well. Netmeeting does 
not support to call to non standard ports. As I was able to call two other 
Netmeeting clients, this as well can't be the problem. 
The main problem is that I more or less after I hit enter to call I get the 
message that the remote side did not accept the call. I know that the remote 
side wasn't even asked, but I'd really like to understand that. 

I created a debug log using -d 6 which can be found at this address 
http://www.thiesen.org/gnomemeeting/debug.out

I created an ethereal dump of the process which can be found here:
http://www.thiesen.org/gnomemeeting/dump

The log and dump actually contain two calling attempts, because I first 
believed that the first attempt was different from the second because it 
needed more time. As I'm experiencing long name resolution times at the 
moment this might be the cause for the delay, therefore I believe that the 
both processes are actually identical.

More detailed information:
I'm using Gnomemeeting 1.1.3 from Debian experimental.
The remote side is using Windows XP SP2 and the bundled netmeeting. The Router 
involved on the remote side is a Netgear RP614v2 using latest firmware. 

This is beside the router exactly the same configuration as two other working 
environments. 

I'd really love to get a deeper insight into this, because at the moment, I 
just don't understand what's going on.

Have fun,
 Marcus


-- 
        :: Marcus Thiesen :: marcus thiesen org :: www.thiesen.org ::        
           :: ICQ#108989768 :: 0x754675F2 :: thiesen jabber org ::        

It is absurd to divide people into good and bad. People are either charming or
tedious.
                                                                  Oscar Wilde