ForumsHQ

Running WG 3.3, and i Rlogin to the TradeWars Game Server which resides on the same machine, works perfectly, dont know if that will still be true, cause i'm reinstalling everything from scratch onto a dedicated machine, gonna not use a door server for awhile until i get a 3rd machine to act a door host. But under XP, WG3.3 and TW2002 GS, it all works fine, no problems..also, the only problem i had with Rlogin was connecting to the syncronet door server, and it was just that everyone logged in as sysop instead of using thier own accounts, but i got clerification on that. But once i put the local ip (192.168.1.100) in the command line when configing the rlogin module for TWGS, had NO problems...but something i did learn my years of using Windows OS's, and particularly xp, is even if the hardware is identicle, every install setups up a little different each time, i dont know why, but i've even seen xp give different install options when even re-installing on the same machine, the only time its been exact, was when i did a Compaq Workstation roll out and used a Ghost cd set from a master machine, did everything install exactly the same.

Interesting! That's very good to hear. I'm thinking the solution may have been one of two things:



- WorldGroup version. Many WG sysops are running 3.2, so it's possible the authors actually fixed the rlogin-to-localhost/loopback bug in 3.3.



- Use of a LAN ip. Most sysops who had the rlogin problem presumably used for the outbound rlogin module an IP of either 127.0.0.1, or the actual static IP (WAN IP that is, not LAN IP) of their BBS. Perhaps WG specifically checks for those two IPs and blocks an rlogin attempt to them, but maybe if you use your LAN IP it doesn't check that?



The latter makes a good experiment -- on your system, if you switch the IP of worldgroup's outbound rlogin module (ie, the connection to TWGS) to either 127.0.0.1 or your static bbs IP, does it stop working?



Again, VERY curious to see the results. Many, many WorldGroup sysops have been unable to set up door servers on their local machine because WG outbound rlogin won't let them connect to another server on the same machine. As a result, most WG sysops don't run door servers because it requires a second computer. If this can be avoided, I could see it greatly increasing the number of sysops running door servers (as well as running TWGS, which is far cheaper and less buggy than WG Twars)

you still around PuFF? very curious as to the above...