Tech Troubleshooting

E-Resources Access Requirements

Note: TAMHSC username and password will not be an authentication option for library resource or services after June 25, 2018. For more information, view the press release Changes to TAMHSC Login for Library Resources.

E-Resources Access Requirements

  • Accept certificates when accessing library resources from a TAMU Libraries website.
  • Javascript and cookies must be enabled/allowed.
  • A NetID is required for off campus access, and access from HSC buildings.
  • Firewall settings on your network or computer may interfere with access. Port 9003 must be accessible.

Still having problems? Please contact us through our Report a problem form so we can further troubleshoot your access issue.

Problems Logging In

For questions or help, contact AskUs Services or Help Desk Central. Common fixes are noted below:

e-Journals (SFX) Access

The library uses the URL below to allow access to e-journals. Port 9003 must be open. To check if you have access to this address:

  • Click the test URL
  • Confirm link takes you to a black screen with a large @SFX created from red numbers, letters, and characters, see the image below.
  • If the page does not load as described, you will need to contact your network administrator or Internet service provider and request they open port 9003.
SFX Login Screen

Off-Campus Access

Off-Campus Bookmark

Add this bookmark to your browser to access Libraries content with your NetID.
  1. Make sure your browser's toolbar is visible
  2. Drag this bookmark image into your bookmarks bar: Find at Texas A&M Libraries
  3. When you land on a resource, click the bookmark and it will prompt you to log in.

Configure Google Scholar to access library resources

Links to Google Scholar on the Libraries websites use software called EZproxy to provide off-campus access to full text subscriptions. EZproxy assigns all computers the same IP address. During times of heavy usage, this occasionally causes Google to misinterpret searches as being made by a robot and block access. There are a couple of options to resolve the problem: