Post reply

Could Active Directory Be Causing a connection manager to point to wrong server

  • August 7, 2014 at 5:22 am

    #291696

    I have a connection manager that is getting its connection string from table. I've checked the table several times and the configuration is correct. I set the server to a server named MyServer and the database named MyDatabase. WhenI run this package on laptop which points to the same configuration table as the package that resides on my qa server, I get the correct record counts from the source "MyServer server and MyDatabase" but when I run it from the qa server in a job I get more records than I should. I've checked the configuration tab for the job and its blank. Could it be that Active Directory could be mapping the MyServer name to another server with a database called MyDatabase?

  • August 7, 2014 at 6:01 am

    #1735930

    Not AD, but DNS could.

    If your machine uses one set of DNS servers and the QA server uses another set, then yes you could potentially have a mismatch of DNS entries.

    Speak to your network guys/server admins, to find out if your DNS servers differ from your QA servers, and if they do find out what MyServer they both want to connect to.

    Edit: Also check for entries in yours and the servers host files, which will bypass DNS and send the connection somewhere else

  • August 7, 2014 at 8:05 am

    #1735983

    Could this happen even if Im using the server name?

  • August 7, 2014 at 8:11 am

    #1735987

    Yes, as with anything networking it needs an IP address not a hostname, so your DNS servers handle the hostname to IP address lookup for you.

    If your laptop is using DNS server 10.0.1.1 and your servers are using 192.168.1.1 and they both have an entry for MyServer, your DNS server could say well MyServer is on IP 10.45.6.7, while the servers DNS server may say that MyServer is on 192.168.34.6. So you will go to two different servers depending where your running the package from.

    So you will need to double check if both your laptop and your servers are sharing the same DNS servers, if they are, then there is something else going on like hostfile entires which will bypass your DNS servers, or even something like DNS caching where either one of you have the wrong IP stored in your DNS cache, or something more sinister is happening.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply