Solved Local Server hosting login with local client but no one can hear me on IVC while in 3D
-
@Micro_440th
And just for the networking challenged like me: Would that be this name?(not some name stated in BMS somewhere ?)
-
@MaxWaldorf said in Local Server hosting login with local client but no one can hear me on IVC while in 3D:
@Micro_440th Basic Network concept…
Don’t set 2 times the same name on the same LAN network…
Well Prime and Prime Server isn’t the same name just similar using as the logbook name in Falcon BMS. If you remove the space it works fine as well.
-
@jayb said in Local Server hosting login with local client but no one can hear me on IVC while in 3D:
@Micro_440th
And just for the networking challenged like me: Would that be this name?(not some name stated in BMS somewhere ?)
@Micro_440th said in Local Server hosting login with local client but no one can hear me on IVC while in 3D:
DoneYa it is the logbook name have not really tried with the System Name.
-
AFAIK it might be a netbios thing…
spaces in netbios don’t translate at all I think…
-
@Micro_440th Also forcing CS to the local client is necessary before anyone will be able to hear the client in IVC.
-
@AviationPlus said in Local Server hosting login with local client but no one can hear me on IVC while in 3D:
@Micro_440th Also forcing CS to the local client is necessary before anyone will be able to hear the client in IVC.
I don’t do it.
-
@AviationPlus nope
-
I would swear I remember seeing a similar thread about this … viz. host names (or is it phonebook entry names?) and callsign/logbook names colliding. But I can’t find anything in past few years…
Here’s a similar thread from 2016 though. Whatever this quirk is, it sounds like it’s been around awhile.
-
@MaxWaldorf Interesting must have just happened to work after I changed it. Will change it back and see what happens.
-
@MaxWaldorf That’s probably that, netbios doesn’t support blank, so the system must have truncate the name before the space, resulting in the same name.