Need a little help from anyone out there. Posted this originally over
in
novell.support.os.server.lan.cards-drivers, but got no response.
Since the
problems are mostly with BM, I guess it really belongs here.

Just swapped out our switch to a gigabit unit and replaced the NICs in
both
our BM and SBS FileServer with Intel Pro/1000 MTs, driver version 7.5.
Both
servers are NW6.02, BM is 3.7SP1, and both servers show a good
connection at
1,000Mb/s full duplex. I went through all the settings in inetcfg on
both
servers again and couldn't see any errors. Ran DSRepair on both
servers. I
kept copies of all the original netinfo.cfg, tcpip.cfg, resolv.cfg,
hosts,
etc. files and can't see any glaring errors between the new and the
old.

The swap of cards went without problems, re-bound the original IP
addresses
to the new cards, etc., but now I see the following messages even
after
several reboots:

On the BM server:
8-5-2003 8:11:31 am: NBMALERT-1.05a-93001C [NBMAlert] Major
Error!
Could not open a connection to 192.168.0.1. IP address=100A8C0,
Code=-11

On the FileServer:
8-05-2003 8:55:05 am: SLP-2.5-0
SLP Activate DA FAILED for v2 DA "192.168.0.40" which returned
different address of "65.40.25.108".
This message recurs throughout the day about every 90 minutes.

The FileServer is on 192.168.0.1, the BM server on 192.168.0.40
(private)
and 65.40.25.108 (public). Internet access works fine except for
secure
sites behind the firewall, such as https://192.168.0.40:2200. If I
disable
access rules in BM I can then access internal https sites. I feel like
I
must have forgotten to enable something (NAT?) on the new private
board, but
I can't find what it is. Outside the firewall https sites work fine.
I
hope I don't have to re-create all my filter exceptions and/or rules
just
for a card swap with the same IP address.

I renamed the new board in the BM server to "PRIVATE" since it
replaced that
adapter. I did not swap out the "PUBLIC" card. On the FileServer, NW
named
the new card CE1000_1, so I left it at that. The card it replaced was

CE100_1. Could renaming the board back to the old name possibly fix
these
problems?

Could I possibly need to completely delete and recreate my SLP DA
again?
When I run DISPLAY SLP DAs on the BM server, I get:
SLP LOOPBACK : v2 : ACTIVE : DEFAULT : IANA : 7 : 0ms
192.168.0.40 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0ms

When I run DISPLAY SLP DAs on the FileServer I only get "192.168.0.40
: v? :
INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0ms", so it apparently can't
see
the running DA on the BM server.

And I really have no idea what is with the NBMALERT and an IP address
of
100A8C0. I get a feeling all these problems are related, but being anon-tech admin I'm not sure where to start. Any ideas would be
greatly
appreciated. TIA.

Greg Obermier
System Administrator