It seems that the SQL Server and the development computer belong to different AD domains that do not have a trust relationship. A trust relationship between domains is used so that you can log into computers with accounts from a trusted domain.
If you cannot add a trust relationship between the domains (you might need to ask your IT department for this), you can use SQL authentication to create accounts on the SQL Server that you can use in the connection string. A typical connection string looks like this:
Data Source=MyServer\MyInstance;Initial Catalog=MyDatabase;User Id=MySQLAccount;Password=MyPassword;
As you see from the sample above, a big advantage of using Windows authentication is that you do not have to store the password in the connection string. If using SQL authentication, it is strongly advised to encrypt the connection strings.
See this link on how to configure Mixed authentication mode on a SQL Server so that you can use SQL authentication.
There is a special account usually called sa. This is the sysadmin account that has all permissions. While a good account for testing authentication issues, it is advised to not use it in applications as a potential attacker could use this account to damage a SQL server installation heavily.
Sql Authentication. Specifically configure thesalogin and use it. - Soham Dasgupta