View Thread
Chaining simulations connection issue
Louis123 31/07/2022 at 14:27
Hi all, I am having some issues trying to chain Brighton and Lancing together, I have followed all the steps on the wiki with no luck at all, Brighton I have set up as port 50505 and Lancing as 50507, when trying to connect to Brighton it comes up in the client connections box that there is a connection.
After about 10 seconds that gets removed from the box and comes up saying that the server has disconnected me. I have tried everything I can with no success. Am I doing anything wrong here?
Cheers.
swiftaw 31/07/2022 at 15:54
According to the Chaining Diagram, Brighton and Lansing dont chain.
Thank you ReplyQuote ReportDionysusnu 31/07/2022 at 16:11
I'm not sure that's true - I recall having chained them before. The chaining diagram doesn't list Brighton in the map part because it's been superseded by Three Bridges.
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.
Thank you ReplyQuote ReportLouis123 31/07/2022 at 16:17
It's for everything mate, I tried chaining Kings Cross and Peterborough and it still comes up with the same message
Thank you ReplyQuote ReportLouis123 31/07/2022 at 16:19
Thanks mate I'll try that, so do I just enter 0.0.0.0 into the IP address then?
Thank you ReplyQuote ReportTrainman525 31/07/2022 at 16:23
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?
Thank you ReplyQuote ReportDionysusnu 31/07/2022 at 16:31
Thanks mate I'll try that, so do I just enter 0.0.0.0 into the IP address then?
Enter 0.0.0.0:50505 or whatever port you're hosting on. So it's the part before the : symbol that you replace.
Alternatively, you could also try localhost:50505 but I'm not sure SimSig accepts it.
Thank you ReplyQuote ReportDionysusnu 31/07/2022 at 16:31
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
Thank you
ReplyQuote Report
Louis123 31/07/2022 at 16:35
That didn't work, it instantly disconnected me as soon as I clicked connect
Thank you ReplyQuote ReportMarkC 31/07/2022 at 16:40
That didn't work, it instantly disconnected me as soon as I clicked connect
Try using 127.0.0.1 for the ip address
Thank you ReplyQuote ReportTempest Malice 31/07/2022 at 18:51
it comes up in the client connections box that there is a connection.After about 10 seconds that gets removed from the box
just to make sure, when the connection appears in the box, you are selecting it and then pressing the "accept" button?
Thank you ReplyQuote ReportLouis123 31/07/2022 at 19:37
Louis123 in post 147402 said:That didn't work, it instantly disconnected me as soon as I clicked connectTry 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
Thank you ReplyQuote ReportTrainman525 31/07/2022 at 19:38
Dionysusnu in post 147401 said:
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 think that proves it has been a long day! Too long for me clearly.
Thank you ReplyQuote Reportclive 31/07/2022 at 20:53
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.
Thank you ReplyQuote Reportclive 31/07/2022 at 20:55
The accept button is blanked out
I think that means that the server hasn't accepted the TCP/IP connection yet.
Thank you ReplyQuote ReportDionysusnu 31/07/2022 at 21:03
Dionysusnu in post 147396 said:Apologies for the wrong info. Not sure where I picked it up. I went and looked and 0.0.0.0 is in the list of past IPs I've tried to connect to in the loader. Maybe I got it swapped around with localhost (which then does work?) in my mind. Thank you ReplyQuote Report
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.
clive 31/07/2022 at 21:05
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.
Thank you ReplyQuote Reportheadshot119 31/07/2022 at 21:09
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?
Thank you ReplyQuote Reportheadshot119 31/07/2022 at 21:09
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.
Thank you ReplyQuote Reportclive 31/07/2022 at 21:10
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.
Stupid me: that's 127.0.0.1.
192.whatever that's assigned to your machine should be recognized by your network stack and not sent to the router.
Thank you ReplyQuote Reportclive 31/07/2022 at 21:10
headshot119 in post 147415 said:
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?
Yes, I did. I was typing my apology as you wrote that.
Thank you ReplyQuote ReportLouis123 31/07/2022 at 21:44
headshot119 in post 147416 said:
Louis123 in post 147406 said:The accept button is blanked outYou 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.
Yeah I clicked on it and only the remove button was available to press.
Thank you ReplyQuote ReportLouis123 31/07/2022 at 21:46
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.
Cheers mate I'll do that.
Thank you ReplyQuote Report