| ECS Home Automation and Security Archives |
| Subject: From: Date: | RE: [ecs] Win update killed my LAN ? Mark Gilmore Thu, 19 Feb 2004 19:23:27 -0800 |
probably not, as both worked before and still comm with each other. signing off for the night. thanks, At 07:20 PM 2/19/2004 -0800, you wrote: >The entries you need are there. > >Any chance that the other PCs are on a different subnet - this one is on >255.255.255.0 > > > >-----Original Message----- >From: Mark Gilmore [mailto:mark@OmnipotenceSoftware.com] >Sent: Thursday, February 19, 2004 7:14 PM >To: ecs@netbloc.com >Subject: RE: [ecs] Win update killed my LAN ? > >Here 'tis: >======================================================================== >=== >Interface List >0x1 ........................... MS TCP Loopback interface >0x2 ...00 40 ca 49 08 22 ...... Intel(R) PRO/100 VE Network Connection - > >Packet Scheduler Miniport >0x10004 ...00 80 ae 00 00 01 ...... Satellite USB Device - Packet >Scheduler >Miniport >======================================================================== >=== >======================================================================== >=== >Active Routes: >Network Destination Netmask Gateway Interface >Metric > 0.0.0.0 0.0.0.0 66.82.157.41 10.4.65.111 >1 > 10.4.65.0 255.255.255.0 10.4.65.111 10.4.65.111 >30 > 10.4.65.111 255.255.255.255 127.0.0.1 127.0.0.1 >30 > 10.255.255.255 255.255.255.255 10.4.65.111 10.4.65.111 >30 > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 >1 > 192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1 >30 > 192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 >30 > 192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 >30 > 224.0.0.0 240.0.0.0 10.4.65.111 10.4.65.111 >30 > 224.0.0.0 240.0.0.0 192.168.1.1 192.168.1.1 >30 > 255.255.255.255 255.255.255.255 10.4.65.111 10.4.65.111 >1 > 255.255.255.255 255.255.255.255 192.168.1.1 192.168.1.1 >1 >Default Gateway: 66.82.157.41 >======================================================================== >=== >Persistent Routes: > None > >At 07:08 PM 2/19/2004 -0800, you wrote: > > >Routing table you can get as follows: > > > >Start->run > >Type "cmd" in the box > > > >This gets you a dos box on the screen. > > > >Then "route print" > > > >That's what we need to see next. Not expecting to find anything given > >this info below, but we need to check it. > > > >-----Original Message----- > >From: Mark Gilmore [mailto:mark@OmnipotenceSoftware.com] > >Sent: Thursday, February 19, 2004 6:54 PM > >To: ecs@netbloc.com > >Subject: RE: [ecs] Win update killed my LAN ? > > > >Hi Martin, > >IPCONFIG /ALL output (not sure if this is a "routing table" :-)): > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : a > > Primary Dns Suffix . . . . . . . : > > Node Type . . . . . . . . . . . . : Unknown > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > Ethernet adapter Local Area Connection 9: > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Intel(R) PRO/100 >VE > > > >Network Connection > > Physical Address. . . . . . . . . : 00-40-CA-49-08-22 > > Dhcp Enabled. . . . . . . . . . . : No > > IP Address. . . . . . . . . . . . : 192.168.1.1 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : > > Ethernet adapter DIRECWAY Satellite Connection: > > Connection-specific DNS Suffix . : direcway.com > > Description . . . . . . . . . . . : Satellite USB > >Device > > Physical Address. . . . . . . . . : 00-80-AE-00-00-01 > > Dhcp Enabled. . . . . . . . . . . : No > > IP Address. . . . . . . . . . . . : 10.4.65.111 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : 66.82.157.41 > > DNS Servers . . . . . . . . . . . : 198.77.116.8 > > > > > >Other PC IPs are 192.168.1.2 and 192.168.1.3. > > > >For both of these IPs, TRACERT repeated timeouts (as do PING to same > >IPs). > > > >Thanks, > > > >At 06:21 PM 2/19/2004 -0800, you wrote: > > > > >Can you show us your routing table? > > > > > >And the IP address of one of the other PCs? > > >Also, a tracert might help. > > > > > > > > >(Route print at a c: prompt) > > > > > >-----Original Message----- > > >From: Mark Gilmore [mailto:mark@OmnipotenceSoftware.com] > > >Sent: Thursday, February 19, 2004 6:20 PM > > >To: ecs@netbloc.com > > >Subject: RE: [ecs] Win update killed my LAN ? > > > > > >Hi Keith, > > >I tried that, but Win said that none were available. > > >But I verified that all the LAN's driver files were at least a year > >old. > > > > > >At 09:13 PM 2/19/2004 -0500, you wrote: > > > > > > >Hi Mark. Man..thats a bummer. Uh, I too ran the updates but Im on > > >dialup so > > > >did not notice anything. CAn you roll back? > > > > > > > >Good luck..Keith > > > > > > > >-----Original Message----- > > > >From: Mark Gilmore [mailto:mark@OmnipotenceSoftware.com] > > > >Sent: Thursday, February 19, 2004 9:07 PM > > > >To: ecsl@netbloc.com; ecs@netbloc.com > > > >Subject: [ecs] Win update killed my LAN ? > > > > > > > > > > > >Hi all, > > > >Any FYI and a question: > > > >After installing the latest "critical update" from Gates, > > > >I can no longer access either of the other PCs on my LAN. > > > > > > > >Pings fail in both directions. > > > > > > > >I noticed that the firewall on the Local Area Connection was >enabled. > > > >I *think* the update did this, but not sure. > > > >I disabled it early on. > > > > > > > >I removed/re-installed the LAN, reset my TCP/IP address to > >192.168.1.1 > > >(as > > > >I always do), > > > >updated the driver, and powered down *numerous* times. > > > > > > > >The ethernet connection LEDs on the PC and the hub are both lit. > > > > > > > >I *can* ping to myself (192.168.1.1), so it appears that all > > >connections > > > >are sound. > > > >Plus, the *other* 2 PCs on the LAN can communicate fine. > > > > > > > >Nothing I do has any effect. > > > >Any suggestions would be greatly appreciated. > > > >Thanks, > > > > > > > >Mark Gilmore > > > >http://OmnipotenceSoftware.com > > > > > > > > > > > > > > > >--- > > > >Incoming mail is certified Virus Free. > > > >Checked by AVG anti-virus system (http://www.grisoft.com). > > > >Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004 > > > > > >Mark Gilmore > > >http://OmnipotenceSoftware.com > > > > > > > > > > > > > > >--- > > >Incoming mail is certified Virus Free. > > >Checked by AVG anti-virus system (http://www.grisoft.com). > > >Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004 > > > >Mark Gilmore > >http://OmnipotenceSoftware.com > > > > > > > > > >--- > >Incoming mail is certified Virus Free. > >Checked by AVG anti-virus system (http://www.grisoft.com). > >Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004 > >Mark Gilmore >http://OmnipotenceSoftware.com > > > > >--- >Incoming mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004 Mark Gilmore http://OmnipotenceSoftware.com
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004