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

Similar Messages

Printing issues when printing to Server 2008 R2 Print Server

We have a problem with netwok printing that encompasses many different areas and versions of Windows OSes so I will be posting this in a few different places.
Let me lay this out for you. We have a single Server 2008 R2 print server with 300 printers of various models. This print server has both 32 and 64-bit drivers installed for every printer. For the HP printers we are using the HP Universal Printing PCL 6
(version 61.94.3.37) and for the Ricoh printers we are using their PCL6 driver for universal printing version 3.5. All drivers run in Isolation mode and no printer gets published to AD.
We have a mix of Windows clients printing to these printers, both XP Pro and Windows 7 32 and 64-bit.
Now for the problems: The other day one Isolation host on the server went crazy, processing was hitting 100% and memory was fluctuating and growing a lot. After investigating a little that isolation host was having issues accessing the Ricoh Driver (which
was 3.4 at the time). In an attempt to resolve the issue we updated the driver to V. 3.5. This seemed to fix the isolation issues and things calmed down however this is the beginning of many other issues for the clients. Both Windows OS versions (XP and 7)
don't seem to be either downloading and installing the updated driver and/or doing so correctly. Clients are now experiencing extremely slow printing, applications such as Word, Outlook, Excel and others open slowly and it can take 2-3 minutes for print dialog
boxes to open. In all cases it seems that we have to have a tech delete the printer(s), delete the driver and then re-install the printer to make things better but for some reason, which is really unknown, this process doesn't work for every machine and on
some we can't even remove the old drivers at all without booting into SafeMode and doing it that way.
With all of that said, are there any suggestions as to why the clients aren't downloading and installing the drivers from the server correctly? How to avoid these issues when we need to upgrade the drivers on the server in the future? Most importantly right
now, are there any recommendations or scripts on how to force the deletions of the printer, driver, reset the print spoolers and then re-add the printers in a more automated fashion?
I have played with both wmic, pnputil and printuidll and am trying to put something together but without a set solution that will work consistently it becomes a lot more difficult.

We are experiencing a very similar issue.
Windows Server 2008 R2. Printers are deployed over group policy.
Clients range from Windows 7 to Windows 8. Citrix XenDesktop and XenApp environment also connects to these endpoints.
We have A wide assortment of HP printers, and Ricoh Printers.
For the ricoh's we have been historically using the PCL6 drivers for the individual device type (not universal print). Up till recently, it all was working fine, until about some time in the middle of june, when everything just seemed to go crazy.
The issue was resolved by moving off from the PCL 6 drivers and using the PCL5e driver counterparts on all of our ricoh printers.
It would crash XenDesktop applications, it would crash office applications.
The print spooler would lock up, even if the ricoh printers were not actually used, just as long as they were loaded.
Even after loading PCL5 on the servers, some of the clients would simply not download the PCL5 version of the driver from the print server. In order to resolve this, I have created the steps below. Be advised, this may possibly cause damage on your system.
We just found it worked great for us. Local printers will likely have to be manually reinstalled after this.
Directions
Stop the print spooler
Open C:\Windows\System32\Spool and delete the following
All files in SERVERS
All files in PRINTERS
All files in drivers
All files in prtprocs
Start the print spooler
Open a command prompt as administrator, and run the following command
Cscript C:\windows\system32\Printing_Admin_Scripts\en-US\prndrvr.vbs -x
This should further delete all print drivers.
Open a command prompt as a standard user (not administrator) and run the following
Gpupdate
Now wait. It takes a while, but the printers will slowly start to repopulate.
I am still not sure what is going on with the PCL6 drivers for ricoh, and why this issue is happening. I'm guessing it has something to do with the Ricoh auto update that is included in their pcl6 drivers. Maybe some sort of auto update happened recently.

Weird issue with Windows Server 2008 R2 Print Server

I have an issue with Windows 2008 R2 (VMWare Hosted) running Windows Print Server.
Prior to a small network change, the print server was working well, hosting about 80 different networked printers from various vendors.
We made a change (that we ended up rolling back) to the Client's DHCP Scope OPT 006 (DNS Servers). The DNS servers never quite worked right and broke AD authentication to different servers, and was just a mess.
After rolling back we are not able to keep the printers online. If we ping them from the print server, the printer(s) never wake up, when a print job is submitted. If we ping them from one of the access switches, they work fine (until they fall back asleep),
to prevent this, if we start a ping on the server AFTER waking them up from the Switch Ping, they stay online and no problems.
If we stop the ping, they fall back asleep at some point, and again, won't wake up without intervention/switch side ping.
Has anyone experienced anything like this? Any tips on how I could possibly resolve it?
Thanks in advance.

Hi,
According to your description, the issue seems to be that the printers can't keep online. Sounds like a power managerment issue. Why these printers fall into sleep? Have you consulted this issue with the manufacturer of these printers? Do these printers
fall into sleep if them lose the contact with printer server? Have you tried to reset the printers?
>>We made a change (that we ended up rolling back) to the Client's DHCP Scope OPT 006 (DNS Servers).
DNS client will cache the recently queried records. If the DNS server has replied with a wrong records, communication issues will occur. To clear the DNS cache on a Windows device, please run the command below:
ipconfig /flushdns
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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.

MacBooks can't resolve printer name when sending job to windows 2008 R2 print server.

So I am work at company in a windows server 2008 r2 and we have a windows 2008 r2 printer server. Our macbook pros are not on the domain so every time we print to the server we have to type in our credentials.
MacBooks can't resolve printer name when sending job to windows 2008 R2 print server while on wifi but works when hard wired. Any thoughts? The error message I receive is "invalid printer name". I've tried adding the printer through the advanced tab in the print and scan tab of system preferences. I add it buy smb://servername/printername.
When I tried to print on the wifi at my office I get "invalid printer name" in the print job status que.
We can just do direct printing but I would like to know if anyone has had this issue before and if you could point me in the right direction. Thanks!

I assume you aare using exchange when configuring the email notifications? What I would do is just use a normal IMAP & SMTP account such as Outlook.com or if you use a POP connector for exchange, one of those accounts' SMTP settings.
For example, I have a POP connector installed and my emails are hosted at 1and1. What I would do here is put my 1and1 SMTP settings in and use these, instead of using Exchange.
Let me know if this is possible.
Ed

Windows 8 can not connect RemoteApp on W2K12 RDS, but Windows 7 can connect. Why?

Hi!
Windows 8 can not connect RemoteApp (W2K12 RDS), but Windows 7 can connect. Why?
External and internal DNS name is different, the public Cert is mapped to RD Web Access and a RD GateWay Role.
The internal cert (issued by enterprise ca) is mapped to RD Connection Broker roles (SSO and Publishing).
These certifications also be installed on client computers (Personal and Trusted Root Certification Authorities).
The internal CA revocation list is publicated to a website and this web site is accessible from internet. Ports (3389,3391,443) forwarded to RDS server.
On windows 7 everything works fine, but Windows 8 can not connect to Remote Apps. Windows 8 can connect to RDS server via Remote Desktop Connection.
The error:
Thank you for your answers.

Check this thread ->
http://social.technet.microsoft.com/Forums/windowsserver/en-US/0c0d7c4a-e422-4a6c-99eb-66df26a1ffc6/rdp8-your-computer-cant-connect-to-the-remote-computer-because-an-error-occurred?forum=winserverTS
and this
http://support.microsoft.com/kb/2903333
HTH,
JB

Word 2010 - "Connecting to printer" message when opening documents at Server 2008 R2 Terminal server

Our users experience sometimes the message "connecting to printer" while they open a document in Word 2010 (32-bit) on our Server 2008 R2 Terminal Server. This is behavior
isn't consequent but random. The default printer in this environment is a Net2Printer-printerdriver (1.16) which redirects the print jobs (in PDF-format) to the local client's default printer. This feature works well. We don't want to change the default printer
because this is the right one to use by our users.
After a long seeking trip on the internet I've found the Microsoft hotfix KB974991 which can fix this issue for Word 2007. My question is, is this also usable for Word
2010 (32-bit) and if not, is there maybe another fix for the 2010 version available?
Any other suggestions or workarounds are welcome!

Hi,
Please change following options test if it works:
Ÿ
Print proofs quickly
Enable the Draft output option. When you use this option, the document prints with minimal formatting. Therefore, the document
may print faster. This option is ideal for printing proofs.
To enable the Draft output option, follow these steps.
Note Some printers may not support this option.
Start Word.
Click File, and then click
Word Options.
In the Word Options dialog box, click Advanced, and then scroll down to the Printing
section.
Click to select the Use draft quality check box, and then click OK.
Ÿ
Use the background printing option that best fits your requirements
When background printing is enabled, you can continue to work in Word while your document prints in the background. Background printing uses additional
memory, and your document may print more slowly.
When background printing is disabled, your document prints faster. However you cannot work in Word until the print job is completed. If you do not have
to continue to work in Word while your document prints, disable background printing to speed up printing.
To do this, follow these steps:
Start Word.
Click File, and then click
Word Options.
In the Word Options dialog box, click Advanced, and then scroll down to the Printing
section.
Click to clear the Print in background check box, and then click OK.
Best regards
William Zhou
TechNet Community Support

Installing Printers from Windows 2008 R2 printer server using the Cname

Am having issues installing printers on workstations from the windows 2008 R2 print server using the DNS names. the servername and Full qualified Name works fine.
l have tweaked the Registry and Disabled the StrictNameChecking but still getting an error. this is the message am getting...
Printer Installation Failed
You do not have enough privilege to complete the printer installation on the local machine.
I found this KB and did exactly what is in the KB but stilll....
lhttp://support.microsoft.com/kb/870911/en-us
need help

Hi.
I think I solved this yesterday. We got 1 printserver, with an alias, which we had this problem to connect to. I noticed that there is a difference between x86 and 64bits system entries in the registry...
When you are having a 64bit system, you must use REG_QWORD instead of REG_DWORD, REG_DWORD is only to be used in x86 system! See below.
Windows 2008 server R2 64-bit
HKLM\SYSTEM\CurrentControlSet\Control\Print
= ”DnsOnWire” = REG_QWORD Decimal = 1
(reg add hklm\system\currentcontrolset\control\print /v DnsOnWire /t REG_QWORD /d 1)
HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters
= DisableStrictNameChecking = REG_QWORD Decimal = 1
(reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v DisableStrictNameChecking /t REG_QWORD /d 1)
HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters\
REG_SZ = OptionalNames = “aliasname” (C-name record in DNS)
(reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v OptionalNames /t REG_SZ)
Windows 2008 server x86
HKLM\SYSTEM\CurrentControlSet\Control\Print = "DnsOnWire" = REG_DWORD Decimal = 1
(reg add hklm\system\currentcontrolset\control\print /v DnsOnWire /t REG_DWORD /d 1)
HKLM\SYSTEM\CurrentControlSet\services\Lanmanserver\Parameters = DisableStrictNameChecking = REG_DWORD Decimal = 1
(reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v DisableStrictNameChecking /t REG_DWORD /d 1)
HKLM\SYSTEM\CurrentControlSet\services\LanManServer\Parameters\ REG_SZ = OptionalNames = “aliasname”
(C-name record in DNS)
(reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v OptionalNames /t REG_SZ)
Don't forget to reboot your system after these changes!
Best Regards, Mats

IDM 7.2 under Windows Server 2008 R2 (SQL Server ): Which NTW ? Which JVM ?

Hello,
We are installing IDM 7.2 under Windows Server 2008 R2 using the database SQL Server 2008 R2.
1/ Which NetWeaver should we use to install the Java Application Server (NTW 7.3 or NTW 7.2)?
Using install guides 7.2rev8, we tried NTW 7.3 but it comes with JVM 1.6 that isn't supported, according to the PAM.
Should we install the AS Java with NTW 7.2 that comes with JVM 1.5 (JVM 1.5 being supported)?
2/ Has someone installed IDM 7.2 under Windows Server 2008 R2 (SQL Server)?
If yes, which NTW was used (7.2 or 7.3)? Which JVM was used (1.5 or 1.6)? Which JDBC drivers (1.2 or 3)?
Thanks a lot for your replies,
Regards.

{quote)For the Java RE are you using 32 or 64 bytes ?{quote)
C:\Users\Administrator>java -version
java version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
{quote)Which JDBC driver do you use (1.2 or 3.0) ?{quote)
{quote)In the IDM Identity Center, for the dispatchers option tools, how do you fill it ?
We are using :
Path to java exe: E:\usr\sap\ID1\J00\exe\sapjvm_6\bin\java.exe{quote)
C:\Program Files\Java\jre6\bin\java.exe
{quote)Path to jvm.dll: E:\usr\sap\ID1\J00\j2ee\JSPM\sapjvm\jre\bin\server\jvm.dll{quote)
C:\Program Files\Java\jre6\bin\server\jvm.dll
{quote)JDBC driver jar: D:\Microsoft SQL Server JDBC Driver 3.0\sqljdbc_3.0\enu\sqljdbc4.jar{quote)
C:\sqljdbc\sqljdbc4.jar
{quote)JDBC driver names: xxxxxxxxx (can you write us what you use){quote)
com.microsoft.sqlserver.jdbc.SQLServerDriver
{quote)CLASSPATH extension: D:\Microsoft SQL Server JDBC Driver 3.0\sqljdbc_3.0\enu\sqljdbc4.jar{quote)
No Classpath specified

Windows XP can't connect to the SMB service of the OS X 10.5.6

Hello,
I can't connect a XP to the SMB server OS X. The XP could see the other pc's in the network and when I share a folder I could access it from the mac enviroment. The 2 vista machines could access also without any problem. Only the XP is a problem...
http://files.image4you.tv/Clients//wimvanroy/Afbeelding%203.png
SMB server: Standalone Server
Workgroup: image4you
Access: NTLMv2&Kerberos
Guest is off (when on I could connect..)
Advanced:
Latin US 437
workgroup master browser selected (horizontal dash)
Homes: enabled
WINS off

I'm so mad I could spit. I've had similar problems for a year and a half, and have periodically gone back to beat my head on the wall with no effect...UNTIL TODAY! I found this little nugget:
"*After you turn on File Vault, you cannot log in to this user account for SMB file sharing or printer sharing.*"
The message appeared when I clicked Apple:System Preferences:Security:File Vault, then turned on File Vault and entered my password. ONLY THEN did the msg appear.
The reason I was turning on File Vault was that I had just started to use Time Machine on a mac on which I turned on File Vault 2 years ago. In order to use Time Machine I had to turn File Vault off and then back on in order to upgrade it to a newer version, compatible with Time Machine.
This warning does not appear anywhere in OSX Help and it is not in Apple's tech support FAQs. I did find it in the Tech Support section after I knew what I was searching for, but who would know to search for "File Vault AND smb" when their Win XP machine could not connect to the Mac. I sure didn't...
Apple needs to make this issue much more prominent or, even better, FIX IT. I'm sure thousands of users have the same situation as me - a PC at home or work and a portable Mac for every day use, keeping the Mac secured with File Vault. There must be some way to allow a manual login via smb, or something, which would then allow a PC user access to encrypted files on the Mac.
I hope this helps everyone! Someone! Anyone! Buehler!

Testing moving to new Windows Server 2008 R2 DHCP Server.

HI all,
I want to bring up a new DCHP server on an existing Windows Server 2008 R2 Domain Controller. The current DHCP server is a Windows 2003 Domain Controller. I have moved all the FSMO Roles to the new 2008 R2 domain controller
with the plan to eventually demote the 2003 server and take it off the network. I have the dhcp role installed on the new Windows Server 2008 R2 and have duplicated the exact settings (reservations, scope, etc.) from the old windows 2003 server
on the new 2008 R2 server. My plan was simply to disable the dhcp service on the old windows server 2003 and then authorize the new Windows Server 2008 R2 DHCP Server. However, after reading several articles, I understand that once you authorize
a new dhcp server, the old dhcp sever is unauthorized. I also read where several people had major issues with the new dhcp server not handing out IP Addresses even though the new dhcp server was authorized successfully. Since this is
a production network, I would like to employ the correct method to bring up the new dhcp server. Also, if there is a problem, is there an easy way to go back to the original dhcp server? Thanks for your help.
FD
Bob Andres

You can authorize multiple DHCP servers on a network.
You can activate and deactivate different scopes independently. So you can test DHCP functionality with a test scope.
Also, you can stop the old server in many ways that allow it to be online very rapidly: stop the dhcp server service, deactivate the scopes and yes even de-authorize the server.
My advice would be to built a test so you are confident (=very important) and not to fear the final onlining too much. DHCP is no rockets science. If you've replicated the configuration and are aware of possible IP Helper configurations on your routers/switches,
it should all work out fine.
MCP/MCSA/MCTS/MCITP

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.

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.

Windows Server 2008, IIS7, SQL Server 2005 - Will this work?

Hi,
Not super concerned about it being supported at this point, BUT, can I run/install CR XI SP2 on Windows Server 2008, IIS7, SQL Server 2005?
I've reference the System Requirement stuff and it was written before Server 2008 was released.
If it's possible, any help on what to install/not install would be great appreciated.
Thanks,
Mike

Try it. If it works great. As you are using ASP, your app must be using craxdrt.dll. This dll has been retired and no longer ships with CR 2008, so even when the next SP for CR 2008 releases, it will be of no use to you. If the ASP app does not work on the server, you may want to post your query to the Legacy Application Development SDKs forum:
SAP Crystal Reports - Legacy SDKs
and see if anyone can help.
Other than that, the only option will be to go to .NET once SP 1 releases for CR 2008, or use CR 10.5 which bundles with .NET 2008.
Ludek

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

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

Similar Messages

Maybe you are looking for