Showing posts with label dns. Show all posts
Showing posts with label dns. Show all posts

Wednesday, March 21, 2012

DNS, Internet and Reporting Services

Seem to not be able to get set up right. Have split-brain dns (Server2003
with AD) natted at the firewall with 5 domains - one internal only and
dynamic; all others static for basically websites and email pointers.
Websites, email, sql, asp pages are working fine - EXCEPT REPORTING
SERVICES!!!
I have uninstalled, reinstalled, added IUSR_MachineName to users and role
assignment as browse in RS. Gave IUSR_MachineName read permissions to folder
and have the following to report:
With
<ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl> not added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set
to no anonymous and winAuth on: Security options and reports display
appropriately. Not viewable using interal ip address. Viewable from outside
the firewall using external ip address only after login prompt.
With
<ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl> added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set
to anonymous and winAuth on:
Using Internal IP: Login, then Folder Listing, Security options do not
display and reports give page not found. Report server - report viewable
Using ServerName: Login, Folder Listing, Security options do not display and
reports give page not found. Report server - report viewable.
Using External IP outside Firewall: Login, Folder Listing, Security options
do not display and reports give page not found under Reports. Report server
- report viewable.
Using domain name: Reports - page not found, ReportServer - page not found.
With
<ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl> added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set
to anonymous and winAuth on AND virtual directories added under website AND
home.aspx added and moved to top under documents for virtual directory:
Using Internal IP: Folder Listing (no login), Security options do not
display and reports give 403.8. Report server - report viewable
Using ServerName: Folder Listing (no login), Security options do not display
and reports give 403.8. Report server - report viewable.
Using External IP outside Firewall: Login, Folder Listing, Security options
do not display and reports give page 403.8. Report server - report viewable.
Using domain name url: Reports - 403.8; ReportServer - 403.8
Next?
JanetHello Janet,
If the Report Manager and Report Server are on the same machine then remove
the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
in the config file - and replace with this:
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
Peter Blackburn
Author: Hitchhiker's Guide to SQL Server 2000 Reporting Services
http://www.sqlreportingservices.net
"janetb" <janetb@.discussions.microsoft.com> wrote in message
news:EB70D3CE-FA1F-4445-9B52-48F0FCA11096@.microsoft.com...
> Seem to not be able to get set up right. Have split-brain dns (Server2003
> with AD) natted at the firewall with 5 domains - one internal only and
> dynamic; all others static for basically websites and email pointers.
> Websites, email, sql, asp pages are working fine - EXCEPT REPORTING
> SERVICES!!!
> I have uninstalled, reinstalled, added IUSR_MachineName to users and role
> assignment as browse in RS. Gave IUSR_MachineName read permissions to
> folder
> and have the following to report:
> With
> <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> not added.
> Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> set
> to no anonymous and winAuth on: Security options and reports display
> appropriately. Not viewable using interal ip address. Viewable from
> outside
> the firewall using external ip address only after login prompt.
> With
> <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> added.
> Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> set
> to anonymous and winAuth on:
> Using Internal IP: Login, then Folder Listing, Security options do not
> display and reports give page not found. Report server - report viewable
> Using ServerName: Login, Folder Listing, Security options do not display
> and
> reports give page not found. Report server - report viewable.
> Using External IP outside Firewall: Login, Folder Listing, Security
> options
> do not display and reports give page not found under Reports. Report
> server
> - report viewable.
> Using domain name: Reports - page not found, ReportServer - page not
> found.
> With
> <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> added.
> Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> set
> to anonymous and winAuth on AND virtual directories added under website
> AND
> home.aspx added and moved to top under documents for virtual directory:
> Using Internal IP: Folder Listing (no login), Security options do not
> display and reports give 403.8. Report server - report viewable
> Using ServerName: Folder Listing (no login), Security options do not
> display
> and reports give 403.8. Report server - report viewable.
> Using External IP outside Firewall: Login, Folder Listing, Security
> options
> do not display and reports give page 403.8. Report server - report
> viewable.
> Using domain name url: Reports - 403.8; ReportServer - 403.8
> Next?
> Janet|||Peter,
Thanks so much for replying. I made the change, but unfortunately there was
no change. When I try to use the url with the domain name instead of the ip
address or machineName, I still get the 403.8 dns error. I even tried
removing the virtual directories for reports and reports server from the
website - no change.
Any other ideas?
Thanks,
Janet
"Peter Blackburn (www.sqlreportingservice" wrote:
> Hello Janet,
> If the Report Manager and Report Server are on the same machine then remove
> the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
> in the config file - and replace with this:
> <UI>
> <ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
> </UI>
> Peter Blackburn
> Author: Hitchhiker's Guide to SQL Server 2000 Reporting Services
> http://www.sqlreportingservices.net
>
> "janetb" <janetb@.discussions.microsoft.com> wrote in message
> news:EB70D3CE-FA1F-4445-9B52-48F0FCA11096@.microsoft.com...
> > Seem to not be able to get set up right. Have split-brain dns (Server2003
> > with AD) natted at the firewall with 5 domains - one internal only and
> > dynamic; all others static for basically websites and email pointers.
> > Websites, email, sql, asp pages are working fine - EXCEPT REPORTING
> > SERVICES!!!
> >
> > I have uninstalled, reinstalled, added IUSR_MachineName to users and role
> > assignment as browse in RS. Gave IUSR_MachineName read permissions to
> > folder
> > and have the following to report:
> >
> > With
> > <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> > not added.
> > Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> > set
> > to no anonymous and winAuth on: Security options and reports display
> > appropriately. Not viewable using interal ip address. Viewable from
> > outside
> > the firewall using external ip address only after login prompt.
> >
> > With
> > <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> > added.
> > Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> > set
> > to anonymous and winAuth on:
> > Using Internal IP: Login, then Folder Listing, Security options do not
> > display and reports give page not found. Report server - report viewable
> > Using ServerName: Login, Folder Listing, Security options do not display
> > and
> > reports give page not found. Report server - report viewable.
> > Using External IP outside Firewall: Login, Folder Listing, Security
> > options
> > do not display and reports give page not found under Reports. Report
> > server
> > - report viewable.
> > Using domain name: Reports - page not found, ReportServer - page not
> > found.
> >
> > With
> > <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> > added.
> > Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> > set
> > to anonymous and winAuth on AND virtual directories added under website
> > AND
> > home.aspx added and moved to top under documents for virtual directory:
> > Using Internal IP: Folder Listing (no login), Security options do not
> > display and reports give 403.8. Report server - report viewable
> > Using ServerName: Folder Listing (no login), Security options do not
> > display
> > and reports give 403.8. Report server - report viewable.
> > Using External IP outside Firewall: Login, Folder Listing, Security
> > options
> > do not display and reports give page 403.8. Report server - report
> > viewable.
> > Using domain name url: Reports - 403.8; ReportServer - 403.8
> >
> > Next?
> >
> > Janet
>
>

DNS required ?

Hi All!
I facing the following problem:
Sometimes i get error while connecting to my SQLServer instance from client
machine "Timeout expired". I found it occurs when my DNS server is not reach
eable from client machine. But i connecting through alias, created by Client
network utility, where i s
pecify directly IP-address, NOT DNS-name ! I tried to connect through QA, os
ql - resuls the same.
Why it requires DNS ? What parameter i missing ?
Telnet on IP-address port works normally.
Server - NT 4.0 SP6 PDC, SQLServer 2000 Std Ed
Client - Windows 98 or NT 4.0IF you try to connect to a server named London, the name London needs to be
resolved to the IP address. This is the function that DNS provides...
However if you use theIP address yourself, DNS does not have to do anything.
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
"Slava Melnikov" <vasya000@.yandex.ru> wrote in message
news:F6CBFA12-2F13-452B-B848-5BA82228D0A1@.microsoft.com...
> Hi All!
> I facing the following problem:
> Sometimes i get error while connecting to my SQLServer instance from
client machine "Timeout expired". I found it occurs when my DNS server is
not reacheable from client machine. But i connecting through alias, created
by Client network utility, where i specify directly IP-address, NOT DNS-name
! I tried to connect through QA, osql - resuls the same.
> Why it requires DNS ? What parameter i missing ?
> Telnet on IP-address port works normally.
> Server - NT 4.0 SP6 PDC, SQLServer 2000 Std Ed
> Client - Windows 98 or NT 4.0|||What version of the SQL Server ODBC driver (sqlsrv32.dll) is installed on
the client. There is a issue with wsome of the earlier MDAC 2.6 SQL Server
ODBC drivers. If your driver version is 2000.8.0.194 you may be running
into this problem. It also occurs on some later versions as well. If you
install one of the more recent versions of MDAC, such as MDAC 2.7 then the
problem I am describing will not occur. Of course this assumes that you are
using the version of MDAC that has the problem.
When you ping the ip address does the response come back quickly or dies it
take some time?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||O-oh!
sqlsrv32.dll version is really 2000.8.0.194.
Thanks for help, Rand !
I should install latest service pack or new MDAC it's
enough ?
ping works normally

>--Original Message--
>What version of the SQL Server ODBC driver
(sqlsrv32.dll) is installed on
>the client. There is a issue with wsome of the earlier
MDAC 2.6 SQL Server
>ODBC drivers. If your driver version is 2000.8.0.194 you
may be running
>into this problem. It also occurs on some later versions
as well. If you
>install one of the more recent versions of MDAC, such as
MDAC 2.7 then the
>problem I am describing will not occur. Of course this
assumes that you are
>using the version of MDAC that has the problem.
>When you ping the ip address does the response come back
quickly or dies it
>take some time?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>

DNS problems in ASP

I hope that I'm right here.
We have an intranet-site in ASP where, till now the data was in an
Access database and we connected to the data via DNS.
Now we would like to change the data to a SQL-server.
For me, it seems logic that logic that everything should work after
creating a new DNS to the new data.
It doesn't!
None of the tables where found, ... After some search I found that I
need to prefix the tables with the owner.
I suppose that I do something wrong here and that there is a solution
for this.
Also I keep a local copy of the site to develop new pages where I also
would like to keep the data in Access so that I don't work with the
real data.
Many thanks in advance,
Filip
What tool did you use to migrate from Access to SQL Server?
You mention that you need to preface the tables with their owner.
Does that mean that a table within Access called tblData is now:
owner.tblData
or
ownertblData
If tables were created with the incorrect name you can change the table
names pretty easily. Look up sp_rename within Books Online
http://msdn2.microsoft.com/en-us/library/ms203721.aspx
If the owner of the table is not dbo and is some database user that you have
within SQL Server you should change the owner to dbo.
Look up sp_changeobjectowner within Books Online.
Once the owner is changed to dbo you should not have to specify the owner of
the table when you retrieve data from the tables.
Now that you are using SQL Server you might want to look into using stored
procedures to perform all your data access (CRUD - create, read, update,
delete)...but lets take things one step at a time.
Keith Kratochvil
"FilMar" <FilMar@.gmail.com> wrote in message
news:1159948972.268238.108090@.c28g2000cwb.googlegr oups.com...
>I hope that I'm right here.
> We have an intranet-site in ASP where, till now the data was in an
> Access database and we connected to the data via DNS.
> Now we would like to change the data to a SQL-server.
> For me, it seems logic that logic that everything should work after
> creating a new DNS to the new data.
> It doesn't!
> None of the tables where found, ... After some search I found that I
> need to prefix the tables with the owner.
> I suppose that I do something wrong here and that there is a solution
> for this.
> Also I keep a local copy of the site to develop new pages where I also
> would like to keep the data in Access so that I don't work with the
> real data.
> Many thanks in advance,
> Filip
>
|||Thanks Keith, that does the trick.
In Access they become owner_tblData but there you can rename them
without problems. In ASP they need to be [owner].[tbl_Data] if there
not owned by dbo but that is now solved with your solution.
BTW: we did the migration with the upsize wizard of Access as it seems
it does the job far better than the import/export of SQL-server.
Many thanks,
Filip
Keith Kratochvil schreef:
[vbcol=seagreen]
> What tool did you use to migrate from Access to SQL Server?
> You mention that you need to preface the tables with their owner.
> Does that mean that a table within Access called tblData is now:
> owner.tblData
> or
> ownertblData
> If tables were created with the incorrect name you can change the table
> names pretty easily. Look up sp_rename within Books Online
> http://msdn2.microsoft.com/en-us/library/ms203721.aspx
> If the owner of the table is not dbo and is some database user that you have
> within SQL Server you should change the owner to dbo.
> Look up sp_changeobjectowner within Books Online.
> Once the owner is changed to dbo you should not have to specify the owner of
> the table when you retrieve data from the tables.
>
> Now that you are using SQL Server you might want to look into using stored
> procedures to perform all your data access (CRUD - create, read, update,
> delete)...but lets take things one step at a time.
>
> --
> Keith Kratochvil
>
> "FilMar" <FilMar@.gmail.com> wrote in message
> news:1159948972.268238.108090@.c28g2000cwb.googlegr oups.com...
|||I am glad that I could help!
Keith Kratochvil
"FilMar" <FilMar@.gmail.com> wrote in message
news:1160572041.620932.71790@.b28g2000cwb.googlegro ups.com...
> Thanks Keith, that does the trick.
> In Access they become owner_tblData but there you can rename them
> without problems. In ASP they need to be [owner].[tbl_Data] if there
> not owned by dbo but that is now solved with your solution.
> BTW: we did the migration with the upsize wizard of Access as it seems
> it does the job far better than the import/export of SQL-server.
> Many thanks,
> Filip
> Keith Kratochvil schreef:
>

DNS problems in ASP

I hope that I'm right here.
We have an intranet-site in ASP where, till now the data was in an
Access database and we connected to the data via DNS.
Now we would like to change the data to a SQL-server.
For me, it seems logic that logic that everything should work after
creating a new DNS to the new data.
It doesn't!
None of the tables where found, ... After some search I found that I
need to prefix the tables with the owner.
I suppose that I do something wrong here and that there is a solution
for this.
Also I keep a local copy of the site to develop new pages where I also
would like to keep the data in Access so that I don't work with the
real data.
Many thanks in advance,
FilipWhat tool did you use to migrate from Access to SQL Server?
You mention that you need to preface the tables with their owner.
Does that mean that a table within Access called tblData is now:
owner.tblData
or
ownertblData
If tables were created with the incorrect name you can change the table
names pretty easily. Look up sp_rename within Books Online
http://msdn2.microsoft.com/en-us/library/ms203721.aspx
If the owner of the table is not dbo and is some database user that you have
within SQL Server you should change the owner to dbo.
Look up sp_changeobjectowner within Books Online.
Once the owner is changed to dbo you should not have to specify the owner of
the table when you retrieve data from the tables.
Now that you are using SQL Server you might want to look into using stored
procedures to perform all your data access (CRUD - create, read, update,
delete)...but lets take things one step at a time.
Keith Kratochvil
"FilMar" <FilMar@.gmail.com> wrote in message
news:1159948972.268238.108090@.c28g2000cwb.googlegroups.com...
>I hope that I'm right here.
> We have an intranet-site in ASP where, till now the data was in an
> Access database and we connected to the data via DNS.
> Now we would like to change the data to a SQL-server.
> For me, it seems logic that logic that everything should work after
> creating a new DNS to the new data.
> It doesn't!
> None of the tables where found, ... After some search I found that I
> need to prefix the tables with the owner.
> I suppose that I do something wrong here and that there is a solution
> for this.
> Also I keep a local copy of the site to develop new pages where I also
> would like to keep the data in Access so that I don't work with the
> real data.
> Many thanks in advance,
> Filip
>|||Thanks Keith, that does the trick.
In Access they become owner_tblData but there you can rename them
without problems. In ASP they need to be [owner].[tbl_Data] if there
not owned by dbo but that is now solved with your solution.
BTW: we did the migration with the upsize wizard of Access as it seems
it does the job far better than the import/export of SQL-server.
Many thanks,
Filip
Keith Kratochvil schreef:
[vbcol=seagreen]
> What tool did you use to migrate from Access to SQL Server?
> You mention that you need to preface the tables with their owner.
> Does that mean that a table within Access called tblData is now:
> owner.tblData
> or
> ownertblData
> If tables were created with the incorrect name you can change the table
> names pretty easily. Look up sp_rename within Books Online
> http://msdn2.microsoft.com/en-us/library/ms203721.aspx
> If the owner of the table is not dbo and is some database user that you ha
ve
> within SQL Server you should change the owner to dbo.
> Look up sp_changeobjectowner within Books Online.
> Once the owner is changed to dbo you should not have to specify the owner
of
> the table when you retrieve data from the tables.
>
> Now that you are using SQL Server you might want to look into using stored
> procedures to perform all your data access (CRUD - create, read, update,
> delete)...but lets take things one step at a time.
>
> --
> Keith Kratochvil
>
> "FilMar" <FilMar@.gmail.com> wrote in message
> news:1159948972.268238.108090@.c28g2000cwb.googlegroups.com...|||I am glad that I could help!
Keith Kratochvil
"FilMar" <FilMar@.gmail.com> wrote in message
news:1160572041.620932.71790@.b28g2000cwb.googlegroups.com...
> Thanks Keith, that does the trick.
> In Access they become owner_tblData but there you can rename them
> without problems. In ASP they need to be [owner].[tbl_Data] if the
re
> not owned by dbo but that is now solved with your solution.
> BTW: we did the migration with the upsize wizard of Access as it seems
> it does the job far better than the import/export of SQL-server.
> Many thanks,
> Filip
> Keith Kratochvil schreef:
>
>

DNS problem with reports (server URL)

I'm developing a SSRS site using SQL Server 2000 and Visual Studio 2003.
The target device is a Nokia 770 Internet tablet over a wireless network
using VPN for authentication (corporate requirement).
The 770 currently has a problem resolving server names to a fully-qualified
URL. It's been identified as a DNS-oriented bug that may take time to be
fixed. In order to enable the 770 tablet to navigate to my site, instead of
using http://myserver/Reports I have to instruct users to enter
http://myserver.country.company.com/Reports. This in and of itself is not a
problem. The trouble starts when the user clicks a report or chart; the url
generated contains a reference to http://myserver/Reportserver.
Unfortunately the tablet can't resolve this.
What I am looking for is a way to override whatever setting is limiting the
Reportserver URL and replace it with a fully qualified URL.
Anyone have any ideas? I've looked into it some but haven't figured out
what I can do.
Thanks,
Randall Arnold
NokiaRandall,
If you're able, I think the simplest solution would be to create a little
one page aspx program in which you can display your reports. Then you can
pass the full domain name to the reports server as part of the program.
Tim
Pharos Innovations
"Randall Arnold" wrote:
> I'm developing a SSRS site using SQL Server 2000 and Visual Studio 2003.
> The target device is a Nokia 770 Internet tablet over a wireless network
> using VPN for authentication (corporate requirement).
> The 770 currently has a problem resolving server names to a fully-qualified
> URL. It's been identified as a DNS-oriented bug that may take time to be
> fixed. In order to enable the 770 tablet to navigate to my site, instead of
> using http://myserver/Reports I have to instruct users to enter
> http://myserver.country.company.com/Reports. This in and of itself is not a
> problem. The trouble starts when the user clicks a report or chart; the url
> generated contains a reference to http://myserver/Reportserver.
> Unfortunately the tablet can't resolve this.
> What I am looking for is a way to override whatever setting is limiting the
> Reportserver URL and replace it with a fully qualified URL.
> Anyone have any ideas? I've looked into it some but haven't figured out
> what I can do.
> Thanks,
> Randall Arnold
> Nokia
>
>sql

DNS on Windows 2000 Server & Windows 2003 Server

We are having numerous issues with disconnects after upgrading our PDC to a
Windows 2003 environment. We have several Windows 2000 Servers running SQL
Databases that users connect to. The issue as described in my post found
under client connections is that the network connection is good but we are
getting RPC errors & "The object invoked disconnected message". Our Windows
2003 Server is running DNS. It was suggested by a developer to install the
DNS windows components found under networking on all other servers.
Will this work? Or will we cause DNS issues as a result of it?Hi
Installing DNS on every server will not solve your problem.
DNS Service in Windows 2003 is reliable so there is not need to setup many
of them.
What the the exact error number and error messages you are getting? Are any
errors logged in the SQL Event Log?
Regards
Mike
"Cstewart" wrote:

> We are having numerous issues with disconnects after upgrading our PDC to
a
> Windows 2003 environment. We have several Windows 2000 Servers running SQ
L
> Databases that users connect to. The issue as described in my post found
> under client connections is that the network connection is good but we are
> getting RPC errors & "The object invoked disconnected message". Our Windo
ws
> 2003 Server is running DNS. It was suggested by a developer to install th
e
> DNS windows components found under networking on all other servers.
> Will this work? Or will we cause DNS issues as a result of it?
>|||The errors that are appearing on the client side are as follows:
"The object invoked has disconnected from its clients" and/or "RPC server
unavailable"
Here is more information that I posted previously:
We have recently upgraded our main server from NT4 to Active Directory
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We hav
e
applied latest Windows Service Pack to clients xp sp2 and to the windows 200
0
server box. If you reboot the server and or/stop services (Com+ and Dcom) o
n
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
Note: Problems occur regardless if client is at Service Pack 2 or 1.
I have checked the event log on the server and nothing reported. I have
checked the error logs in the SQL directory of Logs and nothing reported.
Any suggestion as to what other logs (if any) to look at?
Thank you for your assistance.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Installing DNS on every server will not solve your problem.
> DNS Service in Windows 2003 is reliable so there is not need to setup many
> of them.
> What the the exact error number and error messages you are getting? Are an
y
> errors logged in the SQL Event Log?
> Regards
> Mike
> "Cstewart" wrote:
>

DNS on Windows 2000 Server & Windows 2003 Server

We are having numerous issues with disconnects after upgrading our PDC to a
Windows 2003 environment. We have several Windows 2000 Servers running SQL
Databases that users connect to. The issue as described in my post found
under client connections is that the network connection is good but we are
getting RPC errors & "The object invoked disconnected message". Our Windows
2003 Server is running DNS. It was suggested by a developer to install the
DNS windows components found under networking on all other servers.
Will this work? Or will we cause DNS issues as a result of it?Hi
Installing DNS on every server will not solve your problem.
DNS Service in Windows 2003 is reliable so there is not need to setup many
of them.
What the the exact error number and error messages you are getting? Are any
errors logged in the SQL Event Log?
Regards
Mike
"Cstewart" wrote:
> We are having numerous issues with disconnects after upgrading our PDC to a
> Windows 2003 environment. We have several Windows 2000 Servers running SQL
> Databases that users connect to. The issue as described in my post found
> under client connections is that the network connection is good but we are
> getting RPC errors & "The object invoked disconnected message". Our Windows
> 2003 Server is running DNS. It was suggested by a developer to install the
> DNS windows components found under networking on all other servers.
> Will this work? Or will we cause DNS issues as a result of it?
>|||The errors that are appearing on the client side are as follows:
"The object invoked has disconnected from its clients" and/or "RPC server
unavailable"
Here is more information that I posted previously:
We have recently upgraded our main server from NT4 to Active Directory
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We have
applied latest Windows Service Pack to clients xp sp2 and to the windows 2000
server box. If you reboot the server and or/stop services (Com+ and Dcom) on
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
Note: Problems occur regardless if client is at Service Pack 2 or 1.
I have checked the event log on the server and nothing reported. I have
checked the error logs in the SQL directory of Logs and nothing reported.
Any suggestion as to what other logs (if any) to look at?
Thank you for your assistance.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Installing DNS on every server will not solve your problem.
> DNS Service in Windows 2003 is reliable so there is not need to setup many
> of them.
> What the the exact error number and error messages you are getting? Are any
> errors logged in the SQL Event Log?
> Regards
> Mike
> "Cstewart" wrote:
> > We are having numerous issues with disconnects after upgrading our PDC to a
> > Windows 2003 environment. We have several Windows 2000 Servers running SQL
> > Databases that users connect to. The issue as described in my post found
> > under client connections is that the network connection is good but we are
> > getting RPC errors & "The object invoked disconnected message". Our Windows
> > 2003 Server is running DNS. It was suggested by a developer to install the
> > DNS windows components found under networking on all other servers.
> >
> > Will this work? Or will we cause DNS issues as a result of it?
> >
> >

DNS on Windows 2000 Server & Windows 2003 Server

We are having numerous issues with disconnects after upgrading our PDC to a
Windows 2003 environment. We have several Windows 2000 Servers running SQL
Databases that users connect to. The issue as described in my post found
under client connections is that the network connection is good but we are
getting RPC errors & "The object invoked disconnected message". Our Windows
2003 Server is running DNS. It was suggested by a developer to install the
DNS windows components found under networking on all other servers.
Will this work? Or will we cause DNS issues as a result of it?
Hi
Installing DNS on every server will not solve your problem.
DNS Service in Windows 2003 is reliable so there is not need to setup many
of them.
What the the exact error number and error messages you are getting? Are any
errors logged in the SQL Event Log?
Regards
Mike
"Cstewart" wrote:

> We are having numerous issues with disconnects after upgrading our PDC to a
> Windows 2003 environment. We have several Windows 2000 Servers running SQL
> Databases that users connect to. The issue as described in my post found
> under client connections is that the network connection is good but we are
> getting RPC errors & "The object invoked disconnected message". Our Windows
> 2003 Server is running DNS. It was suggested by a developer to install the
> DNS windows components found under networking on all other servers.
> Will this work? Or will we cause DNS issues as a result of it?
>
|||The errors that are appearing on the client side are as follows:
"The object invoked has disconnected from its clients" and/or "RPC server
unavailable"
Here is more information that I posted previously:
We have recently upgraded our main server from NT4 to Active Directory
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We have
applied latest Windows Service Pack to clients xp sp2 and to the windows 2000
server box. If you reboot the server and or/stop services (Com+ and Dcom) on
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
Note: Problems occur regardless if client is at Service Pack 2 or 1.
I have checked the event log on the server and nothing reported. I have
checked the error logs in the SQL directory of Logs and nothing reported.
Any suggestion as to what other logs (if any) to look at?
Thank you for your assistance.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Installing DNS on every server will not solve your problem.
> DNS Service in Windows 2003 is reliable so there is not need to setup many
> of them.
> What the the exact error number and error messages you are getting? Are any
> errors logged in the SQL Event Log?
> Regards
> Mike
> "Cstewart" wrote:

DNS Hostnames

I'm chewing on a DNS blacklisting system that needs to store a list of
blacklisted hosts. I am having difficulty in deciding whether to use
VARCHAR or NVARCHAR for the hostname column.
Can anyone think of a reason why I might need to store a hostname
containing, say, Chinese characters? Is that even allowed in a hostname?
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSenseiHello, Mike
According to RFC 1035, a domain name may contain uppercase and
lowercase letters (A-Z, a-z), digits (0-9), hypens (-) and points (.).
According to RFC 1738, an URL may contain only printable ASCII
characters (non-printable ASCII characters, but also some printable
characters, should be encoded with %).
In conclusion, it's better to use a varchar column instead of a
nvarchar in this case.
Razvan|||VARCHAR should be used for the hostname column.
Unicode is allowed to appear in internationalized domain names (IDN) as
defined in IDNA, but it's the responsibility of the application (e.g.,
browser) to convert the IDN to restricted-ASCII representation.
From Wikipedia: http://en.wikipedia.org/wiki/Intern...ed_domain_names
Internationalizing Domain Names in Applications (IDNA) is a mechanism
defined in 2003 for handling internationalized domain names containing
non-ASCII characters. Such domain names could not be handled by the existing
DNS and name resolver infrastructure. Rather than redesigning the existing
DNS infrastructure, it was decided that non-ASCII domain names should be
converted to a suitable ASCII-based form by web browsers and other user
applications; IDNA specifies how this conversion is to be done.
Martin C K Poon
Senior Analyst Programmer
====================================
"Mike Labosh" <mlabosh_at_hotmail.com> bl
news:%23dKp$EDYGHA.1352@.TK2MSFTNGP05.phx.gbl g...
> I'm chewing on a DNS blacklisting system that needs to store a list of
> blacklisted hosts. I am having difficulty in deciding whether to use
> VARCHAR or NVARCHAR for the hostname column.
> Can anyone think of a reason why I might need to store a hostname
> containing, say, Chinese characters? Is that even allowed in a hostname?
> --
>
> Peace & happy computing,
> Mike Labosh, MCSD MCT
> Owner, vbSensei.Com
> "Escriba coda ergo sum." -- vbSensei
>
>|||> According to RFC 1035, a domain name may contain uppercase and
> lowercase letters (A-Z, a-z), digits (0-9), hypens (-) and points (.).
> According to RFC 1738, an URL may contain only printable ASCII
> characters (non-printable ASCII characters, but also some printable
> characters, should be encoded with %).
PERFECT! THANKS!
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

DNS Error

Approximately 10 minutes after I start SQL Server, some protocols such as HTTP and IRC are no longer available. When I try to open a webpage in IEX, I get a DNS error, however I can still ping the sites.
Any advice?Could you be experiencing MyDoom (http://support.microsoft.com/?kbid=836528) or Blaster (http://www.microsoft.com/security/incident/blast.mspx)? They could produce these kind of symptoms.

-PatP|||Pat,

no I don't think so, since:

-I don't have any other problems with my PC
-This started only with SQL server
-I have the latest security updates, and the extra Blaster fix
-I have a virus scanner that updates daily

Could it have something to do with the hosts file?|||Could it have something to do with the hosts file?While pretty much anything is possible, that seems unlikely to me. If that were the case, how would starting SQL Server enter into the picture (so that the sites worked before SQL starts, and fail while SQL is running)?

-PatP|||Hmm I thought because I get DNS erros...
I did the Blaster and Doom update again but no infection was found.
Anyone else any ideas what could be wrong? Or how to detect?

Edit: I checked my Event log and there is always 4 errors and 1 warning when this occurs:

Event Type: Error
Event Source: MSSQLSERVER

19012 :
SuperSocket Info: Bind failed on TCP port 1433.

Event Type: Warning
Event Source: MSSQLServer

SuperSocket-Information: (SpnRegister) : Error 1355.

But SQL Server is still working after this. I checked KB but didn't find anything.|||Just curious, but does netstat -a -n show anything relevant?

-PatP|||I`m not sure... I did some checks with that but couldn`t make to much sense
of it. Could you tell me what I`m looking for?

The problem persists... Now I am on a small network and after the said problem the whole network breaks down and I lose internet connection. I have to reboot all machines and sometimes repair the network connection Very strange indeed. I can confirm that this only happens when SQL server is started.

Other programs running:

Kaspersky AV
Webroot SypSweeper
Sometimes ICQ or mIRC
The usual XP services|||Are you absolutely certain that the machine isn't infected by Slammer (http://www.microsoft.com/technet/security/alerts/slammer.mspx)?

-PatP|||Pat I think that was it. I didn't know that my Antivirus Program may not have been aware of this exploit.

Thanks!|||De nada! Glad that you were finally able to isolate (and fix) the problem!

-PatPsql