I have a strange setup going on here, but here goes:

I have worldgroup 3.20, and TWGS 1.11.55. Everything works fine when I run it on my Win98 machine. Using Rlogin port 513 and the local loopback ip 127.0.0.1 from WorldGroup set up like a normal module.
Port 513 is the only port WorldGroup will Rlogin to.

The problem started when I tried to move it to a new box running WinXP, worldgroup and everything else works fine, TWGS even works. But when I try to access TWGS from the BBS with the Rlogin client as normal, it gets stuck at the "connecting to 127.0.0.1...." prompt and eventually gets kicked back, saying it expected an Rlogin.

I have 3 computers hooked up with a router. The one where it worked fine is the "gateway" one, and now it won't work. I've tried Rlogging in to the BBS's IP on port 513, but it's no good either. (Yes, I changed TWGS's IP to it, too)

The way I got around this was to leave TWGS on the original comp, and just rlogin from the BBS box to that computer's internal IP. It works fine, although defeats the purpose.

I don't want to run it like this either, I want everything to be on one computer, the one running WinXP which I built exclusively for the BBS&TWGS. If anyone has any ideas, please hook a guy up. Thanks!
-FireControl

I had a similar problem on a setup I was trying before... Here's what I ended up doing on that box (before I tore it all down )

I set my DMZ to filter everything out except for a single access port (let's say port 1001). The people telnet in via port 1000, hits the external firewall, is NAT'd down to port 23, and then directed to the BBS machine elsewhere in the DMZ.

The BBS software would then access TWGS (located on the same machine) by it's actual IP address and TW port, not by the internal loopback (192.168.0.252:2002 for example) As stupid as it sounds, I was never able to get the stupid thing to work using the internal loopback, and I couldn't ever figure out why.

Actually, all three of my machines in my DMZ have two network addresses: an "external", and an "internal". In my scenario above, the external firewall would NAT and redirect to the "external" address, but the BBS -> TWGS would loop around via the "internal" address. Not sure if that mattered; that may have been part of my problem with the loopback.

Anyway, give that a shot and let me know if it worked.

Hey Red,
Thanks for the reply.

I have no problems with my internal IPs... (or external IP for that matter), it's just my local loopback (127.0.0.1), the "local" IP, which is usually the same for every computer. And it worked fine when I had it set up on my other (win98) box.

I'll give it a shot, I think what you meant was to try using the internal IP of the BBS box I want to use, right? I've tried that allready actually, but I'll play around with it some more. Thanks again!
-FireControl

Hey guy, just checking to see if you had any better luck with your setup...

No, no luck yet...
If I try to set TWGS to the comp's internal IP, and load it up first, then WorldGRroup won't initialize the Rlogin module, since TWGS is allready using it, and if I load WG first, TWGS can't initialize the player listener, cause WG is allready using it... sigh.
It's supposed to work fine with 127.0.0.1, and it did, I just wonder if there's something in WindowsXP that I have to configure for the local loopback to work? Thanks for the help tho!
-FireControl

Wow, that is wierd. Nothing in XP that I know of, but I didn't set mine up on XP so... Had it running under NT 4.0 Server (got LOTS of legal licenses for that one, hehe) and it all worked as-expected. Wierd...

Guess I can do some digging for ya, but I don't even know where to look