I am trying to test out a game with QuestNet on my own computer but I can’t get it to work. When I try to connect to “localhost” with port “10001” I get the error message:

Unable to connect to remote host

Does anybody have any ideas about what I am doing wrong?

did you load the same game in the Quest server, for connection with the quest client ?

make sure the port is right.

run QuestNet, load the game, and click run or whatever it is.

I too have the same issue.
Server:
The server (running) notes the player (myself) has connected.
The test file I used had one room, set as the start room, and it was marked as multiplayer.
The server was set to automatically register anyone who logged in.

The Client:
The client (running) produces a connection status window, stating it is connected to the server, but it never completes, and remains at this window.

My main concern is if this is normal behavior: You cannot connect with a client on the same machine running the server.

The Stalker wrote

My main concern is if this is normal behavior: You cannot connect with a client on the same machine running the server.

Not normal, I've successfully had Questnet server running and two instances of Quest running and connected to the server - all on the same old PC.

You must have a configuration error somewhere.

Al

After returning home from work, I went ahead and tried it again. This time I simply created a clean empty game setup for multiplayer with a start room, and I connected to it via client without a hitch. I'm not sure what I had done wrong originally. Regardless thank, you for your input.

Some firewall settings could be interrupting proper operation of the server/client.

Mman - did you start a game on your computer first, or did you just open Quest and try to connect?
Localhost is your own computer and so you need to start a Questnet Server first.

firewalls won't effect connecting locally, nor through a LAN (I don't think). I don't think port forwarding effects connecting through a lan either, however, you do need to know the local IP of the machine you're connecting to, if you're not running the client on the same machine as the server. Goto Start - Run - type in cmd, and press enter. then type ipconfig

your local IP (starting with 192.168) should appear.

A local IP can be anything.
Like 10.10.10.*, or 10.0.0.*, or 45.24.65.*.

And if you're not connected I don't think Windows gives your machine an IP - other than the loop-back of 127.0.0.1 and 0.0.0.0... Which you can't even see using ipconfig, you need to use netstat (-a -n).

And yes, firewalls DO effect LAN's. Especially Norton's when it is having a funny day.

Port forwarding CAN have an effect through the LAN, but only if it's through a few routers or gateways or servers etc.

And nowaday's firewalls are program specific, meaning they stop network communication at the program-level too... Ever notice those "xxxx.exe want's to connect to the internet" pop-ups when using norton/that other major firewall program (again, I have clients who just click "no" and then wonder why they can't get through to the net with certain programs).
I'm not sure if they can stop connections to 127.0.0.1, I've never tried it. And I can't try it as I have no firewall software.