I have a sql2k inside LAN, which is used for a intranet
web site, in the DSN setting of web server side, I am
using DB server's DNS entry for the server name, it
worked properly, and some days ago, when some setting of
our LAN changed, I find this DNS entry can't be used, but
I still can ping that DB server using the same DNS name.
any hint for this problem?if you can ping that DNS name then you should be able to
connect to it through a DSN, try to run this command on a
DOS command prompt:
telnet <dns name of the db server> 1433
if you see a blank screen that means you are connected to
sql server on port 1433 and there is no network
connectivity issue, otherwise you should get an error.
Please also give us more details about your environment,
OS, service packs, mdac version etc. If you can provide us
details of network configuration on db and http servers
then that would really help. Connecting to sql server is
pretty straight forward task if network configuration is
right. Sometime comapnies put even internal webserver on a
DMZ, which would require more network configuration to be
able to connect to a db server inside firewall.
hth.
>--Original Message--
>I have a sql2k inside LAN, which is used for a intranet
>web site, in the DSN setting of web server side, I am
>using DB server's DNS entry for the server name, it
>worked properly, and some days ago, when some setting of
>our LAN changed, I find this DNS entry can't be used, but
>I still can ping that DB server using the same DNS name.
>any hint for this problem?
>.
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment