Post by Werehound Silverfang on Jul 10, 2010 7:45:53 GMT
I have HGLL along with SIMTools set up within the server (onenter, onexit, onload, x2_def_activate, levelup, onchat is empty, etc) and the nwnx.ini points to fky_chat a dn fky_chat_srv.
When loaded with NWNx (outside of NWNIAB), HGLL works, but trying to send a tell crashes thee server (usual behavior for me at this point, so I haven't been using SIMTools), However, when using NWNIAB, it tells me LETO is registered and CHAT is registered, but HGLL wont work (player gets booted, no changes made), but tells don't crash the server (however, absolutely no chat is logged regardless of my settings). Are Leto and nwnxchat setup to work with NWNIAB. Also, how do I access the NWNeXalt tools and commands. =)
A lot I know, but I'm eager to use the full extent of this nice tool.
(There are three commands above, each on their own line, in case your browser line-wraps them, as mine seems to do on my laptop)
You'll need to do that with the VM shut down. If you're running Windows Firewall, you'll likely get an Unblock request when starting up the VM again (at least, I did on XP and Server 2003).
I did just test this and it worked - I forwarded UDP port 5121 on my router to my PC, then used the internal VirtualBox NAT forwarding to forward port 5121 on my PC into the VM proper, using the above three commands entered at the DOS prompt.
So... ipconfig from the DOS prompt on my computer tells me my local IP is 192.168.1.101...
Running the server I can only see it in the LAN network, and it tells me my IP is 192.168.1.109.
The VM tells me the IP is 192.168.1.103
Forwardign ports to 192.168.1.109 made the server appear on the list.
;D ;D ;D
I presume then that you switched to Bridged instead of using the VirtualBox NAT forwarding trick from above?
Make sure you are only forwarding UDP port 5121 if that's the case - don't forward everything, because the VM has no real security by default (for example, the root and mysql passwords are published). Only forwarding the NWN port means people can't access the secure services from outside your LAN (and using VirtualBox NAT port forwarding means the 'LAN' is limited to being on your PC only).