I set up a local web server and my local web app works fine putting localhost in the browser, but when I connect it to a network it stops working, been a crazy time trying to figure out why. The app keeps running in a VM but won't communicate.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2020-06-06 03:34, Eric Douglas wrote:

I set up a local web server and my local web app works fine putting localhost in the browser, but when I connect it to a network it stops working, been a crazy time trying to figure out why. The app keeps running in a VM but won't communicate.

No idea about WebLogic, but one lead maybe to check which network
interfaces you bind to. There's bound to be documentation for that.

--
DF.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 05 Jun 2020 18:34:12 -0700, Eric Douglas wrote:

I set up a local web server and my local web app works fine putting
localhost in the browser, but when I connect it to a network it stops working, been a crazy time trying to figure out why. The app keeps
running in a VM but won't communicate.

Explain 'stops working' in a a bit more detail, please. The bare
statement could mean anything from it webserver crashing to it not being accessible from another computer and lots else as well.

For starters, is the host machine running a firewall? If so are the
port(s) your webserver uses, usually port 80, accepting connections from
hosts on your local net? ...from hosts on the wider Internet? It
certainly sounds as if this could be the problem.

My tools of choice if I suspect a network or firewall problem are ping,
nmap, traceroute and, as a last resort, wireshark - used in approximately
that order.


--
Martin | martin at
Gregorie | gregorie dot org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Saturday, June 6, 2020 at 5:18:11 PM UTC-4, Martin Gregorie wrote:

Explain 'stops working' in a a bit more detail, please. The bare
statement could mean anything from it webserver crashing to it not being accessible from another computer and lots else as well.

For starters, is the host machine running a firewall? If so are the
port(s) your webserver uses, usually port 80, accepting connections from hosts on your local net? ...from hosts on the wider Internet? It
certainly sounds as if this could be the problem.

My tools of choice if I suspect a network or firewall problem are ping, nmap, traceroute and, as a last resort, wireshark - used in approximately that order.

--
Martin | martin at
Gregorie | gregorie dot org

It's just a local test bed, the client machine is the server physical machine. The weblogic server runs in a Java VM. It's default port is 7001. I've tried changing the port, the issue continues. If I boot the computer with no network connected it
works fine. If I plug in to the internet it stops working. There is no error I can see from the server VM. I normally start it from Eclipse. You can see in task manager the Java session still running under Eclipse. I can telnet to localhost on that
port. I can of course ping localhost. I open a web browser and put in the path under localhost:port/appname. This works fine when not connected, fails when connected. Weblogic also has an administrative console in a web browser, which is also
accessible only when not connected. I can run TOAD and access the database just fine.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, 06 Jun 2020 18:39:28 -0700, Eric Douglas wrote:

On Saturday, June 6, 2020 at 5:18:11 PM UTC-4, Martin Gregorie wrote:

Explain 'stops working' in a a bit more detail, please. The bare
statement could mean anything from it webserver crashing to it not
being accessible from another computer and lots else as well.

For starters, is the host machine running a firewall? If so are the
port(s) your webserver uses, usually port 80, accepting connections
from hosts on your local net? ...from hosts on the wider Internet? It
certainly sounds as if this could be the problem.

My tools of choice if I suspect a network or firewall problem are ping,
nmap, traceroute and, as a last resort, wireshark - used in
approximately that order.


--
Martin | martin at Gregorie | gregorie dot org

It's just a local test bed, the client machine is the server physical machine. The weblogic server runs in a Java VM. It's default port is
7001. I've tried changing the port, the issue continues. If I boot the computer with no network connected it works fine. If I plug in to the internet it stops working. There is no error I can see from the server
VM. I normally start it from Eclipse. You can see in task manager the
Java session still running under Eclipse. I can telnet to localhost on
that port. I can of course ping localhost. I open a web browser and
put in the path under localhost:port/appname. This works fine when not connected, fails when connected. Weblogic also has an administrative
console in a web browser, which is also accessible only when not
connected. I can run TOAD and access the database just fine.

'localhost' doesn't count as a network: its an always-on part of the OS
and, depending how that's organised, may not have anything in common with
your OS's networking modules. It fact that it works when networking is
disabled suggests that its completely separate.

So, what else on that computer is associated closely enough with network software that its only running when networking is enabled? A firewall
would certainly be a candidate. What else? Can you ping that machine from another host on your LAN when networking is enabled?

If it turns out to be a windows or Mac issue, somebody else will have to
help: I haven't used windows for over 15 years or a Mac for 25 years.


--
Martin | martin at
Gregorie | gregorie dot org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)