locked
Windows 2008 R2 Member Server - Netlogon 5719 - Windows 2003 Domain RRS feed

  • Question

  • I have a new Windows 2008 R2 SP1 Server that is a member server in a Windows 2003 domain. I have a second Windows 2008 R2 SP1 server that I just install as a DC and have transferred all the roles to it. Everything is working OK on the DCs and no other workstations are receiving any errors, this includes Windows XP and Windows 7 64bit systems. I have already done the spanning tree settings and porfast and already done all of the Broadcom suggestions. I have seen were everyone says that it's ok to ignore it if everything is working correctly which it is, other than this error. If I log off and on it doesn't show up again just after a reboot. I know that everyone is also saying the server is trying to connect faster than the network is up but I tried to change the group policy to wait for the network or add dependencies the netlog service. Does anyone have a solution to this???
    Friday, October 28, 2011 1:10 AM

Answers

All replies

  • Before we change any default GPO configs or any other AD configs, it will be helpful to first take a look at an ipconfig /all from the two DCs and from the member server in question, just to eliminate any basic config issues.

    Also, are there more than one Broadcom NIC being used that are teamed? If so, I would suggest to dissolve the team, disable one of the NICs, then restart. Sometimes teaming can be a cause of issues. Just an FYI, Microsoft doesn't support teaming NICs. Not that everyone has problems with them, and I have teaming configured on my own customer and my machines, but when there are possible network or other issues, one of the first things Microsoft PSS asks to do is dissolve the team and disable one of the NICs to help troubleshoot.

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Friday, October 28, 2011 2:44 AM
  •  

     They are not teamed and the second nic is disabled, here is the ipconfig for all 3: Fileserver Windows 2003 DC. Mainserver 2008 R2 DC, Exchange 2008 R2 Member Server with the 5719 error.
     
    Windows IP Configuration
     
       Host Name . . . . . . . . . . . . : Fileserver
        Primary Dns Suffix  . . . . . . . : domain.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : Yes
        DNS Suffix Search List. . . . . . : domain.local
     
    Ethernet adapter Local Area Connection:
     
       Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : 3Com Gigabit LOM (3C940)
        Physical Address. . . . . . . . . : 00-0C-6E-4E-C9-86
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.2
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.3
                                            192.168.1.2

     
    Windows IP Configuration
     
       Host Name . . . . . . . . . . . . : MAINSERVER
        Primary Dns Suffix  . . . . . . . : domain.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : domain.local
     
    Ethernet adapter:
     
       Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : BASP Adapter
        Physical Address. . . . . . . . . : 78-2B-CB-30-C7-A9
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : Yes
        Link-local IPv6 Address . . . . . : fe80::5104:42db:4e62:6701%16(Preferred)
        IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCPv6 IAID . . . . . . . . . . . : 393751499
        DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-30-FA-08-78-2B-CB-30-C7-A7
     
       DNS Servers . . . . . . . . . . . : 192.168.1.3
                                            192.168.1.2
        NetBIOS over Tcpip. . . . . . . . : Enabled
     
    Tunnel adapter isatap.{45447604-F431-44FF-9122-74E2C6E42A55}:
     
       Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
        Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : Yes
     
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
     
       Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : Yes
     
    Windows IP Configuration
     
       Host Name . . . . . . . . . . . . : Exchange
        Primary Dns Suffix  . . . . . . . : domain.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : domain.local
     
    Ethernet adapter:
     
       Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : BASP Adapter
        Physical Address. . . . . . . . . : 78-2B-CB-37-99-0A
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : Yes
        Link-local IPv6 Address . . . . . : fe80::2dda:9309:6925:431e%17(Preferred)
        IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCPv6 IAID . . . . . . . . . . . : 410528715
        DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-31-05-0B-78-2B-CB-37-99-08
     
       DNS Servers . . . . . . . . . . . : 192.168.1.3
                                            192.168.1.2
        NetBIOS over Tcpip. . . . . . . . : Enabled
     
    Tunnel adapter isatap.{0D653667-34B8-4891-B28C-31281C7BC4AE}:
     
       Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
        Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : Yes
     
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
     
       Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : Yes



    • Edited by Ryan Laurie Friday, October 28, 2011 3:10 AM
    Friday, October 28, 2011 2:55 AM
  • I saw your earlier post in the email notifiication indicating the NICs were teamed. Did you just dissolve them?

    On "FileServer" I see IP routing and WINS PRoxy enabled. Was this a RRAS server at one time? This is problematic on a DC and will definintely cause major problems on a domain controller, and will cause problems with authentication, logon and replication. Let's disable them.

     

    How to disable WINS Proxy:
    How to Disable NetBT (WINS) Proxy on Incoming Connections (How to disable WINS Proxy):
    http://support.microsoft.com/kb/319848

     

    How to disable IP Routing:
    Click on Start, Administrative Tools, click on "Routing and Remote Access"
    Right click Servername, choose Disable.

    Once you've disabled it, or even if Routing and Remote Access is already disabled, please navigate to the following registry location:
    HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Change value of IPEnableRouter from 1 to 0
    Reboot

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Friday, October 28, 2011 3:05 PM
  • Ok, I did what you said with the 2003 fileserver, rebooted  and replicated with the 2008 R2.  I have also had the nic teamed and not teamed but I'm still getting the error on my member server (exchange) when i reboot with the nic currently not teamed and the second nic disabled.
    Friday, October 28, 2011 5:49 PM
  • Oh, Exchange is in the picture? I may have missed that in this thread. Are both DCs a GC? If not, I would hihgly recommend that, especially for Exchange!

    What version of Exchange? If Exchange 2007, you may have to disable IPv6. More info depending on what version we're talking about here.

    Post the event log errors (Event ID# and Source Name in the event), and describe in more detail what the Exchange issues are, please, whether it's regarding Outlook, OWA, ActiveSync, Blackberry (is there a BES in the picture, too), etc -  please elaborate.


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Friday, October 28, 2011 5:56 PM
  • The Fileserver and Mainserver are DCs and GCs,the Exchange box doesn't have Exchange 2010 installed on it yet.  All I have done with it right now is attached it to the domain like a workstation.  I started receiving this error after that on reboots so I didn't want to install Exchange until I cleared up this issue. I know the Exchange name is confusing and I should have mentioned this.  Here is the event log error:

    Log Name:      System
    Source:        NETLOGON
    Date:          10/28/2011 1:10:08 PM
    Event ID:      5719
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Exchange.domain.local
    Description:
    This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following:
    There are currently no logon servers available to service the logon request.
    This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. 

    ADDITIONAL INFO
    If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="NETLOGON" />
        <EventID Qualifiers="0">5719</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-10-28T17:10:08.000000000Z" />
        <EventRecordID>5509</EventRecordID>
        <Channel>System</Channel>
        <Computer>Exchange.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DOMAIN</Data>
        <Data>%%1311</Data>
        <Binary>5E0000C0</Binary>
      </EventData>
    </Event>

    Friday, October 28, 2011 6:04 PM
  • Ahh, ok. Hence the subject title of this thread. Can you post an ipconfig /all of the server?

    Can you also post an updated ipconfig /all of the DCs?

    Is this a virtual or physical server?

    Clocks synched? If off by 5 minutes, Kerberos fails, causing 5719's. If virtualized, depending if HyperV or VMWare, it may be grabbing time off the host, which we need to disable, otherwise cause the same thing. (There's docs on this issue.) 

    Is an antivirus or antimalware app installed? Most AVs and AMs now have some sort of "network traffic protection" feature that can cause communications issues, such as blocking necessary ports that would negate a secure channel connection.

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Friday, October 28, 2011 10:31 PM
  • All of the servers are physical and all of the clocks are in sync also I have no nic's teamed. I don't have any AV on the 2 Windows 2008 R2 servers (Mainserver = DC, Exchange = Memberserver) as for the Fileserver it has Symantec Corporate Edition 10.1 and doesn't have any firewall or network traffic protection enabled or installed. Here is the ipconfig for all 3 servers. The Exchange server is the member server and is logging the Netlogon 5719 error on reboot and doesn't have any other sofware installed on it (NO EXCHANGE 2010) except for Windows 2008 R2 fully patch from Microsoft Updates.

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Fileserver
       Primary Dns Suffix  . . . . . . . : domain.local
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : 3Com Gigabit LOM (3C940)
       Physical Address. . . . . . . . . : 00-0C-6E-4E-C9-86
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.2
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.3
                                           192.168.1.2

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : MAINSERVER
       Primary Dns Suffix  . . . . . . . : domain.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client) #27
       Physical Address. . . . . . . . . : 78-2B-CB-30-C7-A9
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5104:42db:4e62:6701%16(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 393751499
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-30-FA-08-78-2B-CB-30-C7-A7

       DNS Servers . . . . . . . . . . . : 192.168.1.3
                                           192.168.1.2
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{45447604-F431-44FF-9122-74E2C6E42A55}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Exchange
       Primary Dns Suffix  . . . . . . . : domain.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client) #33
       Physical Address. . . . . . . . . : 78-2B-CB-37-99-08
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::a89c:c96f:d83c:709f%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 242756555
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-31-05-0B-78-2B-CB-37-99-08

       DNS Servers . . . . . . . . . . . : 192.168.1.3
                                           192.168.1.2
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{1AB8997C-62A3-4B1F-A593-9E358F8E39E2}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

     

    Saturday, October 29, 2011 4:21 AM
  • Looks pretty good. The only thing I would change on Fileserver is making itself as the first DNS entry, and Mainserver the second.

    Otherwise, all three look fine.

    But you're still getting 5719's?

    Last question that I can think of that may cause this - was this server cloned or a complete, fresh installation from scratch using the DVD?


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Monday, October 31, 2011 4:51 AM
  • Fresh copy from a DVD, but still getting the 5719 on the member server (Exchange). I've been looking at everything this weekend but still can't get this error to go away.
    Monday, October 31, 2011 5:05 AM
  • I can understand the frustrations. Let's disjoin the machine from the domain, set any Broadcom settings back to default, set any GPOs back to defaults, make sure after it's been disjoined that the computer object no longer exists. Force replication between the DCs (in Sites and Services), then rejoin the machine.

    See if this helps.


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Monday, October 31, 2011 5:12 AM
  • Already did this on Friday with no success.
    Monday, October 31, 2011 5:13 AM
  • I assume you put the GPOs and any NIC changes you made back to default, too? Is the machine in the Computers container, or has it been moved to an OU where this GPO was applied?

    Are there any other GPOs affecting it, possibly that apply to other machines or servers? If so, what sort of settings are in it? I know this can be a long answer, or possibly settings you can't divulge, but what I'm getting at is if there are any other factors affecting this member server? If there are domain based GPOs applying to all OUs, maybe put this in its own OU and block inheritance and/or use WMI filtering to prevent this machine from getting any policies to rule this part out.

    FYI, from my experience, setting this up is usually the easiest part of any deployment or Exchange migration (for example), that I've been tasked to do, and I've honestly never seen any problems with this part of it.

    Curious, do you have another network card to try, too?

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Monday, October 31, 2011 5:54 AM
  • Hi Ryan,

     

    Thanks for posting here.

     

    Have you also get any other error or warning rather than 5719? Just take look the suggestions from the articles below:

     

    Netlogon 5719 and the Disappearing Domain [Controller]

    http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx

     

    Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

    http://support.microsoft.com/kb/825036

     

    Thanks.


    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, October 31, 2011 9:02 AM
  • Good link, Tiger. If Imay share another one, and it applies to 2008/2008 R2:

    Event ID 5719 is logged when you start a computer on a domain, and the computer is running Windows Server 2003, Windows XP, or Windows 2000
    http://support.microsoft.com/kb/938449


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn
    Monday, October 31, 2011 2:32 PM