MRxSMB event

  • Thread starter Thread starter mash
  • Start date Start date
M

mash

hi
i am getting this event logged on my client pc's when ever
i try to do a ODBC connection to my SQL server.
i suspect this is something to do with DNS or DHCP

Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 3034
Date: 12/30/2003
Time: 12:40:23 PM
User: N/A
Computer: tony
Description:
The redirector was unable to initialize security context
or query context attributes.

the ODBC connection fails with the following error
Connection failed:
Sql state :'01000'
sql server error : 1396
[Microsoft][ODBC SQL server driver][named pipes]
connectionopen
(createfile())
connection failed:
SQL state:'08001'
SQL server error:1396
[Microsoft][ODBC SQL server driver]Client unable to
establish connection

i've tried some sugesstions from KB
1)synchronized the clients clock with the DC
2)disconnect the client from the domain and rejoin the
domain
3)delete the clients ip lease from DHCP and get a new lease
4) delete the clients host record from DNS and allow it to
automatically create one
5)delete the clients computer account from the domain and
recreate it.

on all of the above instances the problem gets fixed but
when the client is restarted same thing happens again

need help
thanks in advance
 
Hey Mash,
Are you saying that this error message gets logged everytime you reboot,
or that the ODBC connection doesn't work after you reboot?

In anycase, can you verify that you can access a share on the SQL server
when the problem is occuring. Also have you tried to make the ODBC
connection to use TCPIP instead of Named Pipes. The MRXSMB error is a
Named Pipes connection (Hence SMB, file sharing type connection) were TCPIP
uses a different method.

Thank you,

Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
 
alan
this error message gets logged whenever i try to login
through by OBDC,
when this problem is occuring one client i can acess the
DB throug ODBC from another client.
this is a random issue some clients work for couple of
days and quit and it fixes itself after couple of days.
i tried TCP/IP but no luck

thanks for your reply
 
Back
Top