Auth problems between WHS and Windows 7
-
20 เมษายน 2555 16:04
I have got Windows Home Server running on one machine, and Windows 7 Professional running on another. I also have a couple of Macs, but they work perfectly and can access the shared folders.
The username of the Windows 7 machine is Anjow, so I create a user on the server with that name, and with the same password. I try and connect and it asks me for user/pass and automatically populates "ANJOWGAMES\Anjow". I enter the password and it is rejected. I also try using just \Anjow instead and the same happens. I try changing the username on the PC and creating a new account and it too is rejected. I have also tried using \Administrator, SERVER\Administrator, and SERVER\Anjow - none of them work. Does anyone know how I can get this PC connected, or what it is I'm doing wrong?
ตอบทั้งหมด
-
20 เมษายน 2555 16:24Try just "Anjow" without the "\". Also, if the server is part of a HomeGroup, disconnect it.
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
-
20 เมษายน 2555 16:38
Thanks for the response. I've had a go with that, but it has the same result. Does it matter that beneath it it still says "Domain: ANJOWGAMES"?
I'm not so familiar with Microsoft stuff - what do you mean part of a HomeGroup? When I go on system properties, then computer name, it tells me that the computer name is 'server' and the workgroup is 'WORKGROUP'. Is this what you mean?
-
20 เมษายน 2555 16:43
No, it's a Microsoft way of easily sharing files etc. If you don't know what it is then almost certainly you have not set it up!
Do you have a Domain Controller on your network? What are the IP addresses of Server and problem PC?
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
- แก้ไขโดย Phil Harrison 20 เมษายน 2555 16:46
-
20 เมษายน 2555 17:26
Presumably I'd only have a domain controller set up if I'd specifically done it too. If that's the case then I don't have one.
The IP of the Windows 7 PC is 192.168.0.2, the server 192.168.0.4 - the PC can ping the server fine, and can access its RDP directly and also using the connector software.
-
20 เมษายน 2555 18:00
When you say you try to "Connect", what do you mean? Can you access Shared Folders on the server via the icon that should have been created on your desktip when you installed the Connector software?
Which version of WHS are you using, the original or WHS2011?
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
-
20 เมษายน 2555 18:21This is after a reinstall of WHS original. I already had the connector software on the PC from before, but my server's board failed so I replaced it and reinstalled - I have not reinstalled the connector software - would you recommend that I do so? When I say connect, I mean by either putting \\SERVER\ in the address bar of explorer, or \\192.168.0.4\. It also shows up in the 'network' section of explorer.
-
20 เมษายน 2555 19:21ผู้ดูแล
Did you then grant that user access to one or more shares?... so I create a user on the server with that name, and with the same password. ...
I'm not on the WHS team, I just post a lot. :)
-
21 เมษายน 2555 9:26Yes, it has access to all of them.
-
21 เมษายน 2555 22:59Try creating a new User on your PC. Use the Console to create the same user on your Server and use the same password - give that User access to all folders using the Console. Log onto your PC as the new User and try connecting to your Server. Report back what happens.
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
-
22 เมษายน 2555 10:19I created a user called Test with a password, created the account on the server and gave it access to all folders and the same password. I then logged off on the PC, logged in as Test and tried to access the server by going into computer > network > double click 'SERVER'. It asked me for user/pass and I tried the one I was currently logged in as, and also \Test but both of them told me invalid credentials.
-
22 เมษายน 2555 14:34
http://technet.microsoft.com/en-us/library/user-accounts-overview.aspx
____________
BullDawg
In God We Trust
____________
<Anjow> wrote in message news:eda70c4d-c0f6-45e5-a2fc-a74afffbd9c0@communitybridge.codeplex.com...
:I created a user called Test with a password, created the account on the server and gave it access to all folders and the same password. I then logged off on the PC, logged in as Test and tried to access the server by going into computer > network > double click 'SERVER'. It asked me for user/pass and I tried the one I was currently logged in as, and also \Test but both of them told me invalid credentials.
:
BullDawg -
22 เมษายน 2555 22:13
Is this mentioned with reference to any part in particular? I understand the concept of user accounts, but am not sure why the credentials are being rejected at every step.http://technet.microsoft.com/en-us/library/user-accounts-overview.aspx
BullDawg -
22 เมษายน 2555 22:35I am sure that you do not want to hear this, but if it were me, I would do another re-installation, install all updates and make sure that you do any changes via the Console!
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
-
22 เมษายน 2555 22:46I'm a bit confused, all my changes have been done via the console. Sorry if that's not been clear from my explanations, but I've not done anything outside of the console other than install network drivers.
-
22 เมษายน 2555 23:19I was not suggesting you had, just reminding you not to do so! I can't think of another way of resolving the problem, although it could be a problem with your Client - you appear to be doing everything you need to and it should just work.
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
-
23 เมษายน 2555 0:53Get rid of connector software, I had many issues using this, I access all my folders without the software, set it up via rdp USING the console, you should see each share in explorar and just make a short cut. or one each computer point the folder to the share. The credintals are then managed at the server rather then the client.
-
23 เมษายน 2555 15:40Have you setup the "Allow remote access to your computer" on the home server?
- เสนอเป็นคำตอบโดย DigitalStick 23 เมษายน 2555 15:41
- แก้ไขโดย DigitalStick 23 เมษายน 2555 15:41
- ยกเลิกการนำเสนอเป็นคำตอบโดย Anjow 23 เมษายน 2555 17:31
-
23 เมษายน 2555 16:28
Have you setup the "Allow remote access to your computer" on the home server?
Remote Access and not being able to access shares are two different things!
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
-
23 เมษายน 2555 17:39If it's of any relevance, the connector software allows me to access the console fine but shows as "not connected to server" when I hover over it in the system tray. I have also tried to access the shares directly by putting \\SERVER\Videos in the address bar, but this has the same effect.
-
30 เมษายน 2555 8:33ผู้ดูแล
Hi,
did you verify, that time, date and time zone are identical on your server and the client PCs? If not, check and correct, if necessary.
Does name resolution work properly, so if you ping the server, does it resolve to the proper IP address within your LAN? What happens, if you enter nslookup on your client in a cmd prompt and enter the server name here?
Is any 3rd party security software involved, which contains firewall or network intrusion detection capabilities? If so, try to uninstall.
Do client or server have multiple network interface cards? If so, disable all besides the one, which is used for the current connection.
Best greetings from Germany
Olaf- เสนอเป็นคำตอบโดย Olaf EngelkeMVP, Moderator 21 พฤษภาคม 2555 14:20
-
17 พฤษภาคม 2555 6:59
I'm having exactly the same issue as Anjow - no share access (exactly the same symptoms) - grey home connector icon that still works, ping works, RDP works, etc.
I tried nslookup and got this response
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.0.1DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
