Dns.Resolve on TCP Connection

[veerusrahul]

Hi have developed a ftp append code in VB.net (.net1.1).
I am creating a TCP socket on port 21 using server hostname.The code work fine in my laptop but when i test in a device with WindowsXPe , i am getting a Dns.Resolve error as "The type initilizer for system.Net.Dns threm exception"
at Dns.Resolve(remoteHost)
Please help me !!!!

Public Sub New(ByVal remoteHost As String, ByVal controlPort As Integer, ByVal timeout As Integer)
            Try
                Dim remoteHostEntry As IPHostEntry = Dns.Resolve(remoteHost)
                Dim ipAddresses() As IPAddress = remoteHostEntry.AddressList
               Initialize(ipAddresses(0), controlPort, timeout)
            Catch ex As Exception
                Logger.Write(ELogLevel.ERROR, ex.Message)
            End Try
End Sub
 
Friend Sub Initialize(ByVal remoteAddr As System.Net.IPAddress, ByVal controlPort As Integer, ByVal timeout As Integer)
 
            Try
                'establish socket connection & set timeouts
                Dim ipe As IPEndPoint = New IPEndPoint(remoteAddr, controlPort)
 
                controlSock = New Socket(AddressFamily.InterNetwork,    SocketType.Stream, ProtocolType.Tcp)
                TimeOutValue = timeout
                controlSock.Connect(ipe)
                InitStreams()
                ValidateConnection()
            Catch ex As Exception
                Logger.Write(ELogLevel.ERROR, " ex.Message)
            End Try
 
End Sub
 
 
        End Sub
 

[Plater]

Sounds like whatever code you are writing, one of the functions is not available on compact framework.
Which line was it that had the exception? and what was the exact exception message?

[veerusrahul]

i am using normal .net 1.1 framework , it was working fine earlier know its stopped. I am getting error in
Dim remoteHostEntry As IPHostEntry = Dns.Resolve(remoteHost) this line

[Plater]

@veerusrahul
Right but you said when you put on WindowsXPe (XP embedded), which would use the compact framework, it stops working.

[veerusrahul]

Resolved , there was a problem with Log4net logging but it was always showing this error at that particular time.