Home / user-220834

austinian's questions

Martin Hope
austinian
Asked: 2020-09-22 16:16:03 +0800 CST
  • 2

I'm currently trying to fetch old files off of a box of floppy disks and many of the files fail on the first try but copy successfully after a few tries, I'm assuming because the internal cleaning mechanism is doing its job or something.

I'm using robocopy to copy the files, but no matter what I set the /r: flag to, it only tries once. I've used robocopy in the past to read files off damaged optical media and skip the errors after only a couple of tries, but that was a while ago.

windows floppy robocopy
Martin Hope
austinian
Asked: 2015-01-03 13:01:48 +0800 CST
  • 7

Right now, we've got a business critical application that installs an Outlook add-in. It is a bit slow to load, which makes Outlook 2013 kill it after a few runs, but I've mitigated the issue of Outlook 2013 killing the add-in by using the Office 2013 Group Policy Administrative Templates "List of managed add-ins" policy.

I don't see a similar policy in the 2007/2010 templates, and have to remove the resiliency key from the user's profile whenever the key gets added for whatever reason. Is there a way that I can replicate the functionality of the 2013 policy for 2007 and 2010, or even disable resiliency entirely if granularity is not an option? If so, how?

I've found several ways to selectively kill the plugin-specific resiliency subkey automatically, but this still requires the user to restart outlook if the plugin doesn't load because it was disabled automatically.

outlook-2010
Martin Hope
austinian
Asked: 2014-12-30 08:11:55 +0800 CST
  • 4

I'm using the Windows Update Agent to install WMF 4.0 on my Windows 7 workstations. I unpacked the MSU to get the cab files and install them using DISM online mode with the following commands (one for x86, one for x64 systems)

dism.exe /online /add-package /packagepath:.\Windows6.1-KB2872035-x86.cab /packagepath:.\Windows6.1-KB2872047-x86.cab /packagepath:.\Windows6.1-KB2819745-x86.cab /quiet /norestart
dism.exe /online /add-package /packagepath:.\Windows6.1-KB2809215-x64.cab /packagepath:.\Windows6.1-KB2872035-x64.cab /packagepath:.\Windows6.1-KB2872047-x64.cab /packagepath:.\Windows6.1-KB2819745-x64.cab /quiet /norestart

I get 0x800F081E as a return code, which isn't a Windows Error Message, so I think it's either a message from DISM or WIMGAPI, from what I found at http://msdn.microsoft.com/en-us/library/windows/desktop/hh825833.aspx. Restarting the system after receiving this error code results in a successful installation on all systems in testing, so I've flagged this return value to tell the Windows Update Agent that the system needs a reboot if that error code is detected. I just don't know what this message is supposed to be telling me, so I don't know if there's any action I need to take post-installation, or if I need to modify the command to make it work better.

windows
Martin Hope
austinian
Asked: 2014-12-04 07:47:25 +0800 CST
  • 8

Like the title says, I've got a Dell M6600, running Windows 7, that connects to the network just fine, I can use it to browse the web, including https://officesetup.getmicrosoftkey.com/, I can connect to it via RDP, it was joined to the domain (more below), no noticeable slowness in the network connection. The issue is that the active networks are reporting Access Type: No internet access, and I can't connect to some things, like I can't activate Office 2013 because "We are unable to connect right now. Please check your network and try again later". No software firewall is enabled.

Here's what I've tried:

  • ipconfig release & ipconfig renew
  • run netsh int ip reset c:\temp\resetlog.txt (the log never gets generated)
  • Connect with Wired Ethernet only
  • Connect with WiFi only
  • Uninstall/reinstall the network adapters using the management console
  • Wade through a swath of unhelpful google results like route delete 0.0.0.0 if 11
  • Attempt a domain rejoin, got as far as removing the computer from the domain, but can't readd, as "The network location cannot be reached" (I can still RDP to it at this point using local creds, there are gpupdate failure events that should've told me this would fail)
  • Check NCSI issues: navigation to http://www.msftncsi.com/ncsi.txt in IE results in a page with the text: "Microsoft NCSI", dns.msftncsi.com resolves correctly
  • Pinging the DNS server results in request timed out, but performing nslookup works just fine using said DNS server.
  • changed the IP address of the DHCP reservation to a known unused IP address to check for IP address conflicts
  • uninstalled AV software
  • changing switch port, switch for wired access had no effect, Dynamic Address Tables correctly updated when switched to a different port (the ports on the switches have the same configurations for most of the other successfully communicating computers on the network)
  • pinging DNS server works now, was failing, even though it was working fine with nslookup when pinging

(computer/domain names redacted in the following, some truncated for brevity) ipconfig /all:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : computer
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : contoso.com

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : contoso.com
   Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
   Physical Address. . . . . . . . . : D0-67-E5-2F-D2-20
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 172.17.2.240(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, December 03, 2014 10:11:41 AM
   Lease Expires . . . . . . . . . . : Friday, December 05, 2014 10:14:57 AM
   Default Gateway . . . . . . . . . : 172.17.2.1
   DHCP Server . . . . . . . . . . . : 172.17.2.22
   DNS Servers . . . . . . . . . . . : 172.17.2.22
                                       172.17.2.21
   Primary WINS Server . . . . . . . : 172.17.2.22
   Secondary WINS Server . . . . . . : 172.17.2.24
   NetBIOS over Tcpip. . . . . . . . : Enabled

route print: (normal, removed to post wireshark)

wireshark with filter bootp.option.dhcp during ipconfig /renew & ipconfig /release & ipconfig /renew:

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1265 54.049678000   172.17.2.100          68          172.17.2.22           67               DHCP     348    DHCP Request  - Transaction ID 0xd64657df

Frame 1265: 348 bytes on wire (2784 bits), 348 bytes captured (2784 bits) on interface 0
Ethernet II, Src: Dell_2f:d2:20 (d0:67:e5:2f:d2:20), Dst: Dell_5e:94:e3 (84:2b:2b:5e:94:e3)
Internet Protocol Version 4, Src: 172.17.2.100 (172.17.2.100), Dst: 172.17.2.22 (172.17.2.22)
User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67)
Bootstrap Protocol (Request)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0xd64657df
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 172.17.2.100 (172.17.2.100)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Request)
        Length: 1
        DHCP: Request (3)
    Option: (61) Client identifier
        Length: 7
        Hardware type: Ethernet (0x01)
        Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Option: (12) Host Name
        Length: 11
        Host Name: computer
    Option: (81) Client Fully Qualified Domain Name
        Length: 14
        Flags: 0x00
        0000 .... = Reserved flags: 0x00
        .... 0... = Server DDNS: Some server updates
        .... .0.. = Encoding: ASCII encoding
        .... ..0. = Server overrides: No override
        .... ...0 = Server: Client
        A-RR result: 0
        PTR-RR result: 0
        Client name: computer
    Option: (60) Vendor class identifier
        Length: 8
        Vendor class identifier: MSFT 5.0
    Option: (55) Parameter Request List
        Length: 12
        Parameter Request List Item: (1) Subnet Mask
        Parameter Request List Item: (15) Domain Name
        Parameter Request List Item: (3) Router
        Parameter Request List Item: (6) Domain Name Server
        Parameter Request List Item: (44) NetBIOS over TCP/IP Name Server
        Parameter Request List Item: (46) NetBIOS over TCP/IP Node Type
        Parameter Request List Item: (47) NetBIOS over TCP/IP Scope
        Parameter Request List Item: (31) Perform Router Discover
        Parameter Request List Item: (33) Static Route
        Parameter Request List Item: (121) Classless Static Route
        Parameter Request List Item: (249) Private/Classless Static Route (Microsoft)
        Parameter Request List Item: (43) Vendor-Specific Information
    Option: (255) End
        Option End: 255

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1268 54.050521000   172.17.2.22           67          172.17.2.100          68               DHCP     381    DHCP ACK      - Transaction ID 0xd64657df

Frame 1268: 381 bytes on wire (3048 bits), 381 bytes captured (3048 bits) on interface 0
Ethernet II, Src: Dell_5e:94:e3 (84:2b:2b:5e:94:e3), Dst: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
Internet Protocol Version 4, Src: 172.17.2.22 (172.17.2.22), Dst: 172.17.2.100 (172.17.2.100)
User Datagram Protocol, Src Port: 67 (67), Dst Port: 68 (68)
Bootstrap Protocol (ACK)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0xd64657df
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 172.17.2.100 (172.17.2.100)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (ACK)
        Length: 1
        DHCP: ACK (5)
    Option: (58) Renewal Time Value
        Length: 4
        Renewal Time Value: (86400s) 1 day
    Option: (59) Rebinding Time Value
        Length: 4
        Rebinding Time Value: (151200s) 1 day, 18 hours
    Option: (51) IP Address Lease Time
        Length: 4
        IP Address Lease Time: (172800s) 2 days
    Option: (54) DHCP Server Identifier
        Length: 4
        DHCP Server Identifier: 172.17.2.22 (172.17.2.22)
    Option: (1) Subnet Mask
        Length: 4
        Subnet Mask: 255.255.255.0 (255.255.255.0)
    Option: (81) Client Fully Qualified Domain Name
        Length: 3
        Flags: 0x00
        0000 .... = Reserved flags: 0x00
        .... 0... = Server DDNS: Some server updates
        .... .0.. = Encoding: ASCII encoding
        .... ..0. = Server overrides: No override
        .... ...0 = Server: Client
        A-RR result: 255
        PTR-RR result: 255
    Option: (15) Domain Name
        Length: 9
        Domain Name: contoso.com
    Option: (3) Router
        Length: 4
        Router: 172.17.2.1 (172.17.2.1)
    Option: (6) Domain Name Server
        Length: 8
        Domain Name Server: 172.17.2.22 (172.17.2.22)
        Domain Name Server: 172.17.2.21 (172.17.2.21)
    Option: (44) NetBIOS over TCP/IP Name Server
        Length: 8
        NetBIOS over TCP/IP Name Server: 172.17.2.22 (172.17.2.22)
        NetBIOS over TCP/IP Name Server: 172.17.2.24 (172.17.2.24)
    Option: (46) NetBIOS over TCP/IP Node Type
        Length: 1
        NetBIOS over TCP/IP Node Type: H-node (8)
    Option: (121) Classless Static Route
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (249) Private/Classless Static Route (Microsoft)
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (255) End
        Option End: 255

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1280 54.115690000   172.17.2.100          68          172.17.2.22           67               DHCP     342    DHCP Release  - Transaction ID 0x18a9cba3

Frame 1280: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0
Ethernet II, Src: Dell_2f:d2:20 (d0:67:e5:2f:d2:20), Dst: Dell_5e:94:e3 (84:2b:2b:5e:94:e3)
Internet Protocol Version 4, Src: 172.17.2.100 (172.17.2.100), Dst: 172.17.2.22 (172.17.2.22)
User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67)
Bootstrap Protocol (Release)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x18a9cba3
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 172.17.2.100 (172.17.2.100)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Release)
        Length: 1
        DHCP: Release (7)
    Option: (54) DHCP Server Identifier
        Length: 4
        DHCP Server Identifier: 172.17.2.22 (172.17.2.22)
    Option: (61) Client identifier
        Length: 7
        Hardware type: Ethernet (0x01)
        Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Option: (255) End
        Option End: 255
    Padding

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1372 59.175867000   0.0.0.0               68          255.255.255.255       67               DHCP     342    DHCP Discover - Transaction ID 0x97a2aa5c

Frame 1372: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0
Ethernet II, Src: Dell_2f:d2:20 (d0:67:e5:2f:d2:20), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67)
Bootstrap Protocol (Discover)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x97a2aa5c
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Discover)
        Length: 1
        DHCP: Discover (1)
    Option: (61) Client identifier
        Length: 7
        Hardware type: Ethernet (0x01)
        Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Option: (50) Requested IP Address
        Length: 4
        Requested IP Address: 172.17.2.100 (172.17.2.100)
    Option: (12) Host Name
        Length: 11
        Host Name: computer
    Option: (60) Vendor class identifier
        Length: 8
        Vendor class identifier: MSFT 5.0
    Option: (55) Parameter Request List
        Length: 12
        Parameter Request List Item: (1) Subnet Mask
        Parameter Request List Item: (15) Domain Name
        Parameter Request List Item: (3) Router
        Parameter Request List Item: (6) Domain Name Server
        Parameter Request List Item: (44) NetBIOS over TCP/IP Name Server
        Parameter Request List Item: (46) NetBIOS over TCP/IP Node Type
        Parameter Request List Item: (47) NetBIOS over TCP/IP Scope
        Parameter Request List Item: (31) Perform Router Discover
        Parameter Request List Item: (33) Static Route
        Parameter Request List Item: (121) Classless Static Route
        Parameter Request List Item: (249) Private/Classless Static Route (Microsoft)
        Parameter Request List Item: (43) Vendor-Specific Information
    Option: (255) End
        Option End: 255
    Padding

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1373 59.176223000   172.17.2.22           67          255.255.255.255       68               DHCP     376    DHCP Offer    - Transaction ID 0x97a2aa5c

Frame 1373: 376 bytes on wire (3008 bits), 376 bytes captured (3008 bits) on interface 0
Ethernet II, Src: Dell_5e:94:e3 (84:2b:2b:5e:94:e3), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 172.17.2.22 (172.17.2.22), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: 67 (67), Dst Port: 68 (68)
Bootstrap Protocol (Offer)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x97a2aa5c
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 172.17.2.100 (172.17.2.100)
    Next server IP address: 172.17.2.22 (172.17.2.22)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Offer)
        Length: 1
        DHCP: Offer (2)
    Option: (1) Subnet Mask
        Length: 4
        Subnet Mask: 255.255.255.0 (255.255.255.0)
    Option: (58) Renewal Time Value
        Length: 4
        Renewal Time Value: (86400s) 1 day
    Option: (59) Rebinding Time Value
        Length: 4
        Rebinding Time Value: (151200s) 1 day, 18 hours
    Option: (51) IP Address Lease Time
        Length: 4
        IP Address Lease Time: (172800s) 2 days
    Option: (54) DHCP Server Identifier
        Length: 4
        DHCP Server Identifier: 172.17.2.22 (172.17.2.22)
    Option: (15) Domain Name
        Length: 9
        Domain Name: contoso.com
    Option: (3) Router
        Length: 4
        Router: 172.17.2.1 (172.17.2.1)
    Option: (6) Domain Name Server
        Length: 8
        Domain Name Server: 172.17.2.22 (172.17.2.22)
        Domain Name Server: 172.17.2.21 (172.17.2.21)
    Option: (44) NetBIOS over TCP/IP Name Server
        Length: 8
        NetBIOS over TCP/IP Name Server: 172.17.2.22 (172.17.2.22)
        NetBIOS over TCP/IP Name Server: 172.17.2.24 (172.17.2.24)
    Option: (46) NetBIOS over TCP/IP Node Type
        Length: 1
        NetBIOS over TCP/IP Node Type: H-node (8)
    Option: (121) Classless Static Route
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (249) Private/Classless Static Route (Microsoft)
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (255) End
        Option End: 255

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1374 59.176534000   0.0.0.0               68          255.255.255.255       67               DHCP     360    DHCP Request  - Transaction ID 0x97a2aa5c

Frame 1374: 360 bytes on wire (2880 bits), 360 bytes captured (2880 bits) on interface 0
Ethernet II, Src: Dell_2f:d2:20 (d0:67:e5:2f:d2:20), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67)
Bootstrap Protocol (Request)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x97a2aa5c
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Request)
        Length: 1
        DHCP: Request (3)
    Option: (61) Client identifier
        Length: 7
        Hardware type: Ethernet (0x01)
        Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Option: (50) Requested IP Address
        Length: 4
        Requested IP Address: 172.17.2.100 (172.17.2.100)
    Option: (54) DHCP Server Identifier
        Length: 4
        DHCP Server Identifier: 172.17.2.22 (172.17.2.22)
    Option: (12) Host Name
        Length: 11
        Host Name: computer
    Option: (81) Client Fully Qualified Domain Name
        Length: 14
        Flags: 0x00
        0000 .... = Reserved flags: 0x00
        .... 0... = Server DDNS: Some server updates
        .... .0.. = Encoding: ASCII encoding
        .... ..0. = Server overrides: No override
        .... ...0 = Server: Client
        A-RR result: 0
        PTR-RR result: 0
        Client name: computer
    Option: (60) Vendor class identifier
        Length: 8
        Vendor class identifier: MSFT 5.0
    Option: (55) Parameter Request List
        Length: 12
        Parameter Request List Item: (1) Subnet Mask
        Parameter Request List Item: (15) Domain Name
        Parameter Request List Item: (3) Router
        Parameter Request List Item: (6) Domain Name Server
        Parameter Request List Item: (44) NetBIOS over TCP/IP Name Server
        Parameter Request List Item: (46) NetBIOS over TCP/IP Node Type
        Parameter Request List Item: (47) NetBIOS over TCP/IP Scope
        Parameter Request List Item: (31) Perform Router Discover
        Parameter Request List Item: (33) Static Route
        Parameter Request List Item: (121) Classless Static Route
        Parameter Request List Item: (249) Private/Classless Static Route (Microsoft)
        Parameter Request List Item: (43) Vendor-Specific Information
    Option: (255) End
        Option End: 255

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1375 59.177078000   172.17.2.22           67          255.255.255.255       68               DHCP     381    DHCP ACK      - Transaction ID 0x97a2aa5c

Frame 1375: 381 bytes on wire (3048 bits), 381 bytes captured (3048 bits) on interface 0
Ethernet II, Src: Dell_5e:94:e3 (84:2b:2b:5e:94:e3), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 172.17.2.22 (172.17.2.22), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: 67 (67), Dst Port: 68 (68)
Bootstrap Protocol (ACK)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x97a2aa5c
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 172.17.2.100 (172.17.2.100)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (ACK)
        Length: 1
        DHCP: ACK (5)
    Option: (58) Renewal Time Value
        Length: 4
        Renewal Time Value: (86400s) 1 day
    Option: (59) Rebinding Time Value
        Length: 4
        Rebinding Time Value: (151200s) 1 day, 18 hours
    Option: (51) IP Address Lease Time
        Length: 4
        IP Address Lease Time: (172800s) 2 days
    Option: (54) DHCP Server Identifier
        Length: 4
        DHCP Server Identifier: 172.17.2.22 (172.17.2.22)
    Option: (1) Subnet Mask
        Length: 4
        Subnet Mask: 255.255.255.0 (255.255.255.0)
    Option: (81) Client Fully Qualified Domain Name
        Length: 3
        Flags: 0x00
        0000 .... = Reserved flags: 0x00
        .... 0... = Server DDNS: Some server updates
        .... .0.. = Encoding: ASCII encoding
        .... ..0. = Server overrides: No override
        .... ...0 = Server: Client
        A-RR result: 255
        PTR-RR result: 255
    Option: (15) Domain Name
        Length: 9
        Domain Name: contoso.com
    Option: (3) Router
        Length: 4
        Router: 172.17.2.1 (172.17.2.1)
    Option: (6) Domain Name Server
        Length: 8
        Domain Name Server: 172.17.2.22 (172.17.2.22)
        Domain Name Server: 172.17.2.21 (172.17.2.21)
    Option: (44) NetBIOS over TCP/IP Name Server
        Length: 8
        NetBIOS over TCP/IP Name Server: 172.17.2.22 (172.17.2.22)
        NetBIOS over TCP/IP Name Server: 172.17.2.24 (172.17.2.24)
    Option: (46) NetBIOS over TCP/IP Node Type
        Length: 1
        NetBIOS over TCP/IP Node Type: H-node (8)
    Option: (121) Classless Static Route
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (249) Private/Classless Static Route (Microsoft)
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (255) End
        Option End: 255

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1431 62.210304000   172.17.2.100          68          255.255.255.255       67               DHCP     342    DHCP Inform   - Transaction ID 0xd46e0a9b

Frame 1431: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0
Ethernet II, Src: Dell_2f:d2:20 (d0:67:e5:2f:d2:20), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 172.17.2.100 (172.17.2.100), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67)
Bootstrap Protocol (Inform)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0xd46e0a9b
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 172.17.2.100 (172.17.2.100)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Inform)
        Length: 1
        DHCP: Inform (8)
    Option: (61) Client identifier
        Length: 7
        Hardware type: Ethernet (0x01)
        Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Option: (12) Host Name
        Length: 11
        Host Name: computer
    Option: (60) Vendor class identifier
        Length: 8
        Vendor class identifier: MSFT 5.0
    Option: (55) Parameter Request List
        Length: 13
        Parameter Request List Item: (1) Subnet Mask
        Parameter Request List Item: (15) Domain Name
        Parameter Request List Item: (3) Router
        Parameter Request List Item: (6) Domain Name Server
        Parameter Request List Item: (44) NetBIOS over TCP/IP Name Server
        Parameter Request List Item: (46) NetBIOS over TCP/IP Node Type
        Parameter Request List Item: (47) NetBIOS over TCP/IP Scope
        Parameter Request List Item: (31) Perform Router Discover
        Parameter Request List Item: (33) Static Route
        Parameter Request List Item: (121) Classless Static Route
        Parameter Request List Item: (249) Private/Classless Static Route (Microsoft)
        Parameter Request List Item: (43) Vendor-Specific Information
        Parameter Request List Item: (252) Private/Proxy autodiscovery
    Option: (255) End
        Option End: 255
    Padding

No.     Time           Source                Source Port Destination           Destination Port Protocol Length Info
   1432 62.210721000   172.17.2.22           67          172.17.2.100          68               DHCP     365    DHCP ACK      - Transaction ID 0xd46e0a9b

Frame 1432: 365 bytes on wire (2920 bits), 365 bytes captured (2920 bits) on interface 0
Ethernet II, Src: Dell_5e:94:e3 (84:2b:2b:5e:94:e3), Dst: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
Internet Protocol Version 4, Src: 172.17.2.22 (172.17.2.22), Dst: 172.17.2.100 (172.17.2.100)
User Datagram Protocol, Src Port: 67 (67), Dst Port: 68 (68)
Bootstrap Protocol (ACK)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0xd46e0a9b
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 172.17.2.100 (172.17.2.100)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: Dell_2f:d2:20 (d0:67:e5:2f:d2:20)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (ACK)
        Length: 1
        DHCP: ACK (5)
    Option: (54) DHCP Server Identifier
        Length: 4
        DHCP Server Identifier: 172.17.2.22 (172.17.2.22)
    Option: (1) Subnet Mask
        Length: 4
        Subnet Mask: 255.255.255.0 (255.255.255.0)
    Option: (43) Vendor-Specific Information
        Length: 5
        Value: dc034e4150
    Option: (15) Domain Name
        Length: 9
        Domain Name: contoso.com
    Option: (3) Router
        Length: 4
        Router: 172.17.2.1 (172.17.2.1)
    Option: (6) Domain Name Server
        Length: 8
        Domain Name Server: 172.17.2.22 (172.17.2.22)
        Domain Name Server: 172.17.2.21 (172.17.2.21)
    Option: (44) NetBIOS over TCP/IP Name Server
        Length: 8
        NetBIOS over TCP/IP Name Server: 172.17.2.22 (172.17.2.22)
        NetBIOS over TCP/IP Name Server: 172.17.2.24 (172.17.2.24)
    Option: (46) NetBIOS over TCP/IP Node Type
        Length: 1
        NetBIOS over TCP/IP Node Type: H-node (8)
    Option: (121) Classless Static Route
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (249) Private/Classless Static Route (Microsoft)
        Length: 8
        Subnet/MaskWidth-Router: 172.17.3.0/24-172.17.2.2
    Option: (255) End
        Option End: 255
networking
Martin Hope
austinian
Asked: 2014-11-13 08:34:55 +0800 CST
  • 0

At least sometimes, when our Exchange server gets rebooted for whatever reason, the ValidPorts data at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy resets to using only the bare machine name and the FQDN for the local domain, but loses the additional outside domain information added so that outlook-anywhere will work by accessing the external domain name.

I'm not sure what's causing this issue, and my google-fu is failing to find anything useful so far.

I could, as a workaround, use a script to make sure that the data for the key/value is correct whenever the server starts up, but that doesn't get to the root of the issue and could have unintended consequences.

The computer is running Windows Server 2008 R2 and Exchange 2007 SP3

EDIT: I just edited this key a few hours ago and came back to the server to see that it had changed WITHOUT a reboot or any software/patches being installed. I'm looking through scheduled tasks and RSOP now for clues.

EDIT: I don't see anything in RSOP or Tasks that points to why this key keeps reverting. Logoff/logon doesn't seem to be the cause either.

EDIT: Triple checking my settings: Outlook Anywhere was initially configured using the Exchange Management Console. In the console, if I go to server configuration -> Client Access, go to the server properties -> Outlook Anywhere tab, the External host name field is populated correctly.

windows-server-2008-r2
Martin Hope
austinian
Asked: 2014-10-30 11:52:06 +0800 CST
  • 1

So, I was just reviewing my workstations for software they're not supposed to have, and came across traces of MSXML 4.0 still being on some of my machines.

These are all Windows 7 machines, they had MSXML 4.0 installed on them and I issued the following commands to remove it:

Uninstall MSXML 4.0 SP2 (KB954430) 4.20.9870.0: 

%windir%\System32\msiexec.exe /x {86493ADD-824D-4B8E-BD72-8C5DCDC52A71} /qn /norestart

Uninstall MSXML 4.0 SP2 (KB973688) 4.20.9876.0: 

%windir%\System32\msiexec.exe /x {F662A8E6-F4DC-41A2-901E-8C11F044BDEC} /qn /norestart

(These were the only two versions I found on my network at the time of removal)

Now, in WSUS, I’m still seeing these as being installed, and when I look at the machines themselves, I found the following files on the computers (there's a tab between columns):

Path    Version Product 
C:\Windows\winsxs\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\msxml4.dll 4.20.9818.0    Microsoft(R) MSXML 4.0 SP 2 
C:\Windows\winsxs\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\msxml4.dll 4.20.9876.0    Microsoft(R) MSXML 4.0 SP 2 
C:\Windows\winsxs\x86_microsoft.msxml2r_6bd6b9abf345378f_4.1.0.0_none_3658456fda6654f6\msxml4r.dll 4.10.9404.0  Microsoft(R) MSXML 4.0 SP1 
C:\Windows\winsxs\x86_microsoft.msxml2r_6bd6b9abf345378f_4.1.1.0_none_365945b9da656e4d\msxml4r.dll 4.10.9404.0  Microsoft(R) MSXML 4.0 SP1 
C:\Windows\SysWOW64\msxml4.dll  4.20.9876.0 Microsoft(R) MSXML 4.0 SP 2 
C:\Windows\SysWOW64\msxml4r.dll 4.10.9404.0 Microsoft(R) MSXML 4.0 SP1

The registry is also littered with references to syswow64\msxml4.dll and syswow64\msxml4r.dll in the following locations (“\…” indicates several subkeys contain references): 

HKLM\SOFTWARE\Classes\TypeLib\{F5078F18-C551-11D3-89B9-0000F81FE221}\4.0 
HKLM\SOFTWARE\Classes\Wow6432Node\CLSID\... 
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\... 
HKLM\SOFTWARE\Wow6432Node\Classes\CLSID\... 
HKLM\SOFTWARE\Wow6432Node\Classes\TypeLib\{F5078F18-C551-11D3-89B9-0000F81FE221}\4.0 
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs

I’ve tried installing and removing the updates, but the files and references are still there.

I’m not entirely certain how to use the advice at https://altonblom.com/s34e10/, since my version numbers aren’t the same as the poster’s, and looking at http://support.microsoft.com/kb/269238 doesn’t help much either.

I’m not sure how to proceed, I still haven’t cracked the WinSXS nut.

windows-7
Martin Hope
austinian
Asked: 2014-08-02 06:45:03 +0800 CST
  • 2

Setup:

Server - WSUS 3.0 SP2 running on Windows Server 2008 R2 (I use WSUSPackagePublisher as a GUI for the WSUS API for importing/creating non MS updates/catalogs)

Workstations - Windows 7 Pro 64-bit, nothing special going on, just a bunch of domain joined machines

Update policy - Download and notify for install. We don't use deadlines, we're small enough that we can bother users who don't install updates in a timely manner, and most users use the "Install Updates and Shut Down" option when they leave for the day or for the weekend.

Issue: For the most part, when updates are downloaded to machines and ready to install, the "Install Updates and Shut Down" option becomes available to users, even for custom updates. However, I have 3 custom updates that aren't triggering that, or so it would seem, and as they're out of band with other updates that do trigger this option, I've seen relatively low installation for the past 2 weeks (roughly 5% instead of 95% after this time period). For these updates, in WSUSPackagePublisher, I've checked the option "Requires Network Connectivity" (source code out of date, but this bit may not have changed much since the last source code post).

My question is this: when making custom updates, what are things that would prevent the "Install Updates and Shut Down" option for those updates?

EDIT: Alright, it seems that by removing the "Requires network connectivity" flag made the updates available via the "Install Updates and Shut Down" method. This may end up in a few machines on my network failing to install the updates if the computer is taken offline first, I'll just have to deal with that possibility for now. Original question still stands, what defines the criteria for an update being able to be installed using the "Install Updates and Shut Down" method?

windows
Martin Hope
austinian
Asked: 2014-06-04 14:04:48 +0800 CST
  • 1

I've got a printer with a Fiery running 8e Release 2. I can authenticate users against AD using the LDAP configuration, but I can only get it to work if I don't use SSL/TLS, and only if I use SIMPLE authentication. Right now, it's authenticating using a fairly low-impact user, but it's also the only system on our network that's not using LDAPS.

I can get AD info fine over LDAPS using ldp.exe from my machine, our firewall, our mail filter, our linux boxes, etc. The only problem child is the Fiery.

I've added the LDAP server certificate as a trusted cert to the Fiery, but after I check the box for Secure Communication and change the port to 636, pressing Validate results in a dialog box coming up saying: LDAP Validation Failed Server Name invalid or server is unavailable.

I've tried changing the server name to use just the name, the FQDN, and the IP address, and changed it to another server, just to see if it was just this AD server that was fussy with the Fiery.

EDIT: removed LDP output, added packet capture analysis from wireshark: The conversation seems pretty normal to me, up to the point where the Fiery terminates the connection after the server sends back a handshake response. Maybe they messed up their TLS implementation? I'm trying support, but it's been fairly useless so far. The cert is a SHA-2 (sha256RSA) 2048-bit certificate. Also, it looks like the Fiery is specifying TLS 1.0. Looking at http://msdn.microsoft.com/en-us/library/windows/desktop/aa374757(v=vs.85).aspx, I'm not seeing SHA256 and TLS 1.0 combination being supported by SChannel. headdesk perhaps that's why, after the DC changes the cipher spec, the connection is terminated by the Fiery? TLS 1.1 and 1.2 are enabled on the DC.

Wireshark conversation: DC: 172.17.2.22, Fiery: 172.17.2.42

No.Time        Source            Port Destination  Port  Protocol Length Info
1  0.000000000 172.17.2.42      48633 172.17.2.22  ldaps TCP      74     48633 > ldaps [SYN] Seq=0 Win=5840 Len=0 MSS=1460 SACK_PERM=1 TSval=3101761 TSecr=0 WS=4
2  0.000182000 Dell_5e:94:e3          Broadcast          ARP      60     Who has 172.17.2.42?  Tell 172.17.2.22
3  0.000369000 TyanComp_c9:0f:90      Dell_5e:94:e3      ARP      60     172.17.2.42 is at 00:e0:81:c9:0f:90
4  0.000370000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      74     ldaps > 48633 [SYN, ACK] Seq=0 Ack=1 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1 TSval=67970573 TSecr=3101761
5  0.000548000 172.17.2.42      48633 172.17.2.22  ldaps TCP      66     48633 > ldaps [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSval=3101761 TSecr=67970573
6  0.001000000 172.17.2.42      48633 172.17.2.22  ldaps TLSv1    147    Client Hello
7  0.001326000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      1514   [TCP segment of a reassembled PDU]
8  0.001513000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      1514   [TCP segment of a reassembled PDU]
9  0.001515000 172.17.2.42      48633 172.17.2.22  ldaps TCP      66     48633 > ldaps [ACK] Seq=82 Ack=1449 Win=8736 Len=0 TSval=3101761 TSecr=67970573
10 0.001516000 172.17.2.42      48633 172.17.2.22  ldaps TCP      66     48633 > ldaps [ACK] Seq=82 Ack=2897 Win=11632 Len=0 TSval=3101761 TSecr=67970573
11 0.001732000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      1514   [TCP segment of a reassembled PDU]
12 0.001737000 172.17.2.22      ldaps 172.17.2.42  48633 TLSv1    1243   Server Hello, Certificate, Certificate Request, Server Hello Done
13 0.001738000 172.17.2.42      48633 172.17.2.22  ldaps TCP      66     48633 > ldaps [ACK] Seq=82 Ack=4345 Win=14528 Len=0 TSval=3101761 TSecr=67970573
14 0.001739000 172.17.2.42      48633 172.17.2.22  ldaps TCP      66     48633 > ldaps [ACK] Seq=82 Ack=5522 Win=17424 Len=0 TSval=3101761 TSecr=67970573
15 0.002906000 172.17.2.42      48633 172.17.2.22  ldaps TLSv1    78     Certificate
16 0.004155000 172.17.2.42      48633 172.17.2.22  ldaps TLSv1    333    Client Key Exchange
17 0.004338000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      66     ldaps > 48633 [ACK] Seq=5522 Ack=361 Win=66304 Len=0 TSval=67970573 TSecr=3101762
18 0.004338000 172.17.2.42      48633 172.17.2.22  ldaps TLSv1    72     Change Cipher Spec
19 0.005481000 172.17.2.42      48633 172.17.2.22  ldaps TLSv1    327    Encrypted Handshake Message
20 0.005645000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      66     ldaps > 48633 [ACK] Seq=5522 Ack=628 Win=66048 Len=0 TSval=67970574 TSecr=3101762
21 0.010247000 172.17.2.22      ldaps 172.17.2.42  48633 TLSv1    125    Change Cipher Spec, Encrypted Handshake Message
22 0.016451000 172.17.2.42      48633 172.17.2.22  ldaps TCP      66     48633 > ldaps [FIN, ACK] Seq=628 Ack=5581 Win=17424 Len=0 TSval=3101765 TSecr=67970574
23 0.016630000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      66     ldaps > 48633 [ACK] Seq=5581 Ack=629 Win=66048 Len=0 TSval=67970575 TSecr=3101765
24 0.016811000 172.17.2.22      ldaps 172.17.2.42  48633 TCP      60     ldaps > 48633 [RST, ACK] Seq=5581 Ack=629 Win=0 Len=0

EDIT: revisited this issue after the recent SCHANNEL patching and POODLE prompted changing our cipher management, and I'm still having this issue.

EDIT: addressing @DTK's answer: Root CA added already. Readded to test. DC FQDN being used, cert matches FQDN, resolves correctly in DNS. Client can access DC using LDAP just fine. Other clients reach LDAPS on same DC just fine. DC supports TLS 1.0, 1.1, and 1.2. Using Simple Auth. Public key is RSA 2048 bit signed with SHA256.

Here's the supported ciphers in cipher order for SCHANNEL from HKLM\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002:

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA

active-directory