none
cannot connect client to sbs 2011

    Question

  • hi,

    i have a sbs 2011 and 6 clients (some with win7, some with xp). The server is running for about 1.5 year without any problems.

    But today the following problem occurred. I tried to add an additional client (i tried with xp and afterwards with win7 too), but instead of getting the 'welcome to domain...' message, i just got the error: 'Internal Error'. Then i tried to use the clientadvisor to connect to the network, but it failed too (with the same error).

    Then i checked if the dns works correctly, but i could not figure out any problems (i also cleared the cache). The dns entries on the clients are correct (dhcp and dns server = ip of my sbs).

    I also checked my router, if the dhcp has enabled itself (or something like that), but it was also disabled.

    I hope somebody can help, because i really have no idea :)

    best regards

    thomas
    Friday, October 04, 2013 10:04 PM

Answers

  • Hi:

    Are you trying this with http://connect?

    Can you give us the exact error message that appears when you attempt to join the pc to the domain?

    Dose the computer receive an ip from the SBS?  The pc should be the exact numbers as the SBS except for the last number in the ip address.  If in doubt, post up the results of this command:  ipconfig /all > c:\iptest.txt from both the server and a station.  Don't change anything and tell us which is which.


    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

    Saturday, October 05, 2013 12:38 AM
    Moderator
  • just this only one error? find {FD654956-B628-4ABF-8EA5-A194E7713849}...check?...

    no good ideal...commonly 1018 errors not good, it does in fact indicate a hardware problem.

    http://technet.microsoft.com/en-us/library/hh343919(v=EXCHG.140).aspx

    http://support.microsoft.com/kb/314917/en-us

    http://technet.microsoft.com/en-us/library/bb218731(v=EXCHG.80).aspx

    Best,

    Howtodo

    Monday, October 07, 2013 5:06 PM

All replies

  • Hi:

    Are you trying this with http://connect?

    Can you give us the exact error message that appears when you attempt to join the pc to the domain?

    Dose the computer receive an ip from the SBS?  The pc should be the exact numbers as the SBS except for the last number in the ip address.  If in doubt, post up the results of this command:  ipconfig /all > c:\iptest.txt from both the server and a station.  Don't change anything and tell us which is which.


    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

    Saturday, October 05, 2013 12:38 AM
    Moderator
  • hi,

    at first, thank you for the fast reply.

    yeah, I also tried to connect with http://connect, but without success. I made a screenshot of the exact error message, when i tried to connect with http://connect:

    http://imageshack.us/a/img7/668/47t1.png

    I have installed the sbs 2011 in german, so I added a translation to the screenshot.

    The ipconfig output of the server:

    Windows-IP-Konfiguration

       Hostname  . . . . . . . . . . . . : MYSERVER
       Prim„res DNS-Suffix . . . . . . . : ORION.local
       Knotentyp . . . . . . . . . . . . : Hybrid
       IP-Routing aktiviert  . . . . . . : Ja
       WINS-Proxy aktiviert  . . . . . . : Nein
       DNS-Suffixsuchliste . . . . . . . : orion.local

    PPP-Adapter RAS (Dial In) Interface:

       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : RAS (Dial In) Interface
       Physikalische Adresse . . . . . . :
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja
       IPv4-Adresse  . . . . . . . . . . : 10.0.0.16(Bevorzugt)
       Subnetzmaske  . . . . . . . . . . : 255.255.255.255
       Standardgateway . . . . . . . . . :
       NetBIOS ber TCP/IP . . . . . . . : Aktiviert

    Ethernet-Adapter LAN-Verbindung:

       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
       Physikalische Adresse . . . . . . : 00-1A-64-99-C5-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja
       Verbindungslokale IPv6-Adresse  . : fe80::a18d:b771:1a06:9641%11(Bevorzugt)
       Verbindungslokale IPv6-Adresse  . : fe80::d770:7fa8:43a4:2cb%11(Bevorzugt)
       IPv4-Adresse  . . . . . . . . . . : 10.0.0.10(Bevorzugt)
       Subnetzmaske  . . . . . . . . . . : 255.255.255.0
       Standardgateway . . . . . . . . . : 10.0.0.1
       DHCPv6-IAID . . . . . . . . . . . : 234887780
       DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-16-FF-D3-31-00-1A-64-99-C5-E0
       DNS-Server  . . . . . . . . . . . : fe80::d770:7fa8:43a4:2cb%11
                                           10.0.0.10
       NetBIOS ber TCP/IP . . . . . . . : Aktiviert

    Tunneladapter isatap.{7C715D72-0EF2-481C-97B6-D4119F735204}:

       Medienstatus. . . . . . . . . . . : Medium getrennt
       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
       Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja

    Tunneladapter isatap.{6E06F030-7526-11D2-BAF4-00600815A4BD}:

       Medienstatus. . . . . . . . . . . : Medium getrennt
       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
       Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja

    Tunneladapter LAN-Verbindung* 12:

       Medienstatus. . . . . . . . . . . : Medium getrennt
       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja

    Tunneladapter LAN-Verbindung* 2:

       Medienstatus. . . . . . . . . . . : Medium getrennt
       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3
       Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja

    ipconfig output of the client (currently i use a hyper-v virtual machine to connect, but i get the same errors with the "real pc")

    Windows-IP-Konfiguration

       Hostname  . . . . . . . . . . . . : TESTVIRTUAL
       Prim„res DNS-Suffix . . . . . . . : ORION.LOCAL
       Knotentyp . . . . . . . . . . . . : Hybrid
       IP-Routing aktiviert  . . . . . . : Nein
       WINS-Proxy aktiviert  . . . . . . : Nein
       DNS-Suffixsuchliste . . . . . . . : ORION.LOCAL

    Ethernet-Adapter LAN-Verbindung:

       Verbindungsspezifisches DNS-Suffix: orion.local
       Beschreibung. . . . . . . . . . . : Netzwerkkarte fr Microsoft Virtual Machine-Bus
       Physikalische Adresse . . . . . . : 00-15-5D-00-36-03
       DHCP aktiviert. . . . . . . . . . : Ja
       Autokonfiguration aktiviert . . . : Ja
       Verbindungslokale IPv6-Adresse  . : fe80::352f:fe1a:d3a1:dba3%11(Bevorzugt)
       IPv4-Adresse  . . . . . . . . . . : 10.0.0.29(Bevorzugt)
       Subnetzmaske  . . . . . . . . . . : 255.255.255.0
       Lease erhalten. . . . . . . . . . : Samstag, 05. Oktober 2013 10:18:20
       Lease l„uft ab. . . . . . . . . . : Sonntag, 13. Oktober 2013 10:18:21
       Standardgateway . . . . . . . . . : 10.0.0.1
       DHCP-Server . . . . . . . . . . . : 10.0.0.10
       DHCPv6-IAID . . . . . . . . . . . : 234886493
       DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-FE-2D-68-00-15-5D-00-36-03
       DNS-Server  . . . . . . . . . . . : 10.0.0.10
       NetBIOS ber TCP/IP . . . . . . . : Aktiviert

    Tunneladapter isatap.orion.local:

       Medienstatus. . . . . . . . . . . : Medium getrennt
       Verbindungsspezifisches DNS-Suffix: orion.local
       Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
       Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja

    Tunneladapter LAN-Verbindung* 4:

       Medienstatus. . . . . . . . . . . : Medium getrennt
       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja

    best regards

    thomas

    Saturday, October 05, 2013 8:40 AM
  • The IP looks ok.  But the DNS suffix for both is the same, implying the station has already joined the domain.

    On the SBS, have you run the Fix My Network wizard and the SBS BPA?  For the SBS BPA you can get it at www.sbsbpa.com.  Run the BPA and fix anything it finds.

    Verify that the new clients meet all the requirements.  I have seen systems, mostly XP, that needed dot net 4 installed.  Normally in the same subnet the server will push it, but in remote or different subnets it probably will not.


    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

    Saturday, October 05, 2013 12:05 PM
    Moderator
  • i have run the fix my network wizard, but this tool just found not opened router ports.

    der sbs bpa did not found any errors.

    i have also installed .net 4 on the windows 7 client, i tried to connect lately, but without success.

    Saturday, October 05, 2013 6:44 PM
  • Ok, then on the SBS there are a series of log files.  Look in this folder:

    C:\Program Files\Windows Small Business Server\Logs.

    And check this log file:  CopyConnectComputer.log  If you have tried multiple times it can get pretty long, so you might want to rename it and get a fresh log.  There should be a clue there.  Also look in the event logs on both systems for clues.  You can post up the errors if you have any questions.  for the log, tell us which log file and give the error part, for events, the event id and source.


    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

    Saturday, October 05, 2013 9:51 PM
    Moderator
  • thank you very much for the hints, maybe i'm the trouble on the track...

    after another try to connect my client i checked the event log of the SBS. At first I renamed the CopyConnectComputer.log and found out, that the server did not reach the step, where the log entry is created.

    In the event log I found the folling entry, that fits the time span, when i tried to connect.

    The source of the error is "ActiveDirectory_DomainService"

    The Event-ID is 2008.

    The Log Entry:

    Internal error: The security descriptor propagation task encountered an error while processing the following object. The propagation of security descriptors may not be possible until the problem is corrected.
     
    Object:
    CN=Machine,CN={FD654956-B628-4ABF-8EA5-A194E7713849},CN=Policies,CN=System,DC=orion,DC=local
     
    Additional Data
    Error value:
    -1018 JET_errReadVerifyFailure, Checksum error on a database page
    Internal ID:
    2070b26

    Saturday, October 05, 2013 10:46 PM
  • just this only one error? find {FD654956-B628-4ABF-8EA5-A194E7713849}...check?...

    no good ideal...commonly 1018 errors not good, it does in fact indicate a hardware problem.

    http://technet.microsoft.com/en-us/library/hh343919(v=EXCHG.140).aspx

    http://support.microsoft.com/kb/314917/en-us

    http://technet.microsoft.com/en-us/library/bb218731(v=EXCHG.80).aspx

    Best,

    Howtodo

    Monday, October 07, 2013 5:06 PM