- This topic has 6 replies, 4 voices, and was last updated 18 years, 11 months ago by
.
-
Posts
-
I was just wondering how could I make the yahoo messenger, lets say the latest version, to connect to a certain server, not letting it auto-chose a server, e.g. scsd.msg.yahoo.com:5050 and a certain port.
I’ve tried working around the registry settings HKEY_CURRENT_USERSoftwareYahoopager but no result. It seems to get the server settings from another server, some kind of prelogin process.
Some intresting Values here: Host Name, Port, PreLogin, Relay Server…
So I thought there might be some professional help around here… Ideas/Solutions?
This is an easy one. To set the port simply change the current port number (dword value default is 5050) to another valid one such as -> 20, 23, 25, 80 or 119.
To set your own server there’s a couple ways to do it but the easiest is to create a string called “connserver” with a valid server’s IP address or hostname as the value.
But if I want it to connect on localhost on a firewall port? I’ve tried, but nothing… it simply refuses (maybe localhost is not a valid server, I think…)
As you experienced yes Yahoo! Messenger isn’t a big fan of connecting to local loopback (127.0.0.1). 😀 This can be accomplished by programmatic methods (which I won’t get into) and also accomplished by a few Windows NT-based network administration (machine policy) tricks which I haven’t tried the latter but I’m sure it’d work out.
Out of boredom I used the windows HOSTS file to attempt to redirect Yahoo! Messenger to the loopback address and it was a no go. I even attempted to redirect ALL of the Yahoo! chat “socket servers” (scsa.msg.yahoo.com – scsf.msg.yahoo.com) and those too didn’t work out. I played with connserver and the hostname string values inside the registry and while there might be a trick I overlooked I don’t see you being able to do it.
Now… this doesn’t mean you couldn’t go about it a different way. Besides the programming you could set connserver equal to another machine’s IP address on your network such as a local internal IP since Messenger won’t let you use your own here either. Messenger might allow you to use your WAN ip address (non-internal registered address) to connect to yourself and relay the connection or you might try connecting to another box on your network having the packets relayed through it (ie. 10.0.0.2 as the other box might be addressed). You could also simply just use the proxy support that Messenger already provides (Socks and HTTP) to accomplish this feat or even a third party “proxifying” tool to forcefully redirect the connection to 127.0.0.1, programs such as SocksCap, FreeCap and TorCap which will redirect ANY winsock-based connection to anywhere you want it to go (these programs are free). The tools I mentioned rely on API hooking of winsock so if you programmed yourself this would be an easy task where you wouldn’t need them. Writing your own driver (TDI/NDIS) or your own user-mode Layered Service Provider (LSP) would be an option too (if you have a lot of programming experience).
- You must be logged in to reply to this topic.