DNS Errors ?

[=?Utf-8?B?QmlsIENsaWNr?=]

We have a VB.NET 2.0 application running as a service on several servers.
All are either domain controllers or member servers. Service runs under
domain admin acct. Has been running for several years.

The apps start every 15 minutes and attempt to download from the same web
site. The apps have recently begun to time out at different times, with one
connecting after 2 tries and another taking 10 tries. The log files report:

** Source: System
** Message: The remote name could not be resolved: 'www.xxx.xxx.us'
** Stack:
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest&
request)
at System.Net.WebClient.DownloadData(Uri address)
at System.Net.WebClient.DownloadData(String address)
at CRLoader.CRLoader.GetPageHtml() in
C:\NCID\Projects\dotNet_2.0\Services\CRLoader\CRLo ader.vb:line 503

** Source: System
** Message: Unable to connect to the remote server
** Stack:
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest&
request)
at System.Net.WebClient.DownloadData(Uri address)
at System.Net.WebClient.DownloadData(String address)
at CRLoader.CRLoader.GetPageHtml() in
C:\SourceCode\CRLoader_265\CRLoader.vb:line 503
** InnerException System.Net.Sockets.SocketException: A connection attempt
failed because the connected party did not properly respond after a period of
time, or established connection failed because connected host has failed to
respond
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot,
SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Bool ean connectFailure,
Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState
state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
Our network admin says all is fine, DNS is fine. I am not convinced.

What I would like to know is where .NET get's it's DNS information. Our app
uses:

Imports System.Net.HttpWebRequest
Imports System.Net.HttpWebResponse

Dim myCred As New NetworkCredential(My.Settings.FTPuser,
My.Settings.FTPpassword)
Dim wClient As New WebClient
wClient.Credentials = myCred
Dim pageData As Byte() = wClient.DownloadData(My.Settings.FTPurl)
pageHtml = System.Text.Encoding.ASCII.GetString(pageData)

[Mr. Arnold]

"Bil Click" <Bi******@discussions.microsoft.comwrote in message
news:B8**********************************@microsof t.com...

We have a VB.NET 2.0 application running as a service on several servers.
All are either domain controllers or member servers. Service runs under
domain admin acct. Has been running for several years.

The apps start every 15 minutes and attempt to download from the same web
site. The apps have recently begun to time out at different times, with
one
connecting after 2 tries and another taking 10 tries. The log files
report:

<snipped>

Is the Web site's IP not static?. Why do you even need a www look-up with a
DNS to even com-up with the IP? Why not use put the IP in a config file and
use the IP to the site, instead of doing a DNS look-up. You can also use the
Hostfile that will hold the www.whatever.com = xxx.xxx.xxx.xxx IP so the
machine's O/S never goes to DNS to do the look-up for the IP. The O/S will
go to the Hostfile first, before going to DNS.

[=?Utf-8?B?QmlsIENsaWNr?=]

That is a good thought. It is difficult to get info out of the state of NC
but I will check on that.

"Mr. Arnold" wrote:

>
"Bil Click" <Bi******@discussions.microsoft.comwrote in message
news:B8**********************************@microsof t.com...

We have a VB.NET 2.0 application running as a service on several servers.
All are either domain controllers or member servers. Service runs under
domain admin acct. Has been running for several years.

The apps start every 15 minutes and attempt to download from the same web
site. The apps have recently begun to time out at different times, with
one
connecting after 2 tries and another taking 10 tries. The log files
report:

<snipped>

Is the Web site's IP not static?. Why do you even need a www look-up with a
DNS to even com-up with the IP? Why not use put the IP in a config file and
use the IP to the site, instead of doing a DNS look-up. You can also use the
Hostfile that will hold the www.whatever.com = xxx.xxx.xxx.xxx IP so the
machine's O/S never goes to DNS to do the look-up for the IP. The O/S will
go to the Hostfile first, before going to DNS.

[sloan]

Are you downloading
ftp://wakeftp.co.wake.nc.us/remfdata/
files?


"Bil Click" <Bi******@discussions.microsoft.comwrote in message
news:B8**********************************@microsof t.com...

We have a VB.NET 2.0 application running as a service on several servers.
All are either domain controllers or member servers. Service runs under
domain admin acct. Has been running for several years.

The apps start every 15 minutes and attempt to download from the same web
site. The apps have recently begun to time out at different times, with
one
connecting after 2 tries and another taking 10 tries. The log files
report:

** Source: System
** Message: The remote name could not be resolved: 'www.xxx.xxx.us'
** Stack:
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest&
request)
at System.Net.WebClient.DownloadData(Uri address)
at System.Net.WebClient.DownloadData(String address)
at CRLoader.CRLoader.GetPageHtml() in
C:\NCID\Projects\dotNet_2.0\Services\CRLoader\CRLo ader.vb:line 503

** Source: System
** Message: Unable to connect to the remote server
** Stack:
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest&
request)
at System.Net.WebClient.DownloadData(Uri address)
at System.Net.WebClient.DownloadData(String address)
at CRLoader.CRLoader.GetPageHtml() in
C:\SourceCode\CRLoader_265\CRLoader.vb:line 503
** InnerException System.Net.Sockets.SocketException: A connection attempt
failed because the connected party did not properly respond after a period
of
time, or established connection failed because connected host has failed
to
respond
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot,
SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Bool ean connectFailure,
Socket s4, Socket s6, Socket& socket, IPAddress& address,
ConnectSocketState
state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
Our network admin says all is fine, DNS is fine. I am not convinced.

What I would like to know is where .NET get's it's DNS information. Our
app
uses:

Imports System.Net.HttpWebRequest
Imports System.Net.HttpWebResponse

Dim myCred As New NetworkCredential(My.Settings.FTPuser,
My.Settings.FTPpassword)
Dim wClient As New WebClient
wClient.Credentials = myCred
Dim pageData As Byte() = wClient.DownloadData(My.Settings.FTPurl)
pageHtml = System.Text.Encoding.ASCII.GetString(pageData)