IVC server issue help
-
My issue is as follows:
When I connect to others who host I uave no problem using F1/2 in the UI and UHF/ VHF in 3D.
When I host everybody can use both F 1/2 and UHF/ VHF but I can not hear or be heard either on F2 or on VHF.
All definitions regarding the F key are good, as well as the U/ V channels.
It seems like there’s an issue with my server settings that for some reason block me from VHF/ F2 while all the others can use it.Help shall be appreciated.
-
Going to bet you have your own IP installed into the IVC block when you connect to yourself instead of the feedback loop IP of 127.0.0.1.
-
Going to bet you have your own IP installed into the IVC block when you connect to yourself instead of the feedback loop IP of 127.0.0.1.
“IVC block”?
You mean in the Comm box IVC section?What’s interesting is I changed nothing in my setup or definitions other then change router and provider (all ports are open).
I also always dialed in my active IP in the IVC section in the comm box and it always worked. -
What’s interesting is I changed nothing in my setup or definitions other then change router and provider (all ports are open).
That would have been useful information to have put in your original post. Something has most definitely changed; check again that UDP ports 9987 to 9989 are being forwarded to your flight PC’s internal IP address. Check that internal IP address isn’t changing and reserve it so it doesn’t change, if you haven’t already.
I also always dialed in my active IP in the IVC section in the comm box and it always worked.
Please read the BMS-Manual page 89 for explanation of what should be entered in the COMMS window (aka Phonebook) if you are hosting.
-
Check that internal IP address isn’t changing and reserve it so it doesn’t change, if you haven’t already.
All is understood but the quoted paragraph above…How do you check if it changes and how do you reserve it?
-
I also always dialed in my active IP in the IVC section in the comm box and it always worked.
This is the bit your getting wrong, reread that chapter again as “All is not understood”
-
You will need to read the documentation for your router. It might be called DHCP Reservation in your router settings.
Basically your router will assign internal IP addresses to the devices connected to it, e.g.: 192.168.0.2 onwards. If your flight PC is 192.168.0.10 and all your ports are forwarded to that address you will be fine. If the router changes your flight PC to 192.168.0.13 the next day though and all your ports are still being forwarded to 192.168.0.10 though it will obviously not work.
This might not be the problem, but as you have given us very little information to go on we’re just suggesting things to check at this point.
-
“IVC block”?
You mean in the Comm box IVC section?Yes that is exactly what I mean.
What’s interesting is I changed nothing in my setup or definitions other then change router and provider (all ports are open).
I also always dialed in my active IP in the IVC section in the comm box and it always worked.Entering the feedback loop IP address always works too. As the guys above tried to point out your active IP (real IP address) is good for the router but it produces it’s own IP addresses for the actual computers themselves and if you do not set that up as static that can change when multiple devices requiring IP addresses are connected and the order in which they connect. That IP changing will completely negate any port forwarding you set up as those are set up by IP.
-
So…I dialed in 127.0.0.1 in the IVC comm box and gave others my IP address (as per TS client connection info) and nobody could connect to me.
I changed nothing but the dialed in IP on my system.
Mind you…I have hosted lots of missions and never had such an issue. -
So…I dialed in 127.0.0.1 in the IVC comm box and gave others my IP address (as per TS client connection info) and nobody could connect to me.
I changed nothing but the dialed in IP on my system.
Mind you…I have hosted lots of missions and never had such an issue.Sigh. The only time I have ever had your issue when serving is when I have either messed up the settings or before I had my computer set to a static internal IP and that changed which borked the port forwarding.
Verify your connect to IP block is 0.0.0.0 and your dedicated IVC server block is 127.0.0.1 with the IVC enabled and IVC automatic gain control checked for your serving BMS setup. Then verify that your computers IP and the IP set up in your routers configuration for port forwarding match. Best practice is to have that set static through Windows so it cannot de-link itself. Also it should go without saying but you need to run the IVC server prior to connecting yourself in the comms screen. If you do that and whomever is connecting to you has your REAL IP address of the router dialed into BMS it WILL work.
Now if you are saying they couldn’t connect AT ALL that is a different matter all together and the clients that are trying to connect could have goofed and not be running the same version of BMS or forgot to set their theaters back to KTO. If you try to connect different versions or theaters it will fail.
-
Stubiies2003,
Well…the culprit indeed was my Windows fixed IP settings were reset with the new router.
All is tested and operational.THank you all for your advice and help !
