DNS name expired, Outlook on clients can't connect to exchange anymore

Dear forum people,
We have a pro account with dyndns that kept all the dns names in check. The credit card that paid for this had expired and that wiped the DNS names we had on there. After contacting the US customer service after alot of hastle, I got a salesman on the line
that promised us that if i resubscribed for the ProAccount with a new credit card he would fix this. So I renewed but ofc the DNS names never came back. Typical me being so naïve that a salesman would take care of us after we had paid.
Problem:
The Outlook on the laptops can't connect to the exchange server.
1. I get a message box from outlook saying:
"autodiscover.(DomainName).be - information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
GOOD - the security certificate is from a trusted certifying authority
GOOD - the security certificate date is valid
NOT GOOD - the name on the security certificate is invalid or does not match the name of the site"
+'disconnected'
Question:
I have no prior knowledge of Email mechanics but i'm pretty sure I just need to reinstate the correct dns name + settings of the dns name so the connection can be made again with the exchange server. Any suggestions where I should start finding out what
the settings should be like?
§1 I'm pretty sure the emails are routed over the website which is somewhere else
§2 I did not set up the DNS names myself
§3 I have an amature IT background

Hi,
Find a related KB for your reference:
http://support.microsoft.com/kb/2772058
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • External outlook clients can't connect to Exchange 2013

    Currently running server 2012 r2 and exchange 2013 sp1...
    Internally everything works fine, clients can also connect externally to owa/ecp. However when using an outlook client they are unable to connect. This is my first experience with exchange 2013 so I am at a loss. What steps should I be following to get this
    working properly? Or if anyone has some suggestions to get more information I can do that as well.
    Thanks! 
    Connecting from a mobile-phone using mail.mail.com works fine.
    We are using a self-signed certificate for testing purposes..

    Testing Outlook connectivity.
    The Outlook connectivity test failed.
    Additional Details
    Elapsed Time: 941 ms.
    Test Steps
    Testing RPC over HTTP connectivity to server mail.mail.com
    RPC over HTTP connectivity failed.
    Additional Details
    Elapsed Time: 941 ms.
    Test Steps
    Attempting to resolve the host name mail.mail.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: xxx.xxx.xx.x
    Elapsed Time: 535 ms.
    Testing TCP port 443 on host mail.mail.com to ensure it's listening and open.
    The port was opened successfully.
    Additional Details
    Elapsed Time: 176 ms.
    Testing the SSL certificate to make sure it's valid.
    The SSL certificate failed one or more certificate validation checks.
    Additional Details
    Elapsed Time: 229 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.mail.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=mail.mail.com, Issuer: CN=mail.mail.com.
    Elapsed Time: 154 ms.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name mail.mail.com was found in the Certificate Subject Common name.
    Elapsed Time: 0 ms.
    Certificate trust is being validated.
    Certificate trust validation failed.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.mail.com
    A certificate chain couldn't be constructed for the certificate.
    Tell me more about this issue and how to resolve it
    Additional Details
    The certificate chain didn't end in a trusted root. Root = CN=mail.mail.com
    Elapsed Time: 33 ms.

  • Outlook 2007 SP3 can't connect to Exchange 2013

    Outlok 2007 with latest hotfixes
    Freshly migrated mailboxes
    Gives the error 
    Can't open outlook-The set of folders cannot be opened
    Cert has internal FQDN name. Encryption is disabled
    Any pointers?

    Does the certificate have the server name?
    That was apparently the solution here:
    http://social.technet.microsoft.com/Forums/exchange/en-US/1ae67f48-d1ba-44b5-a3c7-4e9a5e955f3e/outlook-2007-cannot-connect-to-exchange-2013?forum=exchangesvrclients
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Outlook client can't connect in but OWA works

    You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option called Negotiate, which is recommended. As you follow this guide, you will set the ClientAuthenticationMethod (Internal and External if on Exchange 2013) to NTLM...

    Outlook client can't connect in configured outlook on workstation but OWA works.
    This topic first appeared in the Spiceworks Community

  • Some clients can't connect after 10.6.6 update - the see an error -43

    Hi There,
    I'm a designer so am not all that technical but have managed to setup and maintain OS X servers since 10.5.
    I've just updated the server to 10.6.6 and now some of our clients can't connect - they get the following error:
    "There was an error connecting to the server. Check the server name or IP address and try again.
    If you are unable to resolve the problem contact your system administrator."
    If I click OK to the error above on the client, I see another error which reads:
    "The operation cannot be completed because one or more required items cannot be found.
    (Error code -43)"
    I've restarted the server and the clients but no luck.
    The server is running the following services:
    - AFP
    - DNS
    - Firewall
    - NFS (although I don't remember setting this up - is this started with AFP?)
    - Open Directory
    I can ping the server and login via ARD so not sure why we see the first IP address error as mentioned above.
    Any help or suggestions would be most welcome.
    Regards
    Ben

    One question, is this when you hit "Connect to Server" or is this after you've established a connection and try to open/edit/save files?
    Here is some general advice:
    1) I assume your whole network is behind a router and that we are talking a small office environment (5-10 people) and not some large enterprise. If so the Firewall service can probably be disabled. As a matter of fact if your issue is that clients can't connect at all the firewall may actually be causing your problem.
    2) NFS can almost certainly be disabled. Its generally only used for two reasons 1) The netboot service needs it. 2) You support unix/bsd clients. I can see from your list of services that netboot isn't something you're doing and I doubt that as a designer you would have much use for unix/bsd systems.

  • OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

    hi ALL
    OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
    Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
    2 cas Servers
    first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
    Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
    please support
    thanks

    Hi,
    According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
    If I have misunderstand your concern, please do not hesitate to let me know.
    I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
    Please run following command to double check the database status:
    Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
    If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
    for further troubleshooting.
    Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
    Best Regards,
    Allen Wang

  • Windows XP SP3 and Outlook 2010 can't connect with Exchange 2010 or Exchange 2013

    XP+SP3+Outlook 2010 can't connect to Exchange 2010&2013 in the internal network without safe mode.

    Hi,
    Did you get any error messages?
    Do you have Outlook Anywhere and autodiscovery set up properly?
    Can you ping the Exchange server?
    Please use Test Email AutoConfiguration
    to test if the Autodiscover service is configured properly. See:
    https://hosting.intermedia.net/support/kb/default.asp?id=2150
    We can also use the remote connectivity analyzer to troubleshoot the issue:
    https://testconnectivity.microsoft.com/
    In addition, turn off your firewall and anti-virus to check the result.
    Hope this helps.
    Best Regards,
    Steve Fan
    TechNet Community Support

  • Mac10.x client can't connect to File Server on Windows2008 Failover Cluster

    Installation of a cluster was made according to the document "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster " http://technet.microsoft.com/en-us/library/cc731844.aspx.
    My Mac OS X 10.5.2 and Mac OS X 10.4.11 clients be able to connect to a non-cluster file server on a Windows 2008 (the File Services role) and also to old file cluster on a Windows 2003.
    Why Mac clients can't connect to Windows 2008 Failover Cluster?

    Are you running a firewall on the Macs. If yes does it work with out the firewall? If it works with out the firewall that means you will have to create a custom ipf rule which includes the both the physical an virtual IP addresses of your cluster.

  • How many clients can be connected to an Access Point

    Hi friend,
    I want to know how many clients can be connected in Cisco AP 1140.
    Best Regard,
    Marco.

    Hi,
    As Stephen mention the best answer is it depends.
    What you need to keep in mind is that wireless is halfduplex and a shared medium and due to this the bandwith will go down per client.
    http://www.cisco.com/en/US/products/hw/wireless/ps430/products_qanda_item09186a008009483e.shtml
    Q. How many clients can associate to the AP?
    A. The AP has the physical capacity to handle 2048 MAC  addresses, but, because the AP is a shared medium and acts as a wireless  hub, the performance of each user decreases as the number of users  increases on an individual AP. Ideally, not more than 24 clients can  associate with the AP because the throughput of the AP is reduced with  each client that associates to the AP.

  • What is required to Exchange integration work - (Can't connect to Exchange Web Server)?

    Hi guys,
    We have just 'beaten' our Lync installation until it decided to work with mobility, however the clients (IOS) complain that it "Can't connect to Exchange Web Server". Entirely possible its our own fault!
    My question is:
    What exactly do I need to configure to make this work?
    DNS records,
    Firewall rules,
    etc. 
    We are running:
    Exchange 2010 on-premise
    TMG 2010
    Cheers
    Dave
    Dave

    Hi Dave,
    The Lync 2010 mobile client for iPhone and iPad has a Meeting tab that lists meetings for the day from the Exchange calendar.
    The client uses simple Exchange Autodiscover processes to determine the location of the Exchange server of the user who is signed in. The SIP Uniform Resource Identifier (URI) of the user is used in the attempt to discover the Exchange Web Services (EWS) endpoint.
    However, if the user’s SIP URI and email address are different, the Autodiscover process will fail, the Meeting tab will be blank, and Exchange Unified Messaging (UM) voicemail in the Phone tab will not sync.
    For disjointed email and SIP URIs, the Lync 2010 mobile client for iPhone and iPad lets the user specify a different set of credentials for Exchange integration. For the Exchange Autodiscover process to work correctly, the necessary DNS records must be available.
    To confirm that Autodiscover is working, use Microsoft Remote Connectivity Analzyer at http://www.testexchangeconnectivity.com (http://www.testexchangeconnectivity.com/)
    In addition, please also refer to this document
    Lync 2010 Integration. Hope helps.
    Noya Liu
    TechNet Community Support

  • Lync 2010 iPhone - Can't connect to Exchange web server. you can try again later

    Hi there,
    I installed Lync 2010 mobility, and works fine, but iPhone users have a :
    Can't connect to Exchange web server.
    you can try again later
    Now does this have anything to do with it? And how do i fix it? I searched but nothing relevant

    Total server discovery time: 0.3 seconds
    Starting Lync server autodiscovery
    Please wait; this test may take several minutes to complete...
    Starting automatic discovery for secure (HTTPS) internal channel
    Server discovery has completed for https://lyncdiscoverinternal.contoso.com/.
    Automatic discovery results for https://lyncdiscoverinternal.contoso.com/
    Access Location                          : Internal
    SIP Server Internal Access               : server.contoso.com
    SIP Server External Access               : sip.contoso.com
    SIP Client Internal Access               : server.contoso.com
    SIP Client External Access               : sip.contoso.com
    Internal Auth broker service             : https://server.contoso.com/Reach/sip.svc
    External Auth broker service             : https://lync.contoso.com/Reach/sip.svc
    Internal Auto discover service           : https://server.contoso.com/Autodiscover/AutodiscoverService.svc/root
    External Auto discover service           : https://lync.contoso.com/Autodiscover/AutodiscoverService.svc/root
    Internal MCX service                     : https://lync.contoso.com/Mcx/McxService.svc
    External MCX service                     : https://lync.contoso.com/Mcx/McxService.svc
    Internal UCWA service                    : service URL is empty in the discovery response
    External UCWA service                    : service URL is empty in the discovery response
    Internal Webscheduler service            : service URL is empty in the discovery response
    External Webscheduler service            : service URL is empty in the discovery response
    Server discovery succeeded for secure (HTTPS) internal channel against URL https://lyncdiscoverinternal.contoso.com/
    Starting automatic discovery for unsecure (HTTP) internal channel
    Couldn't connect to URL http://lyncdiscoverinternal.contoso.com/[email protected] (HTTP status code Forbidden)
    Server discovery failed for unsecured internal channel against http://lyncdiscoverinternal.contoso.com/
    Starting automatic discovery for secure (HTTPS) external channel

  • Hello.....after updating to Yosemite, i can't get my exchange mail to work.  It keeps saying can't connect to exchange server and asks for my password.  My mail is still working fine on android phone and ipad2.  Can someone help?

    Hello....after updating to Yosemite my mail isn't working .  Keeps saying can't connect to exchange server and asking for password

    I am having this exact same problem with my gmail account. Hopefully someone will have a remedy.

  • My home wifi connection suddenly got cutoff, then my iPod can't connect to it anymore

    My home wifi connection suddenly got cutoff, then my iPod can't connect to it anymore whereas all other devices (Macbook, Blackberry, etc) has no problem connecting. After putting the password, the password is accepted but it keeps searching forever and refuse to connect!

    Does the iPod connect to other networks?
    Try the following that you have not yet done to rule out a software problem:                 
    - Reset the iOS device. Nothing will be lost
    Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Power off and then back on the router
    - Reset network settings: Settings>General>Reset>Reset Network Settings
    - iOS: Troubleshooting Wi-Fi networks and connections
    - iOS: Recommended settings for Wi-Fi routers and access points
    - Restore from backup. See:
    iOS: How to back up
    - Restore to factory settings/new iOS device.
    If still problem make an appointment at the Genius Bar of an Apple store since it appears you have a hardware problem.
    Apple Retail Store - Genius Bar

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

  • Windows 7 client can't connect to Server 2008 R2 Print Server VM (ESXi 5.5)

    I have an issue today that is driving me bonkers.
    I recently came on-board to a company in my area as the system administrator and this network has everything and the kitchen sink wrong with the network layout, probably the worst I've seen and I'm slowly but surely fixing it day by day.....
    Well today I decided I was going to spin up another VM from a template and make a Print Server, seems harmless right? --- I thought so too, added all of the printers to the server and did test pages, all was dandy, but then I tried to add the printers to
    clients and other server and the real fun has begun, I'm truly perplexed now...
    I added a VM to my esxi 5.5 cluster at work that is a 2008 R2 server with only print management on it. I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via
    DNS. I can test printers directly from the print server successfully printing out test pages however whenever I try to map printers you know from the directory in 'devices and printers' from any of the Windows 7 clients or any of the other 2003/2008 servers
    I get the classical "Windows cannot connect please check the network connection and make sure sure the printer is turned on". I disabled the windows firewall and I made the point to print GPO set to disabled and still no luck. Again I can print to
    all of the printers internally inside of the VM (so I know it communicating to all of the printers), I just can't connect to the printers listed in the directory on any of external desktop/client, it's like so annoying. spent about 6 hours until my brain just
    couldn't think anymore, was about to go BS on the VM.
    The only thing I can think of, as I was driving home, is that there is a GPO on one of the DC that has a desginated print server policy set. But prior to last week the forest leve was 2000 and now it's 2003. I just don't know Server 2000 enough to know if GPO's
    worked in the same way they do in 2003.
    Right now printers are connected to other servers in a ad hoc mentality it seems, there has never been a true print server.
    Anyone ever have this problem before?
    I'm truly puzzled...

    Hi Mid.Hudson-IT,
    Before we begin ,we should ensure we have configured the printer server correctly .
    Here is a link for reference of configuring the printer server .
    Print server role: Configuring a print server
    https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
    "I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
    From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
    If we can ping the print server from the client,we can ensure the connection to the printer server is good .
    Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
    If we cannot ping the print server ,we should troubleshoot the network issue firstly.
    We also can check the event viewer for more information to troubleshoot this issue .
    Best regards

Maybe you are looking for