i've just started using nwniab and it looks like a pretty nifty gizmo. so far, it seems that everything runs just fine, even to the point of loading a small test module i set up, but for some reason i can't connect to the server using my normal nwn pc client, running from the same machine [actual, non-virtual pc machine, that is].
ifconfig on the virtual box shows me the address of eth1 is 192.168.56.101.
netstat -ap shows me that nwserver is listening on udp port 5121.
from windows, if i do ipconfig/all, i see the virtual box as 'Ethernet adapter VirtualBox', w/an address of 192.168.56.1 [NOTE : .1, *NOT* .101...]
when i try to direct connect with nwmain.exe +connect 192.168.56.101:5121 i get errors saying either the address can't be mapped or the server has timed out. the same thing happens when i try 192.168.56.1:5121.
when i use the network browser window from my nwn client [i.e., nwmain.exe, multiplayer => join lan game], i do see the module up on the selection screen, but bizarrely, everything in the module info is wrong. the level range is 255->255, the connect address is 192.168.1.2:3099, allow local chars = checked, etc. -- even though i've set all of these differently on the command line for nwserver within nwniab. and when i do try to connect to it this way, i get a 'server not responding' error.
i've added both program and address+port exceptions to my windows firewall for each of these sets of ip+port, no joy, and i'm fresh out of ideas.
does anyone have any ideas on how i could troubleshoot this ?
i'm running the box on a windows xp system. [full specs - windows xp professional sp3, x32].
when i fire up the virtual box, i get a window that's automatically logged me in as the user 'nwn'. i then run a script that's supplied w/nwniab called [iirc] 'nwnstart'. there are no errors in any of the log files, and everything on the nwn server seems to be running fine, at least from within the vb. i then launch nwmain.exe from my windows start menu, on the same machine. it's at this point that i can't connect.