hello... and thank you in advance to anyone that can assist me with my
problem...

I'm running Outlook 2000 on XP connecting to an internal Exchange 2000
server...  When some of the workstations start up Outlook they get the
following error



"Your Microsoft Exchange Server is unavaliable

You can retry connecting to the server using the network,
or work off-line and connect using dial-up networking.

The network did not respond in a timely fashion to
determine the existance of an Exchange Server, you
may retry and continue waiting for a responds or work off-line"



If you select "retry", the Outlook client will always connect to the server
immediately afterwards

I've loaded every patch out there for XP, Outlook & Exchange... I've adjuste
d
the "Connection Timeout" to 60 seconds... My network utilization is under  3
%... So at this point I'm sort of at the end of my rope as what to do...

This has been an on going problem and it's become way beyond simply being a
thorn in my side... I've posted this on here several times... But never gott
en
a reply... If anyone could point me in the right direction I would be extrem
ely
greatful

[ Post a follow-up to this message ]

Welcome to my night mare.  I've been dealing with this issue for two days
now and I think I'm getting closer but the issue has not been resolved.

I realized (with some help) that the NetBIOS over TCP/IP had been disabled
both on the client and on the server.

Make sure that you're able to ping your server name and that when you ping
your server's IP address with the -a switch that the computer name is
returned.

Changed these settings but have not been able to reboot my server so I'm
still out because I don't want to disconnect the users that have been able
to get in.

I hope this helps.

Rafael

"KTyson9426" <ktyson9426@aol.com> wrote in message
news:20040210151200.19898.00001712@mb-m17.aol.com...
> hello... and thank you in advance to anyone that can assist me with my
> problem...
>
> I'm running Outlook 2000 on XP connecting to an internal Exchange 2000
> server...  When some of the workstations start up Outlook they get the
> following error
>
>
>
> "Your Microsoft Exchange Server is unavaliable
>
> You can retry connecting to the server using the network,
> or work off-line and connect using dial-up networking.
>
> The network did not respond in a timely fashion to
> determine the existance of an Exchange Server, you
> may retry and continue waiting for a responds or work off-line"
>
>
>
> If you select "retry", the Outlook client will always connect to the
server
> immediately afterwards
>
> I've loaded every patch out there for XP, Outlook & Exchange... I've
adjusted
> the "Connection Timeout" to 60 seconds... My network utilization is under
3
> %... So at this point I'm sort of at the end of my rope as what to do...
>
> This has been an on going problem and it's become way beyond simply being
a
> thorn in my side... I've posted this on here several times... But never
gotten
> a reply... If anyone could point me in the right direction I would be
extremely
> greatful
>
>

[ Post a follow-up to this message ]

It has nothing to do with BetBIOS overe TCP/IP.

Rafael wrote:

> Welcome to my night mare.  I've been dealing with this issue for two days
> now and I think I'm getting closer but the issue has not been resolved.
>
> I realized (with some help) that the NetBIOS over TCP/IP had been disabled
> both on the client and on the server.
>
> Make sure that you're able to ping your server name and that when you ping
> your server's IP address with the -a switch that the computer name is
> returned.
>
> Changed these settings but have not been able to reboot my server so I'm
> still out because I don't want to disconnect the users that have been able
> to get in.
>
> I hope this helps.
>
> Rafael
>
> "KTyson9426" <ktyson9426@aol.com> wrote in message
> news:20040210151200.19898.00001712@mb-m17.aol.com... 
> server 
> adjusted 
> 3 
> a 
> gotten 
> extremely 

[ Post a follow-up to this message ]

This is name resolution problem
http://support.microsoft.com/defaul...kb;en-us;155048
http://support.microsoft.com/defaul...kb;en-us;136516

KTyson9426 wrote:

> hello... and thank you in advance to anyone that can assist me with my
> problem...
>
> I'm running Outlook 2000 on XP connecting to an internal Exchange 2000
> server...  When some of the workstations start up Outlook they get the
> following error
>
> "Your Microsoft Exchange Server is unavaliable
>
> You can retry connecting to the server using the network,
> or work off-line and connect using dial-up networking.
>
> The network did not respond in a timely fashion to
> determine the existance of an Exchange Server, you
> may retry and continue waiting for a responds or work off-line"
>
> If you select "retry", the Outlook client will always connect to the serve
r
> immediately afterwards
>
> I've loaded every patch out there for XP, Outlook & Exchange... I've adjus
ted
> the "Connection Timeout" to 60 seconds... My network utilization is under 
 3
> %... So at this point I'm sort of at the end of my rope as what to do...
>
> This has been an on going problem and it's become way beyond simply being 
a
> thorn in my side... I've posted this on here several times... But never go
tten
> a reply... If anyone could point me in the right direction I would be extr
emely
> greatful

[ Post a follow-up to this message ]

You might try adding your exchsrvr  info (IP/NAME) to the local host table.

quote:
Originally posted by Kirill S. Palagin 
This is name resolution problem
http://support.microsoft.com/defaul...kb;en-us;155048
http://support.microsoft.com/defaul...kb;en-us;136516

KTyson9426 wrote:

> hello... and thank you in advance to anyone that can assist me with my
> problem...
>
> I'm running Outlook 2000 on XP connecting to an internal Exchange 2000
> server...  When some of the workstations start up Outlook they get the
> following error
>
> "Your Microsoft Exchange Server is unavaliable
>
> You can retry connecting to the server using the network,
> or work off-line and connect using dial-up networking.
>
> The network did not respond in a timely fashion to
> determine the existance of an Exchange Server, you
> may retry and continue waiting for a responds or work off-line"
>
> If you select "retry", the Outlook client will always connect to the serve
r
> immediately afterwards
>
> I've loaded every patch out there for XP, Outlook & Exchange... I've adjus
ted
> the "Connection Timeout" to 60 seconds... My network utilization is under 
 3
> %... So at this point I'm sort of at the end of my rope as what to do...
>
> This has been an on going problem and it's become way beyond simply being 
a
> thorn in my side... I've posted this on here several times... But never go
tten
> a reply... If anyone could point me in the right direction I would be extr
emely
> greatful 

[ Post a follow-up to this message ]