Watching matches in the tournament at Grahama

[jdart]

TLCV has so many bugs I think it is almost unusable. The worst one is that it doesn't keep track correctly of which side is playing Black and which White. Too bad because it is a nice looking interface with good functionality.

--Jon

[bob]

You don't have to do anything special to make connections over the internet. That's a basic function of your firewall.

But unfortunately TLCV wants to do more than making connections. In needs a TCLS running on a machine outside your LAN to make connections to you.

It's not doing anything differently than you are browsing this forum.

Browsing on port 80 is far different than connecting to a remote machine and then having that remote machine try to create a NEW connection back to you. IF you are using a typical router with NAT, the IP address machines outside your LAN see is the IP address of your router. How does data get to you? Router finagles the port numbers so that when a remote machine sends data to port X, it knows to forward that to port Y on your local LAN. But if an outside host tries to connect to your router with a new connection, your router won't know what to do with the packets. Most common solution is "port forwarding" where you tell your router "If ANY connections come to port XYZ, then forward them directly to port XYZ on this specific host machine. Then it will work.

[Dan Cooper]

You don't have to do anything special to make connections over the internet. That's a basic function of your firewall.

But unfortunately TLCV wants to do more than making connections. In needs a TCLS running on a machine outside your LAN to make connections to you.

It's not doing anything differently than you are browsing this forum.

Browsing on port 80 is far different than connecting to a remote machine and then having that remote machine try to create a NEW connection back to you.

I've done packet captures of the protocol TCLV uses. This is not how it works. It does not attempt a new connection back to the client, like FTP does (which is why passive FTP was invented).

TLCV clients sends a UDP packet to the server using the same source port as the server. The server responds back on that port. The client periodically sends keepalives to the server to keep the firewall's state table from expiring.

But the important thing is, just like most things you do on the internet, the server responds to client requests from the source port of the client, which doesn't require any extra configuration on the client end.

What you're describing is what needs to be done server side to allow clients to view your games. This thread is about OP's issues connecting to Graham's games.

Well, obviously you have never tried to use TLCV, and obviously you haven't the slightest idea how it works.

Obviously.

[Graham Banks]

TLCV has so many bugs I think it is almost unusable. The worst one is that it doesn't keep track correctly of which side is playing Black and which White. Too bad because it is a nice looking interface with good functionality.

--Jon

Really? I've never noticed this problem.

[cdani]

TLCV has so many bugs I think it is almost unusable. The worst one is that it doesn't keep track correctly of which side is playing Black and which White. Too bad because it is a nice looking interface with good functionality.

--Jon

For Graham it works very well. It depends on how well adapted is to the GUI you are using.

[hgm]

Well, obviously you have never tried to use TLCV, and obviously you haven't the slightest idea how it works.

Obviously.

Indeed. Because the first thing anyone who tries to use TLCV on an external broadcast will experience, is that you cannot connect unless you set up the port translation for UDP in all intervening connection equipment. Without that, other people watching the broadcast will see you try, but you will only get the popup shown by the OP, and never any moves or chat. It just doesn't work, as everyone can easily conclude for himself by trying to connect to Graham's broadcasts (as the OP confirms).

[Graham Banks]

Well, obviously you have never tried to use TLCV, and obviously you haven't the slightest idea how it works.

Obviously.

Indeed. Because the first thing anyone who tries to use TLCV on an external broadcast will experience, is that you cannot connect unless you set up the port translation for UDP in all intervening connection equipment. Without that, other people watching the broadcast will see you try, but you will only get the popup shown by the OP, and never any moves or chat. It just doesn't work, as everyone can easily conclude for himself by trying to connect to Graham's broadcasts (as the OP confirms).

Dan has run several broadcasts through TLCV successfully.

[hgm]

Running a broadcast is not the same as trying to connect to one. TLCV just doesn't connect if you do not map ports first. If he denies that he is wrong, and it is your choice of whether he is intentionally lying or just ignorant...

[Krzysztof Grzelak]

I have a request to H.G.Muller,Graham Banks,daniel jose,Dan Cooper,Robert Hyatt, Jon Dart. Please install program TLCV and try to connect.

Host- chess.zapto.org
Port- 16001.

If someone manages to combine this please write.

[hgm]

Yes, that works. I see Deep Smash playing against Big Lion.