I posted earlier ("SQL Port 1433 - which IPs should be listening?") and
realize now how unreadable my post was.
I do have a few questions which might help clarify things for everyone though:
1. When running netstat -an, should the (default settings) 1433 port be
listening on IPs other than 0.0.0.0?
2. Does IIS utilize different methods of communicating with SQL than other
software like, say, Service Manager? (I can connect via Service Manager, but
I can't connect via the ASAPI website - is this a problem with the way IIS
operates, or is it something wrong with the DLL on the ASAPI website?)
We do have this same DLL ASAPI website running at a different location, and
it accesses the SQL server without any problems - so I am thinking that the
problem might be on the SQL side - which I have no experience with.
3. What are suggested methods of testing a connection / authentication
between a website hosted (DLL) on IIS, but accessing SQL 2000 on a different
server?
Any help would be greatly appreciated, and I would eagerly accept any
requests for clarifying the issue so that you could more easily help me.
Thanks.Problem as stated has been resolved. Thanks.
No comments:
Post a Comment