Chaining simulations connection issue

Thanks mate I'll try that, so do I just enter 0.0.0.0 into the IP address then?

Brighton and Three Bridges BOTH chain to Lancing, and still do. I believe this is because Three Bridges was built out from Lancing so have the same fringe at Hove?

That didn't work, it instantly disconnected me as soon as I clicked connect

it comes up in the client connections box that there is a connection.

After about 10 seconds that gets removed from the box

Louis123 in post 147402 said:

That didn't work, it instantly disconnected me as soon as I clicked connect

Try using 127.0.0.1 for the ip address

Trainman525 in post 147399 said:

Brighton and Three Bridges BOTH chain to Lancing, and still do. I believe this is because Three Bridges was built out from Lancing so have the same fringe at Hove?

I'm assuming you mean built out of Brighton ;)

I believe you can use 0.0.0.0 instead of the 192.<etc> address as well to connect to your own host. That should be direct, instead of going through your router and being sent back to yourself, which can sometimes cause issues.

The accept button is blanked out

Dionysusnu in post 147396 said:

I believe you can use 0.0.0.0 instead of the 192.<etc> address as well to connect to your own host. That should be direct, instead of going through your router and being sent back to yourself, which can sometimes cause issues.

192.0.0.1 should be recognized by your own device's network card or network stack and turned around without ever leaving the machine.

0.0.0.0 is an unrouteable address; it doesn't come back to you. It's used for things like "accept any address" or "use all interfaces" on a server and "I don't have an address" in give-me-an-address protocols like DHCP. It DOES NOT mean "this machine". Most likely it will be sent to the default gateway which will then throw it away.

MarkC in post 147403 said:

Try using 127.0.0.1 for the ip address

No that doesn't work as it instantly disconnects me with no attempt of even connecting

Dionysusnu in post 147396 said:

I believe you can use 0.0.0.0 instead of the 192.<etc> address as well to connect to your own host. That should be direct, instead of going through your router and being sent back to yourself, which can sometimes cause issues.

192.0.0.1 should be recognized by your own device's network card or network stack and turned around without ever leaving the machine.

0.0.0.0 is an unrouteable address; it doesn't come back to you. It's used for things like "accept any address" or "use all interfaces" on a server and "I don't have an address" in give-me-an-address protocols like DHCP. It DOES NOT mean "this machine". Most likely it will be sent to the default gateway which will then throw it away.

The accept button is blanked out

Dionysusnu in post 147396 said:

I believe you can use 0.0.0.0 instead of the 192.<etc> address as well to connect to your own host. That should be direct, instead of going through your router and being sent back to yourself, which can sometimes cause issues.

192.0.0.1 should be recognized by your own device's network card or network stack and turned around without ever leaving the machine.

clive in post 147410 said:

Dionysusnu in post 147396 said:

I believe you can use 0.0.0.0 instead of the 192.<etc> address as well to connect to your own host. That should be direct, instead of going through your router and being sent back to yourself, which can sometimes cause issues.

192.0.0.1 should be recognized by your own device's network card or network stack and turned around without ever leaving the machine.

0.0.0.0 is an unrouteable address; it doesn't come back to you. It's used for things like "accept any address" or "use all interfaces" on a server and "I don't have an address" in give-me-an-address protocols like DHCP. It DOES NOT mean "this machine". Most likely it will be sent to the default gateway which will then throw it away.

Did you mean 127.0.0.1 here Clive?

Louis123 in post 147406 said:

The accept button is blanked out

You need to click on the incoming connection so it's highlighted in blue, for the Accept and Reject buttons to become "live".

But I agree with Clive it sounds like your firewall is blocking SimSig.

Louis123 in post 147407 said:

MarkC in post 147403 said:

Try using 127.0.0.1 for the ip address

No that doesn't work as it instantly disconnects me with no attempt of even connecting

That strongly suggests that you've got a firewall running on your machine (Windows Defender?) which is blocking the relevant port.

If you open a command box (type cmd in the Windows search box) and then enter "ping 127.0.0.1", that will tell you if your networking loopback is working or not. If so, run the command "netstat -na" and look for "TCP 0.0.0.0:50505 0.0.0.0:0 LISTENING"; this shows that the server is listening.