paulc2000
asked on
Can't browse LOCAL web server? But can ping it!
Hi All,
Very urgent problem, and would be infinitely grateful if someone could help me with this.
I'm no networking expert, but I know enough to be dangerous. Here's the story: I installed a test version of a reservation system that my company uses (Micros Opera) [not to be confused with either Microsoft or the Opera browser!!!] on a test server in officeA. All went ok - I added the name of the computer and its IP address to the hosts file of the test clients, and there was no problem. The IP of the test server was 192.168.3.36. It and 3 other PCs were hooked up directly to a D-Link switch, which in turn was connected to a Netgear router.
I had to ship the whole setup to another office overseas (officeB). When the server and clients were hooked up in the exact same configuration as in officeA, they didn't work as planned... The IP of the server machine is now 192.168.1.150. I got the local guy there to change the hosts file on all the machines to that address, but to no avail. There is no problem pinging the server from any of the clients, but it doesn't browse as it should. Though it does something: the start URL for the app is http://servername/OperaLogin/ which then redirects to http://servername/OperaLogin/Welcome.do - the redirect works, but nothing else - "The page cannot be displayed".
http://192.168.1.150/OperaLogin/ does not work either.
Also, the Internet is available on all machines - server and clients. No problem browsing sites. Just can't browse the local server, but can ping it just fine.
Any ideas would be gratefully tried!
Thanks,
Paul
PS: Opera is a Java app and is accessed via Internet Explorer and uses Oracle as its DB. AFAIK, it uses Apache, but that's installed transparently, so I don't really know... If I run netstat -b I can see Apache running on what appears to be several ports... don't ask me why!
Very urgent problem, and would be infinitely grateful if someone could help me with this.
I'm no networking expert, but I know enough to be dangerous. Here's the story: I installed a test version of a reservation system that my company uses (Micros Opera) [not to be confused with either Microsoft or the Opera browser!!!] on a test server in officeA. All went ok - I added the name of the computer and its IP address to the hosts file of the test clients, and there was no problem. The IP of the test server was 192.168.3.36. It and 3 other PCs were hooked up directly to a D-Link switch, which in turn was connected to a Netgear router.
I had to ship the whole setup to another office overseas (officeB). When the server and clients were hooked up in the exact same configuration as in officeA, they didn't work as planned... The IP of the server machine is now 192.168.1.150. I got the local guy there to change the hosts file on all the machines to that address, but to no avail. There is no problem pinging the server from any of the clients, but it doesn't browse as it should. Though it does something: the start URL for the app is http://servername/OperaLogin/ which then redirects to http://servername/OperaLogin/Welcome.do - the redirect works, but nothing else - "The page cannot be displayed".
http://192.168.1.150/OperaLogin/ does not work either.
Also, the Internet is available on all machines - server and clients. No problem browsing sites. Just can't browse the local server, but can ping it just fine.
Any ideas would be gratefully tried!
Thanks,
Paul
PS: Opera is a Java app and is accessed via Internet Explorer and uses Oracle as its DB. AFAIK, it uses Apache, but that's installed transparently, so I don't really know... If I run netstat -b I can see Apache running on what appears to be several ports... don't ask me why!
ASKER
Thanks for the reply. The problem is that the router in officeA assigns addresses in the 192.168.3.XXX range (that's where the server was set up/configured). OfficeB has a router that assigns addresses in the 192.168.1.XXX range. I've searched high and low on the server for any mention of "192.168.3.36" but they are few and far between, and changing them to 192.168.1.150 doesn't work.
I've called the support people, but I don't know if they'll have good news for me in the morning...
I've called the support people, but I don't know if they'll have good news for me in the morning...
Does jinit.exe try to run on the client computers when they connect? It will probably want to re-register the terminals since the IP for the server changed, and the IP addresses for the clients too.
OfficeB has a different router than OfficeA had, correct?
OfficeB has a different router than OfficeA had, correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it turned out to be an Opera-specific problem, rather than Apache or Java. One flight to Paris, and ten mins on the phone fixed it... Shame they didn't do that while I was back home... Agh!!!!
Anyway, thanks for the suggestions :)
Anyway, thanks for the suggestions :)
Why did your Opera server decide to lease an IP from that Netgear router suddenly? Why did the IP change from static IP address 192.168.3.36 to a leased IP of 192.168.1.150 from the router? It sounds like maybe your server had 2 NIC's, and your tech overseas plugged the other (DHCP'ed) NIC into the network, but not the NIC with the static address.
Opera's config of Apache can be picky about the listening IP. I'd go back to your original plan. Change the hosts files on your client machines to point to your server computer name with 192.168.3.36
Also, the Netgear should claim 192.168.3.1, or something on the 192.168.3.0 subnet, unless you edit the route table on the Netgear to pass traffic between the 192.168.1.0 subnet and the 192.168.3.0 subnet.
Also, I'd add the server name and the IP address of the server to the list of Trusted websites in the client machines' web browsers (under Tools, Internet Options, Security, Trusted Sites). It seems like that Java app that the Opera server pushes out refers back to the server by IP address sometimes, and by servername at other times.