Problem with connecting to MeetingPlace Express server over HTTP

Alexander.Khlemanov_2 · ‎11-28-2008

Hi guys,

I am trying to connect to my MeetingPlace Express server over HTTP from an end-user PC. I can ping my MPE server by the IP address or by the name from this PC but as soon as I am trying to connect over http I can not do it. I have tried all three URLs below but with the same negating result:

http://172.20.16.4/public/login

http://pscmpe01-0.pic.int/public/login

http://pscmpe01-0/public/login

When I am connecting from the console I am connecting to http://pscmpe01-0.pic.int/public/login and it is always successful.

Any idea what the problem might be? Any help will be much appreciated.

Jonathan Schulenberg · ‎11-28-2008

Make sure that

-172.20.16.4 is the IP of eth0 on the server.

-pscmpe01-0 is the DNS name for 172.20.16.4

-eth1 has an IP address in the same subnet

-eth1's IP address also has a DNS name that is resolvable. Note: The DNS names and IP addresses must be different than eth0! I typically name eth0 "meet" and eth1 "meet-rtmp" for example.

Tomcat/Apache only listens on eth0. If you're not getting a response, my first guess would be it's making the request on the eth1 interface.

You can use the "net" command to make modifications to the configuration. If you're not a Linux native, type "sudo net" at the command line once you have logged in as mpxadmin.

Alexander.Khlemanov_2 · ‎12-01-2008

Hi,

No worries, it is all sorted now. It was a problem with the MPE server interface name definition on the customer's DNS. The IP address 172.20.16.4 had to be associated with pscmpe01-0.pic.int and not simply with pscmpe01-0.