Running Win7, lower end of the high spectrum.
Have opened my 5050 port, in and out, for Vassal. Disabled all firewals, including windows firewall. Tried Telnetting as follows:
o game.vassalengine.org 5050 and no connection established.
Pls halp
Thus spake Smackface via messages:
Running Win7, lower end of the high spectrum.
Have opened my 5050 port, in and out, for Vassal. Disabled all firewals,
including windows firewall. Tried Telnetting as follows:o game.vassalengine.org 5050 and no connection established.
Pls halp
Is your ISP blocking you? I can confirm that telnetting to the game
server works for me.
–
J.
Shouldn’t be the ISP, I’m using the same one I’ve used for years. For context, this only started happening after I did a fresh install of Win7 on my PC.
It’s not the ISP. This only started happening after I did a fresh install of Win7
Here’s my error log
2016-02-01 14:39:10,873 [1-AWT-EventQueue-0] WARN VASSAL.tools.logging.LoggedOutputStream - at java.awt.EventDispatchThread.run(Unknown Source)
2016-02-01 14:39:10,873 [1-AWT-EventQueue-0] WARN VASSAL.tools.logging.LoggedOutputStream -
2016-02-01 14:39:10,873 [1-AWT-EventQueue-0] ERROR VASSAL.chat.jabber.JabberClientFactory -
2016-02-01 14:39:46,859 [1-AWT-EventQueue-0] ERROR VASSAL.chat.node.NodeClientFactory -
Thus spake Smackface via messages:
Shouldn’t be the ISP, I’m using the same one I’ve used for years. For
context, this only started happening after I did a fresh install of Win7
on my PC.
It sounds like you have a firewall (possibly on your machine?) between
you and our server which is blocking you. If you can’t telnet to the
game server, then the problem is definitely not the VASSAL program.
–
J.
I disabled all the firewalls, still nothing. For reference, Vassal worked beautifully on Windows Vista for months, never any problems.
Thus spake Smackface via messages:
I disabled all the firewalls, still nothing. For reference, Vassal
worked beautifully on Windows Vista for months, never any problems.
If you can’t telnet to our game server, then you’re having a
connectivity problem, not a problem with VASSAL. Try running traceroute
to our game server to see where you’re being blocked.
–
J.
Took me 15 minutes to type this up by hand. Whoever thought Ctrl+C, Ctrl+V shouldn’t work with cmd is mean.
tracert game.vassal.org
1 2ms 9ms 2ms Cisco01368 (192.168.1.1)
2 * * * Request Timed Out
3 23ms 14ms 16ms 173-219-228-177.suddenlink.net (173-219-228-177)
4 93ms 18ms 24ms 173-219-253-248.suddenlink.net (713.219.253.248)
5 41ms 39ms 38ms 173-219-253-234.suddenlink.net (713.219.253.234)
6 25ms 24ms 21ms 66-76-31-130.suddenlink.net (66.76.31.130)
7 29ms 47ms 28ms chi-b21-link.telia.net (62.115.40.61)
8 25ms 24ms 33ms ash-bb4-link.telia.net (213.115.130.58)
9 106ms 99ms 102ms prs-bb2-link.telia.net (80.91.254.215)
10 125ms 127ms 119ms psr-b8-link.telia.net (62.115.138.139)
11 114ms 117ms 173ms online-ic-315748-prs-b8.c.telia.net (62.115.63.94)
12 113ms 112ms 114ms bb1-bb2-he0-0-0-7.dc3.poneytelecom.eu (195.154.1.250)
13 111ms 119ms 107ms 45x-s31-1-a9k1.dc3.poneytelecom.eu (195.154.1.33)
14 112ms 108ms 111ms one.vassalengine.org (62.210.178.7)
Trace Complete
I can’t answer the initial question but hope this will help you with cmd in the future.
Right mouse click - Select All - Enter
The contents of your cmd screen are now on clip board. Paste as usual.
Thus spake Smackface via messages:
Took me 15 minutes to type this up by hand. Whoever thought Ctrl+C,
Ctrl+V shouldn’t work with cmd is mean.tracert game.vassal.org
1 2ms 9ms 2ms Cisco01368 (192.168.1.1)
2 * * * Request Timed Out
3 23ms 14ms 16ms 173-219-228-177.suddenlink.net
(173-219-228-177)
4 93ms 18ms 24ms 173-219-253-248.suddenlink.net
(713.219.253.248)
5 41ms 39ms 38ms 173-219-253-234.suddenlink.net
(713.219.253.234)
6 25ms 24ms 21ms 66-76-31-130.suddenlink.net (66.76.31.130)
7 29ms 47ms 28ms chi-b21-link.telia.net (62.115.40.61)
8 25ms 24ms 33ms ash-bb4-link.telia.net (213.115.130.58)
9 106ms 99ms 102ms prs-bb2-link.telia.net (80.91.254.215)
10 125ms 127ms 119ms psr-b8-link.telia.net (62.115.138.139)
11 114ms 117ms 173ms online-ic-315748-prs-b8.c.telia.net
(62.115.63.94)
12 113ms 112ms 114ms bb1-bb2-he0-0-0-7.dc3.poneytelecom.eu
(195.154.1.250)
13 111ms 119ms 107ms 45x-s31-1-a9k1.dc3.poneytelecom.eu
(195.154.1.33)
14 112ms 108ms 111ms one.vassalengine.org (62.210.178.7)Trace Complete
So, your pings go through, which shows that you have basic connectivity.
But pings use ICMP, not TCP like connections to our server do. My route
to the server from prs-bb2-link.telia.net onward is the same as yours,
so it’s not likely to be any of those hosts which are blocking you. It’s
also not likely to be the other telia hosts; telia is a backbone
provider.
This leaves suddenlink (your ISP?), your router(s), and your machine
itself as the culprits. What I would do next is start trying to isolate
these.
Can you telnet to game.vassal.org from another machine on your LAN?
If so, then that eliminates your router and suddenlink. If not, then
at least one of your router and suddenlink is the problem.
–
J.
As I said I haven’t had issues with the exact same ISP in the exact same location for vassal, this only happened after I did a fresh install of Windows 7 from Windows Vista. I’ve also used the same two routers for vassal in past years that I am now, so those aren’t the problem. I will telnet from another machine just to triple check, after that I may just have to reinstall vista, and download everything again ;(
Thus spake Smackface via messages:
As I said I haven’t had issues with the exact same ISP in the exact same
location for vassal, this only happened after I did a fresh install of
Windows 7 from Windows Vista. I’ve also used the same two routers for
vassal in past years that I am now, so those aren’t the problem. I will
telnet from another machine just to triple check, after that I may just
have to reinstall vista, and download everything again ;(
In that case, the likely problem is a firewall on your machine. Check
if Windows Firewall is on, or if you have some other firewall installed.
If this happened as a result of installing Vista and you did nothing
additional to turn on a firewall, that suggests that blocking is the
default and you’ll get this once again by doing a reinstall.
–
J.
Like I said, I disabled windows firewall, and I disabled my other firewall. BTW it was a switch from Vista to Win 7, I have had Comodo firewall in the past which has been known to cause issues with other programs. The only thing I can think of is that Zonealarm doesn’t like Vassal
Update, just opened everything I could think of, disabled all my firewalls, closed all backgroud programs, and basically left myself open for anyone who wanted to hack me, and still no connect
New, and probably final update. I opened port 23 going both inbound, and outbound, for a short period of time. Tried telnetting to game.vassal.org again, as this was the problem on other machines, they couldn’t connect through port 23, all with windows 7. Anyways, the telnet failed with port 23 open inbound and out, and it appears windows 7 just simply isn’t compatible with vassal for some reason. Unfortunately I can not revert to Vista, as the switch to 7 was prompted by drivers for my hardware being incompatible with Vista, or simply not existing. I will check periodically over the next year or so, hoping you guys can maybe switch vassal to using a different port or something. I will say I thoroughly enjoyed the program and will recommend it to anyone that can get it to work.
Thus spake Smackface via messages:
New, and probably final update. I opened port 23 going both inbound, and
outbound, for a short period of time. Tried telnetting to
game.vassal.org again, as this was the problem on other machines, they
couldn’t connect through port 23, all with windows 7. Anyways, the
telnet failed with port 23 open inbound and out, and it appears windows
7 just simply isn’t compatible with vassal for some reason.
Unfortunately I can not revert to Vista, as the switch to 7 was prompted
by drivers for my hardware being incompatible with Vista, or simply not
existing. I will check periodically over the next year or so, hoping you
guys can maybe switch vassal to using a different port or something. I
will say I thoroughly enjoyed the program and will recommend it to
anyone that can get it to work.
What you demonstrated above with telnet is that you don’t have TCP
connectivity to our game server, not that VASSAL isn’t compatible with
Windows 7.
I’m pretty sure we have loads of users who have run VASSAL on Windows 7.
Rather than giving up, I suggest finding somebody who is more familiar
with Windows than I am to help you.
–
J.
I can attest to the fact that Vassal runs on Windows 7.
I have been writing Vassal modules on a Windows 7 Home Premium machine for the past 5 years 
Brian
Wait, wait. I misread. Tenletting to port 23 on our machine is guaranteed to timeout.That’s because we don’t have have port 23 open, and nothing running on port 23 to begin with. To test for connectivity to the game server, you need to telnet to the port that the game server runs on, which is 5050.
Could not open connection to host on port 5050 it says.
I have confirmed that P2P over port 5050 is good however, using Hamachi