Windows Server

Guest · Posted: Thu Nov 10, 2005 9:51 pm Post subject: Strange Communictor behavior

Ok, Here is my issue. I'm at a complete loss as to what the issue is. I
understand that it has to be a DNS issue, but all the DNS setup looks
correct. I am hoping that someone on here will be able to point me in
the right direction.

LCS STANDARD 2005 w/ SP1 installed on a Windows 2003 Standard server on
a windows 2000 domain. Exchange 2003 is also on this same server and
works fine. No DNS issues at all. DNS is setup for _sip and
_sipinternal. I'm only using TCP, no TLS is involved. Communicator is
set to auto configuration.

Communicator is installed on all machines as well as WM5.1. Employee's
try to log into LCS 2005, sometimes it logs in, sometimes it doesn't.
When it doesn't it says that the service isn't available. When tracing
is setup on that machine the following errors show up:

17:46:06.639 5F8:9E4 ERROR ::
OUTGOING_TRANSACTION::OnRequestSocketConnectComplete - connection
failed error 80ee001c
17:46:06.623 5F8:8A4 ERROR :: gethostbyname failed for host
sipinternal.internal.domain.com, error: 0x2afc

Now for the strange part. These errors only occur once in a while, and
only on different machines. Never all of them at the same time. If you
wait for 5 minutes and try to log in, it will log in fine, or if you do
an "IPCONFIG /FLUSHDNS" it logs in perfect and communications work
fine. The errors mentioned above do not occur in the log files. After a
while of having communicator connected a user will send a msg to
another user and it will pop up by the system tray, and you can read
the msg, but if you click on it or bring the window up, it is blank.
You will then not be able to send msg's to each other and a flush of
the DNS is required to get it working again.

This has been experienced on all machines in the domain, but not all at
once. It's as though they are pulling a wrong DNS or something. Even
though an NSLOOKUP shows the proper DNS entry for a auto login and the
server can be ping'ed by computer name with no problem.

The DNS has been double checked on both the DC and the LCS servers and
flushed multiple times on both as well. I just can't figure out what
the issue is with the DNS. Any direction of help would be greatly
appreciated. I have to get this working because we upgraded from
Exchange 2000 to 2003 and the IM is no longer integrated in exchange.
I'm just about ready to uninstall LCS and reinstall it in hopes that
will change something. I should mention that the LCS server was
installed when the IP was different x.x.x.62 and then change to
x.x.x.230 after the exchange server upgrade and move was finished.
Could this have a problem that would affect only the LCS server? As
mentioned before Exchange is working great. No problems with it at all.
And before anyone tells me not to put them on the same machine, unless
there are compatibility issues, there isn't a reason not to for me. The
hardware is more than capable and we only are using 17 users for LCS
and Exchange. So the workload is very very small.

TIA!
Tory

	Windows Server Forum Index -> Live Communications Server	All times are GMT
Page 1 of 1