If you're planning on making a server usable from a LAN/WAN configuration, everything needs to visible on the LAN/WAN address of the server computer - with the exception of
database addresses (those can/should be localhost.)
(Use WAN address if not behind a firewall/NAT device - not recommended. Otherwise use LAN address and port-forwarding.)
You're login.ini file looks correct for listening network..but, <loginserver2>'s address doesn't match that subnet.
As well, the "tcp" address is also set to 'localhost.'
A router can forward ports internally. But, there really is no way to do that safely from a computer's LAN card to its internal localhost mapping.
__________________
Uleat of Bertoxxulous
Compilin' Dirty
|
Threaded Mode
