Oct. 5th, 2006
Oct. 5th, 2006 09:11 am
Quick tech support required.
http://www.appliedvegetationdynamics.co.uk/database.html
and click the enter database button. Let me know what happens. Ta!
Thanks everyone!
Port 90 should be in the permissable range, and the machine itself is visible externally(I assume, anyway, this is the problem when I'm inside the system). So we obviously need to sort out how the reference manager database is being connected to. The actual web admin for this site isn't back until tomorrow so no worries.
Oct. 5th, 2006 11:10 am
Quick tech support pt 2.
http://www.appliedvegetationdynamics.co.uk/database.html
and click the enter database button. Let me know what happens. Ta!
Poo. It's now failing internally.
Can someone try this link http://138.253.199.114:90/rmwp with IE rather than firefox?
UPDATE: Hmm. The database crashed, possibly due to the demand coming in through my asking people to check. This is a bit worrying as, well, there would surely have been only a handful of hits. We've reset it and Emma is going to check at lunchtime but this all looks increasingly dodgy.
Oct. 5th, 2006 04:23 pm
Database expert help required!
Sooo...
Webserver runs database 1 through some sort of microsoft server package. They also want to run another database package that has it's own web publishing software. I'm guessing (because webpages, I only write them) that both systems can't use port 80 (the http port) hence the placing of DB2 on port 90. This is cleared with our firewall but still seems to be invisible to the outside world (
blue_condition reports that many institutions block all ports but http and https)
Is the only solution to this problem to run them on separate webservers? Just before I advise the increasingly irate academic that this is the case
Webserver runs database 1 through some sort of microsoft server package. They also want to run another database package that has it's own web publishing software. I'm guessing (because webpages, I only write them) that both systems can't use port 80 (the http port) hence the placing of DB2 on port 90. This is cleared with our firewall but still seems to be invisible to the outside world (
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
Is the only solution to this problem to run them on separate webservers? Just before I advise the increasingly irate academic that this is the case