Ok, well that pretty much narrows it down. So we are fighting your IT admin.Blakey wrote:Trying "Winsock Tester" to simplify the tests a bit. It just allows you to listen and connect giving IP addresses and ports - it shows eactly what the problem is - but not how to fix it.
If I start XP listening on port 51234 then I can connect to it using Winsock from 7. In fact if I have XP listening on port 51234 and have no MT running at all on XP, and then I start MT on 7 I can try connecting to server on port 51234 (direct connect) and the winsock tester on XP sees the connection coming in from 7. So basically XP's 'server' is working.
If I start winsock listening on port 51234 on win7 then try connecting to it using winsock on XP, it never sees the connection. Basically win7's 'server' is being blocked by something. win7 firewall is off completly. Something else on my win7 box is blocking it.
To complete the set I tried 'listening' on ports 21, 23, 25, 80, 51234 and 54321. There seemed to be come phantom connections to ports 21 and 25
but none of the others worked at all. So all I need to do is figure out what is blocking all my ports. Perhaps it's McAfee. I wonder if I can find out...
As I've said before, when win7 is on my work network then this connection works fine. It's just at home that it's blocking.
The non-domain account that you log in locally with, does it have local admin rights? I assume it does not.