We are doing just that! Our problem was that the caching to local
cache or Janet varied depending on network traffic - ie heavy use of
local cache dropped the check to Janet. That is when connections
failed. Now all our cache checks are to Janet - so by trial and error
we have to get cache bypasses for each service. We only have to enter
the beginning of the url - eg:
http://global.umi.com/
instead of the whole of the url. This may be different for your site
and how they manage the cache bypass. Also, remember that the
charging for US calls has had a serious impact on caching policy.
If you come across any better solutions we will be very pleased to
have information.
Elizabeth Chamberlain
Brunel University
>
>Has anyone else using JANET had problems with their e-journals recently?
>
>All of our journals where access is by IP address have suddenly stopped
>working. Having logged in as the subscription administrator to a couple of
>the journals sites and checked the registration details, it appears that
>the IP address of the Janet cache is now being passed onto the publishers
>server, and not our own IP address, so we are therefore denied access form
>the full-text.
>
>Out network manager is looking into this and taking the matter up with the
>Janet Cache helpdesk
>
>In the meantine, short of creating a very long local exclusion file,
>listing the URL for every e-journal, has anyone else found a solution to this?
>
>Many thanks,
>
>Jeremy Evans
>
>NIBSC library
>
>
>
>
>Jeremy Evans
>Information Services
>
>Library
>NIBSC
>Blanche Lane
>South Mimms, Potters Bar
>Hertfordshire UK EN6 3QG
>01707 654753 ext 323/326
>FAX: 01707 646845
>Email: [log in to unmask]
>
>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|