Strange problem socket programming on different Windows plattform

Question

Want to connect to site in internet like http://www.google.com. In Eclipse and as .jar.File on my Windows 7 everything runs fine. On Windows 2003 or Vista I cut LAN, so no network and the application response 'ok' and do not throw an Exception, what my Windows 7 and another Windows XP do immediately. New start of application has the same effect. After a time of circa 20 seconds application throws an Exception. Bad surprise. All Windows use java version 1.6.0_21.
Any ideas, please.
     URL url=null;
               try{
                         url=new URL("http://www.google.de");
               }catch(MalformedURLException e){
                    System.err.println("01");
     try {
               URLConnection con=url.openConnection();
               con.setConnectTimeout(250);
     }catch(IOException e){
          System.err.println("03");
     InetAddress inetAddress=null;
     try{
               inetAddress=InetAddress.getByName(url.getHost());
     }catch(UnknownHostException e){
          System.err.println("04");
     SocketAddress socketAddress=new InetSocketAddress(inetAddress,80));      
     Socket clientSocket=new Socket();
     try{
          clientSocket.connect(socketAddress,250);
     }catch(SocketTimeoutException stoe){
          System.err.println("05");
     }catch(IOException ioe){
          System.err.println("06");
     if(clientSocket!=null){
               if(!clientSocket.isConnected()){
                    System.err.println("07");
               try{
                         clientSocket.close();
               }catch(IOException e){}
     }else{
          System.err.println("08");
     }                      

Answer 1

1. JVM would never get information network is broken.I didn't say anything even remotely resembling that, and I didn't say anything about the JVM at all.
2. Different hardwareI didn't say anything about hardware either.
So you haven't 'disproved' anything yet.
Win XP Pro SP3 on Pentium M and Celeron laptops get information from its hardware.Obviously, and from their TCP/IP stacks.
JVM get information from OSObviously.
and put it to cache every definied time as reply a cycle.I can't make much sense of that, but the JVM certainly doesn't maintain TCP reply timers. It relies entirely on the TCP/IP stack for that.
This unit of time should be set shorter. I think, I have to parameterization JVM to put the information for TCP/IP in shorter time to cache. I would know gladly where this has to define.As this imaginary timer doesn't exist, there is nothing to define. As I already told you, 'there is nothing you can do about it within Java'.
If the hardware delivers an interrupt to the operating system and the operating system delivers that in some form to the TCP/IP stack and the TCP/IP stack construes it as a cable loss and turns that into a ' connection reset', that's what you will get in your Java code. If all that doesn't happen, you won't.