WHS Experts ... WHS connector issues

[GCS]

Set up WHS put it into my domain XXX.local, assigned it an IP address. Seems to be up running fine.

I run the WHS Connector software and it sees the WHS and asks for a password. I key in the password (the one I use to log on to the actual WHS server ie Administrator password) and it acts like it is trying to connect and then says the operation cannot be completed at this time and thus I cannot connect to it.

I can ping the WHS machine and bring it up on the network. I CANNOT access the shared folders on it but I do see them.

I simply want to use WHS to backup the 7 workstations we have in our office.

We are in a domain and the main server runs SBS2008 with Exchange. We do not run any firewall software internally. All network gear is Cisco switches and a router.

Anyone have a solution to this issue? Googling turns up lots of folks who have had this in the past (ie older builds of WHS) but I have yet to find a solution that solves it. Also the troubleshooting guide for WHS did not help.

Thanks in advance for your help.

Greg

 

[Deleted member 4644]

make sure the password is the same. make sure you enter administrator as the user name

 

[GCS]

I don't have anywhere to enter a user name only a password and I have double checked the password several times and it is correct. I even changed it to be safe and still no go.

I have also checked the date and time on the workstation and the WHS to make sure they are the same since I read that had been an issues for others.

Greg

 

[Binky]

User account name on the WHS box should be the same as the client's computer name, or login name. Crap, I forget which one. Try them both.

For ease of use, the client's password on the WHS machine should be the same as the password you use to login to the client machine. If you dont use a password, set one, then google "login without password" and set the machine to automatically login. You need a password on the client machine.

 

[RebateMonger]

Did you try the WHS Connector Troubleshooter? It's part of the WHS Toolkit v1.1.

http://www.microsoft.com/downloads/...93-5f81-4ef7-8c7d-fe905094ab13&DisplayLang=en

There's also an MS paper on troubleshooting the Connector:

http://www.microsoft.com/downloads/...83-2c54-446e-86ed-e3e9e7e33a98&displaylang=en

You implied that you joined WHS to your Domain?

 

[GCS]

Did you try the WHS Connector Troubleshooter? It's part of the WHS Toolkit v1.1.

http://www.microsoft.com/downloads/...93-5f81-4ef7-8c7d-fe905094ab13&DisplayLang=en

There's also an MS paper on troubleshooting the Connector:

http://www.microsoft.com/downloads/...83-2c54-446e-86ed-e3e9e7e33a98&displaylang=en

You implied that you joined WHS to your Domain?

I tried these already with no luck.

Yes I simply went under my computer and placed it in the domain with the rest of our computers XXX.local.

Like I said I can see the machine just fine and can ping it all day long.

The password for the WHS and my machine happen to be the same (for simple testing purposes at the moment) so I know I am putting it in correctly.

Greg

 

[boomerang]

I think it's because you've put it in the domain. You should have left the default workgroup in place. Also, changing settings on anything outside of the console is a gamble. WHS is really meant to be administered through the console.

You can try to change it back to the default workgroup which is "WORKGROUP" and see if it works. I borked an install so badly trying to set up a HD through Disk Management ( I knew better, too) that I found it was easier to just do a fresh install. I could not even do a repair install which in WHS is termed a reinstall.

If you can't do it through the Console, it doesn't need to be done is a good rule of thumb.

Disclaimer: I am far from an expert on WHS.

Edit: After a quick glance it looks as though this may be of some help. http://forum.wegotserved.com/index.php?/topic/4179-wiki-join-windows-home-server-to-a-domain/

 

[GCS]

Ok so even though all my computers are in a domain the WHS does not need to be in it as well in order to see them?

Doing a fresh install is not a big deal either as I haven't done anything with the WHS machine at all other than try to connect to it.

Greg

 

[alanwest09872]

Good luck. I have had so many problems with whs login that i just gave up on it and ate the 100 bucks. Every time I would get the same error where it kept telling me I needed to enter a password then it said wrong password. It peed me off because everything would work fine even the backup utilty but I just couldnt log into it. and the problem would come on suddenly after working for 2-3 months.

 

[SunnyD]

#1 - WHS is not compatible with AD domains, but it can happily exist on an AD domained network provided it is not domained.

#2 - Check to verify your WHS machine time & date (and timezone) are set correctly and your client machines as closely match the WHS machine as possible. This is particularly important.

An easy way to see if #2 is the problem is if you can physically remote desktop into the machine. If you can, but the connector fails, odds are that may be your problem.

 

[boomerang]

Ok so even though all my computers are in a domain the WHS does not need to be in it as well in order to see them?

I hope I made it clear, I am not an expert, but according to the small amount of research I did, it appears it will work.

Doing a fresh install is not a big deal either as I haven't done anything with the WHS machine at all other than try to connect to it.

Greg

Try changing to WORKGROUP first. A fresh install is really time consuming. I can only assume a reinstall is lengthy too.

 

[GCS]

Well what do you know, you guys were right.

Took it out of the domain and bang connected instantly this time during the install and now is slated for backup each night.

Greg

 

[boomerang]

Yaayy!!

Glad for both of us! :awe:

 

[GCS]

Guess you learn something new everyday. I always thought you had to be in the domain to have access to other machines. Oh well glad I have access now. Let's see how WHS does on these little old workstations.

Greg

 

[RebateMonger]

As you found, WHS definitely doesn't need to join your Domain to do it's job. I've probably installed ten of them in offices with Domains and I've never attempted to join them to the Domain. Joining it to a Domain is definitely not supported by MS. I guess we know why.

Edit: In addition, that link posted by Boomerang says that WHS will start doing automatic reboots every couple of hours after it's been joined to a Domain for a couple of days.

 

[RebateMonger]

Try changing to WORKGROUP first. A fresh install is really time consuming. I can only assume a reinstall is lengthy too.

I used to think the same thing. True, it DOES take a long time to install WHS. But MS did a really good job of limiting human interaction except at the very beginning and the very end of the installation. Once you get the install started, you can go get a beer. Good enough reason for me, anyway.

 

[GCS]

Agreed once I got past the issue with the wrong type of drive (ie I had an IDE drive) and needing to install SATA drivers WHS did it's thing and it was done.

And outside f this "domain issue" it was pretty simple.

Greg