RE: Outlook trying to connect.......



Hi Chace

Thanks for your message.

I tried all those tests and they work perfect.

Anyhow I think I resolved my problems.

I had to change the protocol for Kerbersos to use TCPIP instead of UDP(MS
Article 244474). I believe my UDP packets were being fragmented through the
VPN. Also installed Security Update for Windows XP (KB913446) on the client.

I have tested this several times on different remote workstations and seems
to be working.

Thanks for your support.

Bye

Alfred


"chace zhang" wrote:

Hi Alfred,

Thank you for your reply.

Based on my research, this problem seems caused by DNS issue or Net Logon
issue. If this issue still persists.
I'd like to provide you with the following info for your reference:

Info 1. Check Net Logon service.

1. Click Start and click Run.
2. Type "services.msc" and click OK.
3. In the right pane, double-click Net Logon.
4. Make sure that the status is Automatic - Started.
5. Test whether the problem persists.

Please also refer to the following KB:

XADM: Error Message Received When You Start Exchange System Attendant
http://support.microsoft.com/default.aspx?scid=kb;en-us;299563

Info 2. DNS.

1. Click Start and click Run.
2. Type "cmd" and click OK.
3. Type "nslookup <domai controller name>" and hit Enter.
4. Can the name be resolved?

Please refer to the following KBs as well:

Event ID 1054 is logged in the application event log
http://support.microsoft.com/default.aspx?scid=kb;en-us;298656

Event ID 1054 Is Logged in the Application Event Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;324174

Info 3. Check Media Sense.

Please follow KB 239924 to diable Media Sense and check the issue again.

How to disable Media Sense for TCP/IP in Windows
http://support.microsoft.com/default.aspx?scid=kb;en-us;239924

In addition, since you mentioned this issue appeared after applying SP1, I
would like to explain Windows Server 2003 Service Pack 1 added a new RPC
element called multiple transfer syntax negotiation , The new element
provides a method for clients and servers to discover and negotiate their
capabilities during bind time instead of durind the first request in the
verification trailer. This new addition to the RPC protocol may not be
recognized by firewalls, routers or virtual private networks (VPN). If such
frames are not recognized, routers, firewalls, and VPN connections will
drop the new RPC bind request frames.Therefore any operation that requires
an RPC bind may now fail with RPC errors if the RPC caller is a Windows
Server 2003 Service Pack 1-based server.

899148Some firewalls may reject network traffic that originates from
Windows Server 2003 Service Pack 1-based computers
http://support.microsoft.com/default.aspx?scid=kb;en-us;899148


Hope this helps. Have a nice day!


Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.


.



Relevant Pages

  • RE: Connecting via RPC
    ... I understand that you encountered problem when trying RPC to your Exchange ... 825763 How to configure Internet access in Windows Small Business Server ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: login and email problems
    ... Please carefully check settings required in my previous post and post the ... Install the RPC ping utility on the client computer and then open a command ... Microsoft CSS Online Newsgroup Support ... Leave the Default Gateway of the internal NIC blank of the server box. ...
    (microsoft.public.windows.server.sbs)
  • Re: The Web site cannot be found - errors
    ... What is the server OS version? ... SBS 2003 or Windows 2003? ... setup and deployment newsgroup. ... this issue may occur if the web site is using ...
    (microsoft.public.windows.server.sbs)
  • Re: NTFRS
    ... The server holding the PDC role is down. ... Default-First-Site-Name\WIN2003 via RPC ... I have no Sysvol on the Windows 2003 server. ...
    (microsoft.public.win2000.active_directory)
  • RE: DFS & GPO Problems
    ... Thank you for posting in SBS newsgroup. ... DNS Server address is not configured correctly on the affected ... We can also try to disable the Windows Firewall on the problematic ...
    (microsoft.public.windows.server.sbs)