Hi Shawn, The firewall was the first thing I looked into and after fiddling with it, I still see the issue. But if that was the issue, why WebSphere doesn't run into it but Jetty is? However, your point about domain / non domain and private / public network maybe provide me with some new area to look into.
Thanks Steve On Fri, Apr 24, 2015 at 10:11 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/24/2015 8:03 AM, Steven White wrote: > > This maybe a Jetty question but let me start here first. > > > > I have Solr running on my laptop and from my desktop I have no issue > > accessing it. However, if I take my laptop home and connect it to my > home > > network, the next day when I connect the laptop to my office network, I > no > > longer can access Solr from my desktop. A restart of Solr will not do, > the > > only fix is to restart my Windows 8.1 OS (that's what's on my laptop). > > > > I have not been able to figure out why this is happening and I'm > suspecting > > it has to do something with Jetty because I have Solr 3.6 running on my > > laptop in a WebSphere profile and it does not run into this issue. > > > > Any ideas what could be causing this? Is this question for the Jetty > > mailing list? > > I'm guessing the Windows firewall is the problem here. I'm betting your > computer is detecting your home network and the office network as two > different types (one as domain, the other as private, possibly), and > that the Windows firewall only allows connections to Jetty when you are > on one of those types of networks. The websphere install may have add > explicit firewall exceptions for all network types when it was installed. > > Fiddling with the firewall exceptions is probably the way to fix this. > > Thanks, > Shawn > >
