Login failed for user 'COMPUTERNAME\\Guest'.

I'm testing my winforms application, trying to connect to it via a remote computer, and it has problems, giving me the message above.

A little background:

I have written this winforms application so it is possible to change the database at runtime.

It works flawlessly when using it locally (mostly tested on a vista machine, with SQL Server 2005 enterprise version).

Have just installed it on a win xp machien, running SQL Server express. I can connect to this database when our application is installed on the XP machien. But when the application is installed on another machine on the network, I get the message when I try to read a table "Login failed for user 'COMPUTERNAME\\Guest'." (COMPUTERNAME is the name of the machine the sql express server resides on).

I am quite confident the username and password I have entered when switching databases is correct (username is 'sa'). I am able to connect to the sqlexpress database from the network (tested it with MS SQL management Studio).

As far as I can tell, the code I'm using to change databases is this:

                    NetTiersProvider provider = DecEzy.Data.SqlClient.Utils.AddDataProvider(connName, connString);

                    //change provider to be current data provider
                    ConnectionScope.Current.DataProvider = provider;

Any assistance would be appreciated.

Please, check you connection string and look for Windows Authentication... it should be something like: "Integrated Security=SSPI".

You should not have that in you connection string, if you do, update the connection string to use login and password.

That would be my first guess.

Hello,

Could you double check you have followed the steps outlined in this document to enable remote SQL Express connections.

I would also set the connection string in the web.config for .netTiers. This would allow you to check to make sure this connection works without dynamically adding the new dataprovider.

Thanks

-Blake Niemyjski

Thanks vbandrade - that was spot on.

blake - your suggestion was close. I was having those problems earlier on, but found the very same website you suggested (it ended up being the firewall)

fweeee:

Thanks vbandrade - that was spot on.

That's why I'm not humble enough... haha

vbandrade:

fweeee:

Thanks vbandrade - that was spot on.

yay!

That's why I'm not humble enough... haha

 

LOL