Menu
▾
▴
#71 Strange Login behavior too
This is on Redhat 7.2 with all updates installed,
including these software packages:
Apache 1.3.20-16
MySQL 3.23.41-1
php-4.0.6-7
IRM-1.3.4
Created database fine without errors but If I try to
login using Admin/admin I get a blank page - not even
an error page using either MS Exploder v5.5 or 6.0 and
Netscape on Linux or Mozilla, or Lynx.
If I use any other name and password, I get bad
password BUT it allows me to change any information in
setup, including admin password. I added my own name
and password and it is still the same. On login, I
get a error page, on logout....its the same. Almost
like the host is unresolvable.
Logged In: NO
I found the fix for this:
our server is on an internal LAN, only assessable from our
technicians and customers whom have been supplied a password
to access it. It must be done over an encrypted tunnel.
Because its on a private ip address range, the apache conf
is set for the server name by its IP address.
I monitored this by using ethereal and capturing the packets
from client to server and found that "somewhere" the login
script was really looking for http://your.server.com I
browsed through all files until I found the corresponding
entry at the bottom of /irm-root/include/config.inc.php I
changed this to the servers IP address and fixed user and
admin logins.
Logged In: NO
I found the fix for this:
our server is on an internal LAN, only assessable from our
technicians and customers whom have been supplied a password
to access it. It must be done over an encrypted tunnel.
Because its on a private ip address range, the apache conf
is set for the server name by its IP address.
I monitored this by using ethereal and capturing the packets
from client to server and found that "somewhere" the login
script was really looking for http://your.server.com I
browsed through all files until I found the corresponding
entry at the bottom of /irm-root/include/config.inc.php I
changed this to the servers IP address and fixed user and
admin logins.
Logged In: NO
I found the fix for this:
our server is on an internal LAN, only assessable from our
technicians and customers whom have been supplied a password
to access it. It must be done over an encrypted tunnel.
Because its on a private ip address range, the apache conf
is set for the server name by its IP address.
I monitored this by using ethereal and capturing the packets
from client to server and found that "somewhere" the login
script was really looking for http://your.server.com I
browsed through all files until I found the corresponding
entry at the bottom of /irm-root/include/config.inc.php I
changed this to the servers IP address and fixed user and
admin logins.
Logged In: NO
I found the fix for this:
our server is on an internal LAN, only assessable from our
technicians and customers whom have been supplied a password
to access it. It must be done over an encrypted tunnel.
Because its on a private ip address range, the apache conf
is set for the server name by its IP address.
I monitored this by using ethereal and capturing the packets
from client to server and found that "somewhere" the login
script was really looking for http://your.server.com I
browsed through all files until I found the corresponding
entry at the bottom of /irm-root/include/config.inc.php I
changed this to the servers IP address and fixed user and
admin logins.
Logged In: NO
As noted by 'nobody', this problem is almost always due to
an incorrect entry in the /irm_root/include/config.inc.php
file... usually the last entry that asks for your host
name. Also check to make sure that your
username/password/database are keyed in correctly in this
file.
Logged In: YES
user_id=44672
This bug matches a bug already in our database. Your submission
has been counted, but has been merged with the previous bug
report to save our developers from getting headaches.