Hello Manjree,
Thank you for your update!
From the symptom, it seems SQL Browser service is not started or it's
blocked by firewall. Please make sure it's started. Also, if firewall is
on, please enable UDP 1434 so that client could access sql browser service.
http://blogs.msdn.com/sql_protocols/...24/473502.aspx
INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932
Since it's not a default instance, client will not try 1433 directly and it
will contact browser service to get the proper port to use.
To work around this issue, you could also create alias for the server in
sql client network utility to test
http://blogs.msdn.com/sql_protocols/...ion-alias.aspx
If you have any update, please feel free to let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
================================================== ===
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.