Joining BCM to SBS Domain 1

[awebber]

Hi,

I am a new user of the BCM. We had it installed last week. Our supplier said network configuration was up to us, not them, so I gave it a go!...

Being cautious, I tried first to change the networking so that the BCM was now in our network IP address range and after this successfully joined it to a temporary workgroup so we could back up the configuration. This was done successfully and all was fine.

I then tried joining the BCM into our Windows domain - so that the backup could be saved direct to the server for easy backup. It joined the domain successfully - the NetDom command in maintainence confirms it can see our PDC.

Unfortunately, since joining the domain, I can no longer log into configuration or Wizards as the username / password is invalid (or locked out). I presume the password must be correct as I can log into Maintenance successfully.

Was I supposed to do anything else before or when adding the BCM to the domain?

Any help is gratefully received.

 

[biv343]

I ran into this once before when I joined a BCM to a domain - that was the one and only time I did that.

Try logging in with a username of bcmname\supervisor (where BCM name is the netbios name of your BCM). That may get you logged in. If I'm not mistaken, that was the path that I took.

Once I got logged in, I put the BCM back in a workgroup. You can do backups to a domain server when the BCM is in a separate workgroup - just be sure to specify your domain name in the username (such as mydomain\myaccount). Or you can do FTP.

Hope this helps.

 

[awebber]

Hi,

Thanks for your answer. Unfortunately it doesn't seem to help in my case. The BCM name is simply BCM but logging in as bcm\supervisor has not worked.

Is there anything further I can try?

 

[biv343]

Maybe try adding supervisor with appropriate password as a user on your domain? The log in with a username of yourdomain\supervisor.

I wish I could remember what I did to get myself out of the same situation a couple years back, but I'm drawing a blank. All I remember is that I told myself I'd never do it again.

Have you tried logging in with the ee_admin account and the appropriate password?

 

[awebber]

Apologies for the delay in response...

I tried your suggestion but that did not do the trick either I'm afraid. The ee_admin account would not login either, only in the maintenance screen.

Our installer made a visit and confirmed the problem existed. Then today, between us, we discovered a solution.

Luckily - we recalled that one of the two LAN cards was in a different IP address range that would not communicate with the domain. We just put a spare PC into that address range, connected it to the other LAN card, and we could then log into the BCM.

We were next able to remove the BCM from the domain and back to a workgroup.

So I didn't really resolve the problem, but did find a way to circumnavigate it. I hope this will be of help to anyone else who lands in the unfortunate position.

I too am now telling myself I will never do it again ;-)

Many thanks for your help. It has been very much appreciated.

 

[acewarlock]

If you had used the serial port, you could have logged in and changed the IP address and domain.

 

[nsantin]

Create/reset the computer account for the BCM on your Domain Controller.

 

[awebber]

>AceWarlock - Thanks for the hint - wasn't aware of that, so will bare it in mind in future.

>nsantin - I had also tried what you suggested. The BCM would not join the domain until I created a computer account for it. While it was a member of the domain it generated errors in the server event logs reading that the trust between the workstation and server had failed. On browsing support sites for this error it is suggested that resetting the account would help and I believe this is achieved through the NetDom utility. However, the NetDom utility only produced "Access Denied" error messages when used in relation to the BCM account. Although I'm no longer in a position to re-create and troubleshoot the situation, I am still keen to hear peoples thoughts and suggestions as this still has me somewhat baffled!!

Thankyou both for your suggestions.

 

[augs]

We have an older BCM 1000 running v3.6. One of the first things we did was join it to our domain. We have had no problems at all. We used the Unified Manager to configure the system and join it to the domain. There was nothing we needed to do initially except make sure the BCM was on the same network (IP and subnet needed to be set within our network range). We can now easily direct the BRU to place its file on a network server for backup by our enterprise software.