Hi guys I hope you can help
Monday morning is fast approaching and I have a dillema.
New server with new domain went online today - 2003 standard on two servers in one domain. all machines in the office are members of this domain. SQL server is running on one server and AD/DC etc running on the other. All good in house.
We also have this old terminal server machine serving up our app to remote users (this machine will be upgraded in a couple of weeks). It is on its own domain and manages its own AD/DC etc services for terminal server.
Because the terminal server and the sql server are now on different domains - my client applications hosted on terminal server can no longer connect to the sql server using ODBC.
I can ping the sql server from TS machine as well as create network drives to other shared resources, but ODBC will not go.
HELP
Monday morning is fast approaching and I have a dillema.
New server with new domain went online today - 2003 standard on two servers in one domain. all machines in the office are members of this domain. SQL server is running on one server and AD/DC etc running on the other. All good in house.
We also have this old terminal server machine serving up our app to remote users (this machine will be upgraded in a couple of weeks). It is on its own domain and manages its own AD/DC etc services for terminal server.
Because the terminal server and the sql server are now on different domains - my client applications hosted on terminal server can no longer connect to the sql server using ODBC.
I can ping the sql server from TS machine as well as create network drives to other shared resources, but ODBC will not go.
HELP