> Your web interface is acting very odly, in the 7.9.2 server.
Is it different from previous versions? Did you try an older version on
that installation?
> The http server fires up and in netstat -l I see it is bound to no
> specific network interface. That's okay, but having control would be
> better.
You've been shown how you can bind it to one. Did you try that?
> Still it gets worse. This server has multiple network interfaces, 2
> internal and one external (public internet). When I connect to the
> server from my internal LAN subnet I get a 403: Forbidden response. The
As said before: tell LMS what interface to use. It seems to pick the
wrong one. That's nothing new. The only change to older versions is that
it would no longer accept connections from the other interfaces.
Previously it would accept any connection from anywhere. Whether it be
local or not.
> server log is trying to send its response message to my public
The server is only logging to a local file, no network.
> address. Even though the traffic is all totally internal. If I open a
> hole in my firewall for port 9000, sure enough I can connect with the
> server on port 9000 no problem from the public Internet!!!!
That's nothing new. You just didn't realize because you didn't think
about it.
> Nothing I have tried will make the server operate (bind) itself to my
> internal lan interface.
What did you try? I ask again: did you try the advice given in the other
thread? From your response there I must assume you did not.
> Any tips, I have already seen others facing the same problems, so I'm
> not alone. Its inflexible.
No, it's too flexible. If it wasn't flexible it would only run on
Windows :-).
--
Michael
Is it different from previous versions? Did you try an older version on
that installation?
> The http server fires up and in netstat -l I see it is bound to no
> specific network interface. That's okay, but having control would be
> better.
You've been shown how you can bind it to one. Did you try that?
> Still it gets worse. This server has multiple network interfaces, 2
> internal and one external (public internet). When I connect to the
> server from my internal LAN subnet I get a 403: Forbidden response. The
As said before: tell LMS what interface to use. It seems to pick the
wrong one. That's nothing new. The only change to older versions is that
it would no longer accept connections from the other interfaces.
Previously it would accept any connection from anywhere. Whether it be
local or not.
> server log is trying to send its response message to my public
The server is only logging to a local file, no network.
> address. Even though the traffic is all totally internal. If I open a
> hole in my firewall for port 9000, sure enough I can connect with the
> server on port 9000 no problem from the public Internet!!!!
That's nothing new. You just didn't realize because you didn't think
about it.
> Nothing I have tried will make the server operate (bind) itself to my
> internal lan interface.
What did you try? I ask again: did you try the advice given in the other
thread? From your response there I must assume you did not.
> Any tips, I have already seen others facing the same problems, so I'm
> not alone. Its inflexible.
No, it's too flexible. If it wasn't flexible it would only run on
Windows :-).
--
Michael
Comment