Error connecting with 3.5 console

[DTracy]

Hi all;

I have installed ePO 3.5 on my XP-Pro laptop. I am loged onto our lan as administrator. When I try to logon to the ePO server 3.0.1 I get the following error message:
*****
Unable to log on as the database administrator. Be sure that you are logged on as a local adinistrator.
*****

I checked the account settings on this laptop for myself and the administrator. Both have the ePO users group membership included.

I am able to connect to the ePO databases (Reporting) for the reports and run any report that I need.

I tried to install ePO console 3.0.1 on this laptop and it also failed but it didn't show a specific error message other than a browser error 4. However I installed the ePO console 3.0.1 onto a W2k workstation and am able to logon with no problems.

Any ideas would be greatly appreciated.



Best Regards,
David Tracy

 

[PredatorUK]

I normally put the server in to the local host file on my laptop / workstation to logon to the ePO server.

 

[DTracy]

Hi PredatorUK-

I don't think I understand what you mean by putting the server into the local host file on your laptop. When ePO 3.5 installed on my XP laptop it made an entry for ePO User Group in the local groups folder, and there are entries for myself and Administrator in the local users folder. Also, domain entries for myself and admin are in user accounts and both local and domain admin account passwords are the same. Would you explain a little further about your local host file please?

Thanks ever-so-much for your assistance.




Best Regards,
David Tracy

 

[JimmyZ1]

I think PredatorUK is talking about the lmhost file or the host file... located under C:windows\system32\drivers\etc

you can append names to IP addresses, I think its for DNS resolution when a DNS server can't be found.

 

[DTracy]

Xavier2-

I've used the same DNS numbers on my XP laptop as on my W2k workstation, the W2k works, the XP does not.

Thanks



Best Regards,
David Tracy

 

[JimmyZ1]

check out my posting about problems logging into the reports sounds like you have the reverse problem, might be the same fix...

It should be located a couple of posts down call

A problem with logging into the reports

 

[DTracy]

Xavier2,

Both the W2k and the XP were already configured the same on that registry key.

A search of the NAI knowledgebase indicated the problem to be related to group policy. However, the workstation and the laptop have the same group policy settings.

Any ideas would be greatly appreciated.

Thanks



Best Regards,
David Tracy

 

[DTracy]

Xavier2,

Both the W2k and the XP were already configured the same on that registry key.

A search of the NAI knowledgebase indicated the problem to be related to group policy. However, the workstation and the laptop have the same group policy settings.

Any ideas would be greatly appreciated.

Thanks

Best Regards,
David Tracy

 

[JimmyZ1]

are your DNS settings correct?

 

[DTracy]

Xavier,

Yes, the DNS are OK. The W2k workstation and the XP laptop are configured the same, same lan, dhcp. The W2k works, the XP doesn't.

A couple of weeks ago I started a thread regarding the use of XP and ePO Console. All the responses indicated that XP did work--not for me!

I appreciate your interest and help on the problem.



Best Regards,
David Tracy

 

[Lyf]

Can you mix console and server versions like that? I always assumed that a 3.5.x console would only connect to a 3.5.x server. From 3.0 to 3.5 was a major version change, wasn't it? A brief look through the documentation never mentions servers and consoles with different versions.

 

[JimmyZ1]

Yeah, different version consoles won't work. it has to be 3.5 to 3.5

 

[DTracy]

Xavier & Lyf,

Thanks, I removed the 3.5 and installed the 3.0.1 console on the XP. It starts, connects to the server, can run reports, but when I access the repository I get a 404 error in the browser.

I was on the phone with McAfee yesterday for nearly three hours and accomplished nothing. All suggestions had already been tried.

Well, sooner or later this puppy is going to work!

Thanks for your help.



Best Regards,
David Tracy

 

[JimmyZ1]

upgrade everything to 3.5...

 

[DTracy]

I had so much trouble installing the 3.0.1 and getting it to work that I am afraid to try upgrading to 3.5. It might crash and then I would be back to doing virus updates manually.




Best Regards,
David Tracy

 

[JimmyZ1]

3.5 worked great for us, and we had a bunch of problems with 3.0, bad problems with hundreds of machines.. but all those problems have gone and ePO works great.

goodluck