J# Socket Bug - Hotfix

From: chris vella (chris_at_dload.com.au)
Date: 08/02/04

  • Next message: Bob: "Displaying Unicode characters in J#" 
    Date: Mon, 2 Aug 2004 10:14:43 +1000

    I have a jsharp server application that was built and running fine on my
    development machine. However when it went live to a Win 2k server the
    application could not connect to the remote application. It was receiving a
    NoRouteHost Exception. The difference between the two machines was the
    server was mutli homed while the dev box isn't.

    Essentially the J# socket was binding to the wrong nic which was connected
    to an internal network. No matter what I tried (adding routes to route table
    etc.) the socket would not binf to the external nic. I believe that this is
    an issue as stated in Q819777 but I haven't had any replies from microsoft
    support in relation to obtaining this hotfix.

    Can someone please help me out?

    Cheers

    Chris

  • Next message: Bob: "Displaying Unicode characters in J#"

    Relevant Pages

    • VB->SQL: Date Format Problem.
      ... which although it worked on my development machine, ... but wasnt accepted by the live server. ... it appears that the SQL code that is called ... I imagine that this is something to do with regional settings or ...
      (microsoft.public.sqlserver.programming)
    • VB->SQL: Date Format Problem.
      ... which although it worked on my development machine, ... but wasnt accepted by the live server. ... it appears that the SQL code that is called ... I imagine that this is something to do with regional settings or ...
      (microsoft.public.vb.database)
    • Re: Can not automation word with Vb.net
      ... development machine. ... My references are pointing to Word and Office 9.0 Object ... Unable to cast COM object of type "System._Comobject' to interface type ... which is on a server ...
      (microsoft.public.office.developer.automation)
    • Re: Program crashes in msvcrt.dll
      ... It is not necessary for the development machine to be the same os-version as ... and look at the call stack when it crashes. ... > Windows 2003 Server or Windows 2000 Server. ...
      (microsoft.public.vstudio.development)
    • Problems upgrading application from .NET 1.0 to 1.1
      ... Format" every time I try to connect to a SQL Server 2000 database. ... My development machine is running Win XP with both the 1.0 and 1.1 ... I removed and re-added all of the Crystal references, ... removing and rebuilding the setup project from scratch. ...
      (microsoft.public.dotnet.framework)
    Loading