It may be that they are just blocking all inbound connections which probably means that you will not be able to use any port to get around it. Unless you can find out they have whitelisted some ports, it would take a little investigation to check that. If you have a buddy that knows Linux, they could burn you a live cd and go through some tcp tests to scan different ports and see if any are white listed during peak time.
On 1/5/07, schoie88 <[EMAIL PROTECTED]> wrote: > > --- In [email protected] <vassalengine%40yahoogroups.com>, > Joel Uckelman <[EMAIL PROTECTED]> > > wrote: > > > > Thus spake "schoie88": > > > A while ago I noticed I could connect to server but got no > feedback, > > > e.g. couldn't see anyone [including me] in rooms, even though the > > > server status showed them to be busy. My opponents could see me > in > > > there. Quite clearly the server couldn't 'upload' to me. Other > > > connections are fine. A few plyers on the VASL forum had the same > > > problem. > > > > > > After several tests I now realise this is because the ISP blocks > all > > > connection to P2P sites at peak times. The VASSAL server comes > back > > > when P"P software is unblocked. More and more ISP's are blocking > this > > > traffic at peak times. So more and more players will be kept out > of > > > VASSAL in the evenings. Is VASSAL server seen as P2P by the > ISP's? Can > > > this be altered? > > > > > > cheers > > > David > > > > If you're showing up for others on the server, then clearly you > have no > > problem getting packets through to the server. Your problem is > receiving > > packets coming back to you from the server. > > > > VASSAL uses port 5050, last I checked. Are you sure the problem is > that > > your ISP is blocking port 5050? (I'm dubious about this, since Yahoo > > Messenger also uses 5050; I have a hard time believing that they'd > block > > Yahoo Messenger.) Another explanation is that your firewall is > blocking > > those packets, but that's also weird since (I think) the incoming > packets > > from the VASSAL server should be interpreted by your firewall as > related > > to a connection you initiated, and so let in. > > > > Hmm. It might be worth calling your ISP about to get more > information. > > If it turns out that they are blocking 5050, what I would do, in > order > > of severity, is 1) ask them not to block that port, 2) point out > that > > it prevents you from getting what you pay for, 3) threaten to > switch to > > another ISP (even if you don't really mean it), and 4) switch to > another > > ISP and write them a letter explaining why. > > > > -- > > J. > > > Most helpful thanks. > > > [Non-text portions of this message have been removed]
