locked
Weird one - Router Death by Vista RRS feed

  • Question

  • Here's a weird one.

    It seems that Vista RC2 is routinely killing my ADSL router

     

    I have a dual boot system (patched up XP Pro vs Vista RC2).

    Vista seems to be killing my D-Link DSL-500 like...., several times a day while Vista is running.

    Has anyone else noticed this ???

     

    I'm thinking.... some sort of weird network plug and play thing (which is disabled - by the way)

     

    RickW

    Sunday, October 15, 2006 8:09 AM

All replies

  • Why do you believe Windows Vista is the culprit?  Please share any logs, etc from any debugging you have done
    Monday, October 23, 2006 3:12 AM
  • Mike,

    RE: Why do you believe Windows Vista is the culprit? 

    I admit the evidence is circumstantial... however... it goes like this...

     

    1. The system is dual booted between Vista RC2 and XP Pro SP2

    2. The local 192.168.x.x. network has 1 single PC (above) a default gateway (combo DLink ADSL router + DHCP server)

    3. There is also a Dlink 504 802.11G AP on 192.168.x.x. with no clients

    4. The "hung" router symptom only happens when the dual boot  PC system is in Vista mode

    5. The "hung" condition is quite frequent 0-3 times in a 4 hour session say. The routers LEDs freeze and the default gateway will not respond to PING and the web interface is not responsive. I have recycle the power on the ADSL router to restore connectivity

    6. I notice the symptom in 3 ways:

    - While actively browsing the web under Vista  - noticing that sites are no longer responding

    - Noticing the Vista network icon shows "Limited Connectivity"

    - Using the XBOX 360 Media Extender - the session disconnects from Vista PC

    7. The only log I have is off the ADSL router

                                
    [PPP]Up 1 min 28 secs-Connect:PPP LCP reaches open state;                                                   
    [PPP]Up 1 min 28 secs-Auth:PPP Start PAP authentication;                                                  
    [PPP]Up 1 min 31 secs-Connect:PPP Stop;                                                                   
    [PPP]Up 1 min 31 secs-Connect:PPP LCP reaches open state;                                                 
    [PPP]Up 1 min 31 secs-Auth:PPP Start PAP authentication;                                                  
    [PPP]Up 1 min 32 secs-Auth:PPP authentication fail;                                                       
    [PPP]Up 1 min 32 secs-Connect:PPP Stop;                                                                   
    [PPP]Up 2 mins 7 secs-Connect:PPP triggered start;                                                        
    [PPP]Up 2 mins 10 secs-Connect:PPP LCP reaches open state;                                                
    [PPP]Up 2 mins 10 secs-Auth:PPP Start PAP authentication;                                                 
    [PPP]Up 2 mins 10 secs-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 2 mins 11 secs-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 274 mins 30 secs-Connect:PPP Stop;                                                                
    [PPP]Up 302 mins 56 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 302 mins 59 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 302 mins 59 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 303 mins 0 sec-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 303 mins 0 sec-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 412 mins 39 secs-Connect:PPP Stop;                                                                
    [PPP]Up 517 mins 14 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 517 mins 17 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 517 mins 17 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 517 mins 18 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 517 mins 18 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 782 mins 7 secs-Connect:PPP Stop;                                                                 
    [PPP]Up 1180 mins 51 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1180 mins 54 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1180 mins 54 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1180 mins 54 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1180 mins 55 secs-Connect:PPP IPCP reaches open state;  
                                              
    [PPP]Up 1337 mins 4 secs-Connect:PPP Stop;                                                                
    [PPP]Up 1345 mins 33 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1345 mins 36 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1345 mins 36 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1345 mins 37 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1345 mins 38 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1360 mins 36 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1364 mins 46 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1364 mins 49 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1364 mins 49 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1364 mins 50 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1364 mins 50 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1632 mins 39 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1675 mins 33 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1675 mins 36 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1675 mins 36 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1675 mins 36 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1675 mins 36 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1841 mins 36 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1875 mins 27 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1875 mins 30 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1875 mins 30 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1875 mins 31 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1875 mins 31 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1907 mins 40 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1922 mins 50 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1922 mins 53 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1922 mins 53 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1922 mins 54 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1922 mins 55 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1954 mins 33 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2015 mins 43 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2015 mins 46 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2015 mins 46 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2015 mins 46 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2015 mins 46 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2851 mins 46 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2854 mins 16 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2854 mins 19 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2854 mins 19 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2854 mins 19 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2854 mins 20 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 3642 mins 59 secs-Connect:PPP Stop;                                                               
    [PPP]Up 4055 mins 3 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 4055 mins 6 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 4055 mins 6 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 4055 mins 6 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 4055 mins 7 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 1 min 35 secs-Connect:PPP IPCP reaches open state;                                                
    [PPP]Up 218 mins 5 secs-Connect:PPP Stop;                                                                 
    [PPP]Up 243 mins 5 secs-Connect:PPP triggered start;                                                      
    [PPP]Up 243 mins 8 secs-Connect:PPP LCP reaches open state;                                               
    [PPP]Up 243 mins 8 secs-Auth:PPP Start PAP authentication;                                                
    [PPP]Up 243 mins 9 secs-Connect:PPP IPCP reaches open state;                                              
    [PPP]Up 243 mins 9 secs-Connect:PPP IPCP reaches open state;                                              
    [PPP]Up 325 mins 38 secs-Connect:PPP Stop;                                                                
    [PPP]Up 328 mins 17 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 328 mins 20 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 328 mins 20 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 328 mins 20 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 328 mins 20 secs-Connect:PPP IPCP reaches open state;
                                                 
    [PPP]Up 410 mins 0 sec-Connect:PPP Stop;                                                                  
    [PPP]Up 423 mins 31 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 423 mins 34 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 423 mins 34 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 423 mins 34 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 423 mins 34 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 512 mins 14 secs-Connect:PPP Stop;                                                                
    [PPP]Up 832 mins 37 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 832 mins 40 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 832 mins 40 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 832 mins 40 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 832 mins 41 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 847 mins 0 sec-Connect:PPP Stop;                                                                  
    [PPP]Up 857 mins 39 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 857 mins 42 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 857 mins 42 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 857 mins 42 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 857 mins 42 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 862 mins 52 secs-Connect:PPP Stop;                                                                
    [PPP]Up 871 mins 10 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 871 mins 13 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 871 mins 13 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 871 mins 13 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 871 mins 14 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 877 mins 43 secs-Connect:PPP Stop;                                                                
    [PPP]Up 877 mins 57 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 878 mins 0 sec-Connect:PPP LCP reaches open state;                                                
    [PPP]Up 878 mins 0 sec-Auth:PPP Start PAP authentication;                                                 
    [PPP]Up 878 mins 0 sec-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 878 mins 0 sec-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 887 mins 20 secs-Connect:PPP Stop;                                                                
    [PPP]Up 901 mins 11 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 901 mins 14 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 901 mins 14 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 901 mins 15 secs-Auth:PPP authentication fail;                                                    
    [PPP]Up 901 mins 15 secs-Connect:PPP Stop;                                                                
    [PPP]Up 901 mins 19 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 901 mins 22 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 901 mins 22 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 901 mins 23 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 901 mins 23 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 961 mins 2 secs-Connect:PPP Stop;                                                                 
    [PPP]Up 995 mins 25 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 995 mins 28 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 995 mins 28 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 995 mins 29 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 995 mins 29 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 1043 mins 48 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1051 mins 21 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1051 mins 24 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1051 mins 24 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1051 mins 24 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1051 mins 25 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1097 mins 24 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1105 mins 23 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1105 mins 26 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1105 mins 26 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1105 mins 26 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1105 mins 26 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1244 mins 46 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1251 mins 13 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1251 mins 16 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1251 mins 16 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1251 mins 17 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1251 mins 17 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1257 mins 36 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1258 mins 29 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1258 mins 32 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1258 mins 32 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1258 mins 33 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1258 mins 33 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1295 mins 12 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1296 mins 22 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1296 mins 25 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1296 mins 25 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1296 mins 26 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1296 mins 26 secs-Connect:PPP IPCP reaches open state;                                            
    [SNMP]Up 12 secs-Link:Ethernet Link Up;                                                                   
    [BUN]Up 16 secs-Link:ADSL Link Up;                                                                        
    [PPP]Up 1 min 7 secs-Connect:PPP triggered start;                                                         
    [PPP]Up 1 min 31 secs-Connect:PPP LCP reaches open state;                                                 
    [PPP]Up 1 min 31 secs-Auth:PPP Start PAP authentication;                                                  
    [PPP]Up 1 min 32 secs-Connect:PPP IPCP reaches open state;                                                
    [PPP]Up 1 min 32 secs-Connect:PPP IPCP reaches open state;                                                
    [PPP]Up 69 mins 1 sec-Connect:PPP Stop;                                                                   
    [PPP]Up 73 mins 59 secs-Connect:PPP triggered start;                                                      
    [PPP]Up 74 mins 3 secs-Connect:PPP LCP reaches open state;                                                
    [PPP]Up 74 mins 3 secs-Auth:PPP Start PAP authentication;                                                 
    [PPP]Up 74 mins 3 secs-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 74 mins 3 secs-Connect:PPP IPCP reaches open state;                                               
    [PPP]Up 1343 mins 43 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1344 mins 12 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1344 mins 15 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1344 mins 15 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1344 mins 15 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1344 mins 15 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1350 mins 55 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1363 mins 27 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1363 mins 30 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1363 mins 30 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1363 mins 31 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1363 mins 31 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1387 mins 20 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1396 mins 46 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1396 mins 49 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1396 mins 49 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1396 mins 49 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1396 mins 49 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1402 mins 29 secs-Connect:PPP Stop;                                                               
    [PPP]Up 1408 mins 29 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 1408 mins 32 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 1408 mins 32 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 1408 mins 33 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 1408 mins 33 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2181 mins 2 secs-Connect:PPP Stop;                                                                
    [PPP]Up 2230 mins 22 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2230 mins 25 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2230 mins 25 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2230 mins 25 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2230 mins 25 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2304 mins 35 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2305 mins 41 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2305 mins 44 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2305 mins 44 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2305 mins 45 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2305 mins 45 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2322 mins 14 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2335 mins 56 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2335 mins 59 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2335 mins 59 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2335 mins 59 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2335 mins 59 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2373 mins 49 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2396 mins 9 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 2396 mins 12 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2396 mins 12 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2396 mins 13 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2396 mins 14 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2401 mins 22 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2426 mins 22 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2426 mins 25 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2426 mins 25 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2426 mins 25 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2426 mins 26 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2437 mins 35 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2456 mins 35 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2456 mins 39 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2456 mins 39 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2456 mins 39 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2456 mins 39 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2461 mins 49 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2486 mins 49 secs-Connect:PPP triggered start;                                                    
    [PPP]Up 2486 mins 52 secs-Connect:PPP LCP reaches open state;                                             
    [PPP]Up 2486 mins 52 secs-Auth:PPP Start PAP authentication;                                              
    [PPP]Up 2486 mins 52 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2486 mins 52 secs-Connect:PPP IPCP reaches open state;                                            
    [PPP]Up 2493 mins 22 secs-Connect:PPP Stop;                                                               
    [PPP]Up 2517 mins 5 secs-Connect:PPP triggered start;                                                     
    [PPP]Up 2517 mins 8 secs-Connect:PPP LCP reaches open state;                                              
    [PPP]Up 2517 mins 8 secs-Auth:PPP Start PAP authentication;                                               
    [PPP]Up 2517 mins 9 secs-Connect:PPP IPCP reaches open state;                                             
    [PPP]Up 2517 mins 9 secs-Connect:PPP IPCP reaches open state;                                             
    [SNMP]Up 12 secs-Link:Ethernet Link Up;                                                                   
    [BUN]Up 16 secs-Link:ADSL Link Up;                                                                        
    [PPP]Up 1 min 7 secs-Connect:PPP triggered start;                                                         

     

    I don't know how to force the behaviour.

    Correlation is not causation - that's why I want to ask folk if they have noticed this symptom as well.

    These sorts of possible interaction issue often get the blood pressure up eh?

    I have a workaround via the power reset , however, The Wife Acceptance Factor is being severely dented :(

     

    Cheers,

    RickW

     

     

     

     

    Monday, October 23, 2006 8:44 PM
  • hi,

    I have the same problem. Also perfectly working on xp and router dieing in vista.

    I have tried to uncheck the TCP/IPv6 box in the LAN options a minute ago, seems to be working but not sure though.

    Happened to me on wired and wireless router, the router just resets itself leaving me with no internet, only a local connection. I have to go into the router and make it renew DHCP to find my external ip/dns etc..

     

    I'll try to post back later to tell you if this problem is solved. Maybe you can try it too :)

     

    cheers,

    -bb10

    Sunday, November 19, 2006 9:02 PM
  •  

    The symptoms sound similar.

    I will try disabling IPv6 too.

    BTW: When I went to reply.... the router had hung and needed to be rebooted .

     

    Monday, November 20, 2006 1:00 AM
  •  

    bb10,

    Nice try. I tried it and it seemed to work for a few hours. I had really high hopes - the fix sounded attractive intuitively.

    It has to be something like this. i.e. something Vista is doing differently that the router is not expecting and not handling properly.

    Any other ideas?

    RickW

     

     

     

     

     

     

    Tuesday, November 21, 2006 7:08 PM
  • hi,

     

    Yeah it D/C'ed for me too. Also found that when i start/shut down vista it resets the router.

    Haven't found a solution yet but i'll keep searching.

     

    I also think it has something to do with vista sending a signal to the router that causes it to reset.

     

    cheers,

    bb10

    Tuesday, November 21, 2006 9:04 PM
  • I may have found a solution :)

    Turned off UPnP in my router, now my router doesn't d/c when i start/shut down vista or the nic.

    :)

    Friday, November 24, 2006 12:47 PM
  • Except I have always had uPnP disabled and I still get hard lockups every few hours

    What model router do you have?

     

    I may end up having to buy another brand/model :(

     

    Rickw

    Saturday, November 25, 2006 12:37 AM
  • I have been having problems with my DLink DI-624 rev C. Whenever Vista is booted I cannot connect to the wireless side from my XP tablet. It works fine when Vista is shut down, or I'm running XP. I tried turning off UPnP in the router, and then the router just keeps rebooting.
    Monday, November 27, 2006 1:15 AM
  • I have a linksys Wireless-B Broadband Router (BEFW11S4), and I'm facing the same problem, after a few minutes my router hangs on me.

    The following are facts about my system:

    • I'm running Vista RTM
    • I updated the routers firmware to the latest
    • I disabled the IPv6
    • I tried to connect only wired and only wireless

     

    Nothing helped so far.

     

    Any ideas are more than welcome

    Monday, November 27, 2006 7:47 PM
  •  ZardoS42 wrote:

    Except I have always had uPnP disabled and I still get hard lockups every few hours

    What model router do you have?

     

    I may end up having to buy another brand/model :(

     

    Rickw

    I have a SMC Barracuda 7004ABR v2 EU

    Monday, November 27, 2006 10:54 PM
  • Yesterday (on my DLink DI624 rev C, I downgraded the firmware from 2.76 to 2.42 and it works as it has in the past (now with Vista) <fwiw>
    Wednesday, November 29, 2006 2:06 PM
  • Same here.  I have the Linksys WRT55AG, which is terrible as it is but sure enough, I continually have to restart the router if Vista restarts or is even on for an extended period of time.  Xbox 360 has to be re-added in MCE every time.  Tried everything here.  Any new thoughts?
    Thursday, November 30, 2006 1:15 AM
  • I have the same problem with a Belkin F5D7630uk-4A.

    On logon or restart/shutdown, or an attempt to access the internet by Windows components (Windows updates, Windows Defender, downloading Media Guide etc), my router will restart and I will lose internet connectivity for however long it takes the router to cycle.

    I am running a dual-boot of XP Pro SP2 on my C: drive (250GB SATA2) and Vista RC2 on my G: drive (80GB SATA2). There are no problems with the router whatsoever under XP.

    The exact same problems occured with Beta 2 & RC1.

    Saturday, December 2, 2006 2:50 PM
  • Rick, any luck thus far keeping the Xbox 360 connected?  Mine disconnects after every restart.  Takes 1 hour each time trying to re-add the extender in MCE.
    Tuesday, December 5, 2006 12:48 AM
  • thebasa,

    I have not seen this behaviour so far. (the needing to "re-add" bit and the 1 hour bit)

    The disconnect behaviour I have seen but in my case it seems to be related to either the DHCP lease expiring and the ADSL router (DHCP server) being in a hung state.

    One observation I have is that the the XBOX 360 seems to need the default gateway to be present to communicate to the MCE PC even when the IP address and masks are for the same network. This I don;t understand.

    My understanding of TCP/IP is that the communications on the 192.168.0.XXX 255.255.255.0 address space should be via MAC ARP etc since the XBOX 360 get allocated .2 and the MCE PC is allocated .52 

    Try checking your MCE machine IP address allocation mechanism - mine is static - yours may not be and may be being allocated a different IP address each time it restarts (depending onthe whims of the DHCP server or other address allocator)

    RickW

    Tuesday, December 5, 2006 8:46 PM
  • Tony,

    So your are saying it works ok now?

    What hints are there in the firmware release notes as to causation?

     

    RickW

    Tuesday, December 5, 2006 8:49 PM
  • Hazzamon,

    I suggest you keep a watch on this thread until a pattern appears.

    I am very keen to hear if this problem occurs on non-residential routers too i.e. more SME and upwards Cisco 8xx series etc

    RickW

     

    Tuesday, December 5, 2006 8:58 PM
  • Mike,

    This topic seems to have touched a raw nerve out there.

    If something in the updated Vista TCP/IP stack is freaking out popular consumer grade ADSL and 802.11 routers then it needs to be tracked down and squashed before the general consumer market release.

    RickW

     

     

    Tuesday, December 5, 2006 9:17 PM
  • Yeah my Vista MCE machine IP is static and the Xbox 360 gets any available. Xbox 360 default gateway is always set as the router IP. Having to add the 360 extender in MCE again is all a result of the router getting hung as you describe, but additionally for me, it seems not as cut and dry as a router restart for everything to be peachy again. The 1 hour sessions involve multiple restarts of all equipment to finally get MCE to agree there's a ready-and-waiting 360 out there to connect. I read here that adding a switch for the Vista PC and 360 might work bnut haven't tried yet: http://thegreenbutton.com/forums/thread/151017.aspx

    Friends at Xbox forums, same problem: http://forums.xbox.com/8598619/ShowPost.aspx

    I should mention what I did in that forum:

    "One thing I'm sure of is that the behavior absolutely never happened before I went through the Windows Media Player 11 setup upon opening it for the first time. There are specific steps for overcoming WMP11 Vista-to-360 extender problems......and they work as good as the directions to add an extender.........THEY DON'T!"

    Perhaps getting rid of WMP11 is the answer???

    Tuesday, December 5, 2006 10:04 PM
  • aaron,

    Under Network and Sharing ...

    What have you got configured?

    Are you using Media Sharing? Media Connect - the plain vanilla 360 to PC connection s/w?

    BTW: I followed the http://thegreenbutton.com/forums/thread/151017.aspx
    and other link and I don't get the connection - am I missing something?

    RickW

     

     

     

    Tuesday, December 5, 2006 11:27 PM
  • Hi RickW,

    I'm having the problem with a Linksys WRV54G, usually marketed to small businesses for hotspot and VPN use.  I do use it at home though.

    Every few hours or so, my laptop loses its wireless connection and I look over too see the router blinking about an error (haven't looked up the exact error condition yet).  I reboot the router, but often that's not enough for Vista to be able to reconnect.  Sometimes it's necessary for me to reboot it as many as 5 times (waiting for a while in between) before it will show up in Vista's list of available connections when I click the refresh button.  Sometimes when it's back on the list, Vista reports that it was unable to make the connection.  Other times, Vista connects but the connection is labelled "Limited Connection".  It always works eventually, if I just keep at it.

    I need to dig into the documentation myself, but I wanted to let you know about this, since you were wondering if there are issues with non-residential routers as well.

    Jacob

    Wednesday, December 6, 2006 2:03 AM
  • Linksys WRT54G

    Same problem as others - Each time Vista reboots, LAN does not work. Limited connection.

    Read this post last night, and tried all the "solutions" Nothing has helped. Same problem exists.

    I shut down my machine often, so I am leaving it on, to see if my router restarts, or I lose internet after long periods on.

     

    I will try and follow this post and see if anything works...

    In the meantime I think I will get a wireless card in this desktop and see if that works (or helps). Not looking good since Jacob, above, is having wireless issues ><

    Wednesday, December 6, 2006 4:21 AM
  • Jacob,

    Is your laptop dual booted to an XP or Linux which works ok so that you can show that there is a Vista effect?

    Also, have you tried locking both the router connect negotiation to "802.11G only"

    RickW

     

    Wednesday, December 6, 2006 4:43 AM
  • Everything that's suggested:

    - Private Network
    - Discovery enabled (all green lights really)
    - Appropriate media folders shared through Media Sharing/Media Player 11

    The only connection to that particular link was the post by "accident" alluding to the advanced Vista networking features and proposed solution of a switch sitting in between the router and PC/360.  Also, he makes mention of problems specific to Linksys which is me, WRT55AG.


    Wednesday, December 6, 2006 2:53 PM
  • Hi RickW,

    My laptop is not dual bootable, so it's not currently possible for me to switch back and forth between operating systems.  What I do know is that:

    1. This problem with the router began when I installed Vista on the laptop.
    2. This problem only occurs when the laptop is running.  The router is fine when only the desktop is running, which is connected via Ethernet and also has Vista installed.
    3. So far, when I connect the laptop to the router via Ethernet and disable the wireless connection, the router has been fine.  However, I need to run in this configuration quite a bit more before suggesting that the problem is limited to Vista and wireless communications.

    The wireless card in my laptop is 802.11B, so I wouldn't want to set the router to 802.11G only.  It is currently set to "mixed", which would generally be the case for this router (e.g. in hotspots).  I could try setting it to 802.11B only, just to see if it helps as a temporary workaround.

    Jacob

    (Updated 12/8/2006) - I worked all day yesterday with the laptop connected by Ethernet to the router and experienced no problems.  This issue does seem to be confined to wireless communications, at least in my case.

    Wednesday, December 6, 2006 8:11 PM
  • This is a good opportunity for me to post.  I was involved in the compatibility testing of a lot of these routers, and I think I can offer some assistance.

    Vista does a lot more with networking than XP did; in addition there is a new driver model - so many wireless cards have brand-new drivers.  If you are having trouble with a router, I want to know - here are some steps that help a great deal:

    1. first of all, verify with a wired connection to the router.  This simplifies the configuration, since there are a whole host of other issues w.r.t wireless.  If it is working OK with a wired connection, but having trouble with wireless, that is a signficant data point and changes the focus of remedy.

    2. If you are having trouble with your wired connection, try disabling UPnP.  If UPnP is enabled on the router, Vista will use it much more heavily than XP ever did, and we've discovered that many routers have poor UPnP implementations.  I use "poor" in the sense that these implementations often leak memory, which can cause the router to either freeze up or reboot.  Remember, a router is a mini computer; and software on the router (the firmware) can have bugs which cause hangs, crashes, etc.  This is much more of a problem on routers that are over 1&1/2 years old.

    3. If UPnP is disabled, and you are STILL having problems with your router, go to the vendor's website and see if there is a firmware update.  Windows update does not do this for you.  Many companies (like SMC, for example) are no longer in the retail router business, and have quit supporting their routers.  Other devices have been end-of-lifed, and there is no further support.  Some of the older routers are still being maintained, and should have patches dated from the second half of 2006.  If your device is EOL'd, end-of-lifed, I'm afraid you're out of luck.

    Also, not all firmware updates improve!  These routers are very much a commodity business, and are totally cost-driven.  We have found through our testing, and one of the posters mentions this, that some updates introduce regressions.

    There is very little similarity between routers of smiliar model numbers - for example, the linksys wrt54g is totally different from the wrt55ag; indeed, there are 7 different hardware versions of the wrt54g, and each one has different firmware versions, so the matrix for just one device class - the wrt54g - is very large.  There are specific, known issues with the WRT54g v5, for example.

    All this being said, we went through a lot of work and fixed a lot of issues in Vista which did cause compatibility problems with routers.

    The next steps have to do with wireless issues - please verify with the wired tests, above, first.

    4. If the device is working OK with wired, but you have trouble with wireless, generally speaking it is a driver issue for your wireless card.   Since these drivers are 3rd party, there is not always a lot we can directly do about these.  Make sure you have the latest & greatest driver for your devices.

    5. Try the device at different security settings.  We tested with the lowest security (none) and the highest supported security the device supports.  Your mileage may vary; some of the older devices had problems with WPA2 AES security, but were OK unsecured.  If this is the case with your router, it's time to upgrade.

    Please run through these steps - a posting that says "my wrt54g v7 with firmware blah.blah.blah does not connect to my toshiba m4 with wireless using WPA TKIP" is way more usefull than "my router doesn't work with vista".

    Cheers,

    Karl

    Monday, December 11, 2006 7:57 PM
  • I've managed to stop most of the router restarts by disabling the upnp service, and turning off Network Discovery in the Network & Sharing Centre.

    The only time the router restarts now is very occasionally upon booting into Vista.
    Wednesday, December 20, 2006 11:20 AM
  • So has everyone gotten past this problem now?  I've been back on MCE 05 for a while now after I pulled all my hair out so just looking for the go ahead.  I did find a solution here: http://www.vista64.net/forums/showthread.php?s=fa513d44185b1c3bda2d30e9ae03828b&t=3130&page=2 to run [netsh int tcp set global autotuninglevel=disabled] but I can't test.
    Thursday, February 1, 2007 4:54 PM
  • I'm having the same issue with two different routers.  Have you found any way to fix it?
    Friday, February 16, 2007 8:41 PM
  •  

     

    Strange but ... on my return from vacation .... my dlink has only locked up once. I just don't get it. Aside from auto-updates I have not done anything to the system.

    RickW

     

     

     

    Friday, February 16, 2007 9:31 PM
  • your not alone, killed mine as well cannot network the system yet, got a new sys-link and did the same thing,begining to wonder if I made a VISTA oa a mistake.....any fixes out there?
    Tuesday, February 20, 2007 8:12 PM
  • Here's an update.  My laptop has a rather old Intel PRO/Wireless 2100 3B mini PCI adapter in it, totally unsupported now.  I disabled it and plugged in a more current Linksys WPC54G wireless adapter a few weeks ago and my router has not shown an error light since.

    Router: WRV54G
    PC Adapter: Motherboard's built-in Broadcom 10/100 Ethernet adapter (not using wireless)
    Laptop Adapter: Linksys WPC54G (works fine now)

    Jacob
    Tuesday, February 20, 2007 8:48 PM
  • Well guys its confirmed vista stinks. I had my two pcs at home networked with two xp computers. While i could share files, i had the problem with my linksys cable modem losing my internet connection daily and even updates did not solve the problem, so i suspect it might have somwething to do with my provider resetting the connection and booting me off causing me to reset to get back on.  

    When my main xp computer went i got a new vista one. While the problem with the unstable internet connection remained i now have the added problem that vista removed support for some networking features that xp had and my second computer will no longer connect to my home network and get an internet connection, although i can still share files.

    I went to the microsoft website to look up the steps to hook up a home network between vista and xp, surpise the directions were wrong. They posted vista directions instead of including directions how to reconfigure my xp for my new vista network set up. all it said was change my group name and my xp will magically work, not the case. for one with xp you need a network setup disk run on both pcs, vista does not.

    Vista removed some other features for networking as well, for instance in xp you could setup a new network for an always on broadband connection, that does not require a user name or password. vista removed this and it no longer supports a high speed connection that i can find, only dialup and dsl, isnt this a step backwards?

    i went to the store to check out new routers today, what a suprise most do not mention what versions of windows etc they support, the few that do, do not support vista. only one did a d-link at around a hundred a fifty bucks. i currently have a belikn and a linksys both worked on my xp network. belkin didn't list any routers on there website that supported vista. linksys did but in reality most models had updates coming soon, and everything that had updates did not work at all. There website does not support vista os for any of their automatic network setup tools. so all my routers are no good anymore. i guess when i can afford it i will be using d-link products instead, and hope that finally clears up all my networking problems.

    Wednesday, February 21, 2007 10:37 PM
  • did i mention at first my high speed connection at first was by itself and i never had a problem, then i got a three in one deal to save some bucks from comcast with my high speed, cable, and phone in one package. They put this big telephony modem in my house to combine all three. Afterwards i started losing my internet every few days, slowly it grow to me bing kicked off the web several times a day. The good news is now that i have vista i can clearly see that when i am kicked off its because of my provider. i have to reset things to get back on again. Unfortunately beyond the intermittine internet problem, vista has totally prevented me from networking because they removwed some important features that i stated in my last post.

    Wednesday, February 21, 2007 11:40 PM
  • I have an SMC Barracade-g  model = SMC2804WBR.  I turned off uPnP and have not had any more problems with router resets and lockups.
    Thursday, March 1, 2007 10:46 AM
  • check these out:

    http://lotherius.joeuser.com/index.asp?c=1&CID=1
    Vista causing issues with some Home/SOHO routers?
    I do a search for "vista router problem". I saw a huge list of hits - all of them right on the money with the symptoms. Turns out there's a Vista flaw with SPI (Stateful Packet Inspection) routers. A ZDNet Article Here: Link describes the troubles

    Here's the really good part He posted that a year ago. People have been struggling with this bug for a YEAR! Either that, or I'm wrong, and both my friend and I are having a different issue. I don't think so, however.

    (EDIT) Upon further research, this appears to be related to a bug with a new feature called "Scaling". Microsoft claims it is not a bug - it is a feature - and blames router manufacturers who don't support it. That of course is bull, since it wasn't a feature that needed supported previously, and Microsoft's inept handling of it broke a lot of routers, which aren't likely to ever be patched to support a totally new feature. For Beta 2 of Vista, they released a patch to fix the problem. And, sure enough, on my friend's computer, I actually got the disalogue box telling me it was "disabling" an incompatible feature (appropriately vague, that). Her connection was fine then - until the next reboot. Subsequent attempts to diagnose/repair the connection said nothing was wrong, but the behaviour remained. MS says this isn't a bug - they say it's fixed - but the fact remains that if I'm going to continue using Vista, I'm going to end up having to buy a new router. And I'm rather pissed off at that, because in this case it is Microsoft's fault things are broken, not the vendor. Routers should not be on the list of hardware that becomes incompatible with an OS upgrade!

    http://blogs.zdnet.com/Bott/?p=10
    A painful Vista networking bug
    ....a known bug in recent builds of Windows Vista affects a slew of recent-vintage routers....
    Trouble is, the new and improved TCP/IP stack in Windows Vista falls apart when it encounters an SPI-enabled router.

    from http://vistanoob.com/content/view/10/9/


     Microsoft has a brief knowledge base entry (http://support.microsoft.com/kb/932134) about the problem, that merely acknowledges that there are problems, and makes no attempt to offer a solution.
     
    There are really at least two seperate problems here. First, TCP/IP "Scaling" or "AutoTuning" breaks some routers. Second, Vista also breaks some routers with Stateful Packet Inspection. So far, I have found that I have to apply two seperate fixes - which hopefully are going to work long term (and as always, I'll update this FAQ if I find out otherwise).
     
    First: Disable AutoTuning:
    Open up a command prompt with Administrator Priveledges (go to the start menu, Accessories, and right click on "Command Prompt" and select "Run as Administrator").

    At the command prompt, type:
    netsh interface tcp set global autotuning=disabled
     
    You can verify the status before and after by using:
     
    netsh interface tcp show global
     
    You may wish to create a batch file that can be run upon login (as administrator), since this setting won't save across reboots.
     
    Second: Disable Stateful Packet Inspection (SPI) on your Router
    It is unfortunately beyond the scope of this article to explain how to do this for your particular router. If you need help doing this, contact someone at DSLReports.com and ask about your particular brand/model of router. If your router supports SPI, but does not offer a way to disable it, you may be out of luck and have to buy a new router. Thanks Microsoft!
     
    Ultimately, however, I am still having router issues, and the problems are not completely resolved!
    That's right - I don't have a complete fix or workaround yet. Every time I think I've got it going I come back to a hosed router that needs restarted.  There's something that I'm still missing in compatibility issues. If you're lucky, your router manufacturer will provide a firmware update for Vista compatibility.


    Friday, March 2, 2007 1:30 AM
  • I am having the same issues with my Linksys BEFW11S4 wireless router.  Once I wake my computer, after previously having established a working internet connection, it can no longer find my router, i.e. it is no longer even in my list of available networks.  I then have to reboot the router and then the computer locates it and can establish a connection. 

    My old computer (Compaq Presario running XP) recently died.  It worked great w/ this router & I rarely had any problems.  I recently purchased an HP Pavilion dv6000 running Vista and now I'm having these issues constantly.  I could shell out a few bucks and buy a new router, but I really don't want to.  I tried disabling uPnP but its had no effect.  Would sure appreciate if it anyone can share info on any tips or if they have resolved the issue.

    Saturday, March 10, 2007 8:06 PM
  • I'm in the same bizarre boat, here. Thought this would have been resolved by now. Westell Versalink 327w yields the same problems.

    I have to see what else can be turned off. uPnP is already off.

    I have an old Aiport around. I can ethernet that into my Westell, and then go wireless to that. Perhaps my old Apple technology can save my new Windows machine!

    If anyone ever finds a link to an authoritative fix, please post, as I doubt my Airport option is the best one.



    Monday, March 12, 2007 9:49 PM
  • I had a similar problem whereby vista kept on forcing my dlink dls-504t to restart.

    there was once i used the diagnose and repair to solve the issue, vista somehow knows how to solve this type of issue with old router.

    however, after i rebuilt my laptop, i couldn't get the auto-configuration to work again. so, i did it myself (based on research from the web).

    If you go to "manage network connection" and view the properties of the "local area connection", you will see that many items listed under "this connection uses the following items" and one of them is "internet protocol version 4".

    I uninstalled "link-layer topology discovery mapper i/o driver", "link-layer topology discovery responder", "QoS Packet Scheduler", and unchecked "internet protocol version 6".

    after done this, i never have router restarted issue anymore.

    hope this help.

    Saturday, March 31, 2007 8:45 AM
  • I am having a very similar problem. I upgraded to Vista from XP. I use a Cable connection with a D-Link VWR for my VOIP phone connection. Everytime I restart Vista for whatever reason it drops the network all together. I have to reset the modem and the router at least 3 times for Vista to indentify the Network. I've tried everything from c-prompt IPCONFIG options to Vista's little Network Fix tools and nothing. If I disconnect the router and go strait through the modem all works fine, however since I use Vonage for VOIP I have to have the router hooked up or I have no phone. I have read several of the Microsoft Forums and I see alot of router connection problems when people have purchased and upgarded to Vista.

     

    I have talked with my Dad who upgraded to Vista and he has the same issue, however he purchased a new computer for his Home office and it was pre loaded with Vista and everything works fine. I have been scouring the internet for weeks now looking for solutions and I found nothing but the same complaints I am making. It has something to do with Ultimate edition. All the others with the exception of Business work fine. Business has the same issues, which is ironic because the majority of businesses use routers.

     

    There will probably be another lawsuit against Microsoft soon for this, because it seems they are ignoring the problem. If anyone knows of a patch out there for Network Routers and Vista let me know. Or I guess I'll wait the 12 months until Microsoft decides to read their customer complaints and then spend another 8 months trying to fix it.

    Saturday, April 7, 2007 2:16 AM
  •  ZardoS42 wrote:

    Mike,

    This topic seems to have touched a raw nerve out there.

    If something in the updated Vista TCP/IP stack is freaking out popular consumer grade ADSL and 802.11 routers then it needs to be tracked down and squashed before the general consumer market release.

    RickW

     

     

     

    Yes Here here.

    Saturday, April 7, 2007 2:19 AM
  • I have the same setup as yours  Windows Vista, D-Link VWR and also the same problem you encountered. I got the solution, I called Vonage (VoIP provider for D-Link VWR) and they helped me configure the router. You don't need to configure your PC just the router. Call Vonage tech support  1-866-243-4357 for the configuration. www.vonage.com  - Carlo Hizon     maloney888@yahoo.com
    Sunday, June 17, 2007 2:24 PM
  • Format your harddrive.  Use the COA from your old computer and install Windows XP on your new one...problem solved.  Or abandon Windows altogeather and run Linux again problem solved.  When enough people respond in this manner to the problem, MS may do something about their buggy OS instead of having us pay for the priviledge of beta testing this POS.
    Sunday, July 29, 2007 5:53 PM
  • Not sure if this is the same issue. I had a link sys cable modem/router and it kept kickin me off my internet connection. I thought it was my cable providers problem but it ended up being a link sys problem. you may want to replace the ac adapter, this sometimes can be defective. I switched to a modem my cable provider provides and a dlink router. I have not had any issues since with dropped internet. I can not get my vista to recognize my networked hardrive. oh well vista sucks.

    Monday, February 18, 2008 4:40 PM
  • Wednesday, May 28, 2008 6:55 PM
  • I have the same Vista annoyance. I am also using an SMC Barricade router. Each time Vista starts up or comes out of hibernation, it resets the router and everything else loses their network connection temporarily. I just turned UPnP off on the router as suggested in one of these posts, unplugged the network cable on the Vista laptop and plugged it back in and the other computers didnt lose their network connection this time. YES! Thank you. STUPID Vista. Dont tell its not a Vista BUG if the Linux, XP, Windows 2000 all work fine.
    Monday, December 15, 2008 1:58 AM
  • I have the D-Link router, and for some reason I keep pulling .100 as an I.P for my vista machine. This causes an identity crises with the router. Causing this machine to loose Internet every so often. Think that is strange.... When I pick up the laptop and move to another room, vista refuses to see any networks available. LOL. So I have to reboot my whole system as a cold boot. Then it Vista says YAY!!!! We found networks!!! Does this mean my router is not Vista ready, or is it Vista is not Vista ready.

    Wednesday, January 14, 2009 4:36 PM