Connection to Lan fails and locks server

Morning,
We have two nodes in a sql cluster. The "Lan" connection on one of the
servers fails at different times and I can't track down the problem and I am
not sure where to start.
I have changed NIC's Cables, Switches and still no luck..
Any suggestions where to start would be appreciated.
Thanks
Firmware? BIOS? Drivers? Called the vendors?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"James" <James@.discussions.microsoft.com> wrote in message
news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I
> am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks
|||Actually we had a DELL rep come out and set this up because we did not want
to mess with the SAN LUN's. He couldn't figure it out either. I will take a
look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
I noticed earlier that Network DTC was not installed on both servers so I
installed that see if maybe that will make a difference.
"Rodney R. Fournier [MVP]" wrote:

> Firmware? BIOS? Drivers? Called the vendors?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "James" <James@.discussions.microsoft.com> wrote in message
> news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
>
>
|||"James" <James@.discussions.microsoft.com> wrote in message
news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> Actually we had a DELL rep come out and set this up because we did not
want
> to mess with the SAN LUN's. He couldn't figure it out either. I will
take a
> look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
>
To ask the obvious... SP3a installed?
[vbcol=seagreen]
> I noticed earlier that Network DTC was not installed on both servers so I
> installed that see if maybe that will make a difference.
> "Rodney R. Fournier [MVP]" wrote:
the[vbcol=seagreen]
and I[vbcol=seagreen]
|||SP3 A is installed. Server failed again after 3 day. Network cards pass all
test? I will post some logs see if anyone has seen it before.
"Greg D. Moore (Strider)" wrote:

> "James" <James@.discussions.microsoft.com> wrote in message
> news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> want
> take a
> To ask the obvious... SP3a installed?
>
> the
> and I
>
>
|||Ok Here is the Cluster Log as soon as it fails I cannot figure this out. We
have had this problem for 3 weeks now, the amount of time it takes to fail
varies. Any help would be appreciated.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Reporting connectivity
to leader for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
completed successfully for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
worker thread finished.
000003c0.00000804::2004/12/30-14:53:46.531 INFO [GUM] s_GumUpdateNode:
dispatching seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:46.531 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is unreachable (node: Server1, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 is unreachable (node: Server2, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is down.
000003c0.00000804::2004/12/30-14:53:46.547 INFO [GUM] s_GumUpdateNode:
completed update seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:50.405 INFO [NM] Received request to get
online address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Found address
10.40.0.91 for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Received request to get
ping address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Received request to
ping targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging targets for
interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging host 10.40.0.1
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Ping of host 10.40.0.1
failed.
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Pinging host 10.40.0.182
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Ping of host
10.40.0.182 failed.
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Pinging host 10.40.0.2
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Ping of host 10.40.0.2
failed.
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Pinging host 10.40.0.7
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Ping of host 10.40.0.7
failed.
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Pinging host 10.40.0.39
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Ping of host 10.40.0.39
failed.
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Finished pinging
targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
dispatching seq 8885type 2 context 15
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is up (node: Server1, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 failed (node: Server2, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is up.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
completed update seq 8885type 2 context 15
"James" wrote:

> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks

'Connection terminated' errors in C/S application...

Client workstations getting 'conection terminated' message through the client
app.
Happens sporadically and we can't seem to make it happen. Sometimes the
users get error messages from SQL Srvr and sometimes just the 'con term'
message. I've checked the switch, the wire, the patch level, the clients
(2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
Have an open case w/microsoft for over a month! No help... Updated mdac,
jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
Have done limited net monitoring (through MS worthless net monitor prog,
doing ethereal next) and can't come up with any definitive 'ah hah' and alas
a fix.
Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
Clients are 98se, 2k, XP Pro.
Server 2003 SBS SP1 throughout
SQL Server 2000 SP3a
Hi
I assume there is no information in the Windows Event log or SQL Server log
to help you?
Have you tried running the client on the server (with and without shared
memory)?
You may want to try setting up a separate (small) test environment to see if
it still happens with other hardware on a standalone network.
John
"drkc" wrote:

> Client workstations getting 'conection terminated' message through the client
> app.
> Happens sporadically and we can't seem to make it happen. Sometimes the
> users get error messages from SQL Srvr and sometimes just the 'con term'
> message. I've checked the switch, the wire, the patch level, the clients
> (2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
> Have an open case w/microsoft for over a month! No help... Updated mdac,
> jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
> Have done limited net monitoring (through MS worthless net monitor prog,
> doing ethereal next) and can't come up with any definitive 'ah hah' and alas
> a fix.
> Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
> up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
> Clients are 98se, 2k, XP Pro.
> Server 2003 SBS SP1 throughout
> SQL Server 2000 SP3a
>

Connection problem with NT4

Ive installed SQL2000 in a NT4-SP6 server, but I cant connect from another machine.
I receive the following msg in Query analizer : "sql server does not exists or access denied"
Ive tried both authentications methods, created alias with IP and server name but nothing works.

If I use query analizer locally I can connect using the server name, but cant if use the ip.

Please, save me :)

thanks in advanceHi Felipe,

I faced a similiar problem when using a Business-Intelligence Client
to connect from a NT-Client to our cube located on a XP-PC with
MS SQL and MS OLAP.

I tried realy everthing:
At the end the following worked.

I added every user, who wants to connect locally(!) as an account.
I added a role to the MS OLAP cube and added the new user to this
role.

Hint:
These users must be domain-users
(and in our case local users too )

hth

Michael|||thanks for your time Michael, but I cant connect with "sa"