- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: OmniBackII GUI on Windows 2000
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2000 10:51 AM
тАО08-17-2000 10:51 AM
OmniBackII GUI on Windows 2000
Your OmniBack II administrator set your user rights so that you do not have access to any OmniBack II functionality.
Contact your OmniBack II administrator for details.
Any ideas to remedy this problem?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2000 11:04 AM
тАО08-17-2000 11:04 AM
Re: OmniBackII GUI on Windows 2000
Stop and restart NT gui. Should work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2000 11:17 AM
тАО08-17-2000 11:17 AM
Re: OmniBackII GUI on Windows 2000
User Name aknoll
Group/Domain *
Real Name
Host Name is this the unix host or my
2000 workstation IP?
User Group Admin
Windows User
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2000 11:27 AM
тАО08-17-2000 11:27 AM
Re: OmniBackII GUI on Windows 2000
If you want to type, pay attention on solving name convention. If using DNS you need to provide full qualified name.
Did I ansker to your question?
(As an ex., my NT user that uses OmniBack on NT is CLSTRADMIN , real name clstradmin, Host Name omrdb1.domainname.com Group/Domain *
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2000 11:32 AM
тАО08-17-2000 11:32 AM
Re: OmniBackII GUI on Windows 2000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2000 11:40 AM
тАО08-17-2000 11:40 AM
Re: OmniBackII GUI on Windows 2000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2000 12:57 PM
тАО08-18-2000 12:57 PM
Re: OmniBackII GUI on Windows 2000
http://forums.itrc.hp.com/cm/CategoryHome/1,1147,163,00.html
This is a fairly common issue - but the fix may be a little difficult.
Omniback uses name resolution as part of its security model.
As a result, if the name resolution in your environment is inconsistent, you can have this security issue.
Since you have Windows 2000, you may well have set up a private DNS (in order to get active directory to work.) This caused me some grief...but eventually, using hosts files I got things working.
Alternatively, you may have multiple network cards. Setting up name resolution for these can be a chore. Correct name resolution for multiple network card machines is particularly important where we have integrations of Omniback to hot backups of databases (Oracle, informix, Syabase, MS-SQL...)
In the short run, you can open up a big hole in the Omniback security, by allowing anybody from any group from any server to act as an Omniback administrator.
Then tighten the security model, until you find the issue.
Some times the issue is name resolution mismatches, some times it is spelling, or CASE SENSITIVITY.
Good Luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2000 01:06 PM
тАО08-18-2000 01:06 PM
Re: OmniBackII GUI on Windows 2000
on NT:
(from the command prompt)
HOSTNAME
SET (values for username and userdomain)
nslookup ntbox
nslookup ntbox.domain.com
nslookup nt.ip.ip.ip
(same idea again, nslookup the cell server...)
NSLOOKUP may fail and complain about 127.0.0.1 - if so ignore nslookup, and concentrate on HOSTS, otherwise, fix DNS...
c:winntsystem32driversetchosts
(entries for localhost, nt box, and for cell server)
On the cell server
more /etc/opt/omni/users/UserList
compare the comment, username, groupname, servername
/etc/hosts
on UX, make note where nslookup fresolves from (ie. files, NIS, DNS...)
nslookup ntbox
nslookup ntbox.domain.com
nslookup nt.ip.ip.ip
(same idea again, nslookup the cell server...)
If you look carefully at the differences
carefully, there is a really strong chance you will find the issue.
Again, good luck.