When I OFF the windows firewall on the machine,

it worked . Now can connect to sql server and through telnet too.

Huh.

Guess the windows firewall icon popped up on that...

Roy Ernest (9/15/2011)

---

Could be that.. But there is another possibility that you have to look at. You said that TCP port 1433 was green and open, but to connect using...

When I OFF the windows firewall on the machine,

it worked . Now can connect to sql server and through telnet too.

Huh.

Guess the windows firewall icon popped up on that...

Steve Jones - SSC Editor (9/15/2011)

---

have you checked the SQL Server log on the remote machine. Is it listening on 1433? When SQL starts up, it will let you know...

I ran through QA on the remote...

@ jack..

I checked the firewall settings,

on the exception tab i have many buttons checked , the relevant looks like these

1) SQL 1433 port ( TCP button green)

2) sql 1443...

@ jack

I am not able to telnet it

it says no connection to host on the port 1433

I made sure that 1433 port is sql server on that machine.

What could...

telnet 127.0.0.1 [port #]

Should hte port number be 1443 or what else?

Regards,

Sushant

@ jack

I can ping through remote server.

Didn't try telnet though (Don't know how to execute it )

Nothing has changed from last time i connected, but yes, always it took around...

@ jack ....

I connected with/without linked server,

from both, I am getting same error.

Regards,

Sushant

Hi,

Yes I have already created a linked server to it.

But when I test connection, I get this error:--

(Attached)

Regards,

Sushant

do that by import, export task on the instance

and den select save ssis package in end

then make a new job with tht ssis package running the time u want to

Regards,

Sushant

go to jobs. select it

go to object explorer

select 1

ctrl all jobs

right click ...create to file

then wen u r into sql 2008 r2

jsut execute tht sql statments

It should be good to...

any views??

Regards,

Sushant

jlennartz (9/14/2011)

---

Steve Jones - SSC Editor (9/14/2011)

---

This problem with the question is entirely my fault, not Ron's. I copied over the code, making a mistake after testing it when I...