Victor-
A couple additional things to add to Imelda's response. First off... just a
clarification on the support of SNA Server 4.0. SNA Server 4.0 has moved out
of it's mainstream support phase and is now in what we call extended
support. This means that we will no longer produce hotfixes for SNA Server
4.0 unless you have a special extended support contract. However, we do
still provide technical support over all our standard channels (newsgroup,
phone, etc..) for SNA Server 4.0. For more information on product
lifecycles, please visit the following page:
http://support.microsoft.com/default.aspx?scid=fh;[ln];lifecycle
As for the problem you are experiencing you need to understand the
difference between locating servers by name and locating by subdomain. When
you choose to locate servers by subdomain name the client will actually send
out broadcast messages with that subdomain name and establish a sponsor
connection to the first server that responds to the broadcast. With current
network infrastructures this can be problematic because most networks now do
not forward broadcasts to all segments by default. So, my guess is that
these new servers probably lie on a different network segment or behind a
different router which is not forwarding the broadcasts to the SNA Servers
in the subdomain. When you choose to locate a server by server name the
client will actually resolve that name to an IP address and connect directly
to the server thus avoiding the problems you are having with broadcast
messages.
So... you will probably either need to change your routers/switches/etc to
forward the broadcast messages or configure your clients to locate servers
by name rather than subdomain name.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Imelda Irby [MSFT]Victor,
first of all this version of SNA 4.0 is not suported any longer, unless you
have some kind of special contract...
However, based on the information below you might want to check the
dependancies for SNABASE and see if all of them are starting...
The SnaBase service cannot start until all dependency services have
completed initialization. The SnaBase service is designed to time out if
the dependency services do not start after 10 seconds. The Host Integration
Server 2000 Admin Client's SnaBase service is dependent upon the following
Workstation and NT LM Security Support Provider
If any of these other services do not start in a timely fashion, the
SnaBase service will not be able to start, and an event ID 590 may be
logged in the application event log.
The following Microsoft Knowledge Base article describes a registry
parameter that can be configured to increase SnaBase's default service
Thank you,
Imelda Irby, MCSE
Microsoft® HIS 2000/SNA Server Support Team
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS" with no
warranties, and confers no rights.