This is a problem that recently surfaced. We haven't had any prior problems like this. On newly formated Win XP machines, we are trying to establish ODBC connections to SQL Server Databases. As security at my company is very very lax, we only use one username and password company-wide.
After adding the System DSN, filling out the name of the connection and the SQL Server, we would typically accept all other default settings on the next screen:
:Windows NT Authentication
:Connect to SQL Server to obtain all other default settings for the additional configuration options.
:TCP/IP Selected in Client Configuration.
Everything else is default, with the exception of the default database selection.
It also shows that certain PCs with WinXP are having difficulties connecting to other PCs on the domain, with OS of 2000 and up. They are prompted for Username/Password, and when entered, the system does not accept them as valid.
I'm not sure why this is happening, but as our security is so lax, there shouldn't be any special usernames and passwords for individual machines and SQL Server connections. All other machines have no issues.
Please help!
After adding the System DSN, filling out the name of the connection and the SQL Server, we would typically accept all other default settings on the next screen:
:Windows NT Authentication
:Connect to SQL Server to obtain all other default settings for the additional configuration options.
:TCP/IP Selected in Client Configuration.
Everything else is default, with the exception of the default database selection.
It also shows that certain PCs with WinXP are having difficulties connecting to other PCs on the domain, with OS of 2000 and up. They are prompted for Username/Password, and when entered, the system does not accept them as valid.
I'm not sure why this is happening, but as our security is so lax, there shouldn't be any special usernames and passwords for individual machines and SQL Server connections. All other machines have no issues.
Please help!