解决XP下安装IPV6的Error 0x800704b8的问题

最新推荐文章于 2025-07-17 18:16:30 发布
原创 最新推荐文章于 2025-07-17 18:16:30 发布 · 2.8k 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#xp #cmd

本文介绍了一种通过使用esentutl工具来修复Windows安全数据库的方法。具体步骤为打开命令提示符，然后输入特定命令来实现安全数据库(secedit.sdb)的修复，并且还提到了ipv6相关组件的安装。

点击开始->运行，输入cmd回车

再输入以下两行命令即可：

 esentutl /p %windir%/security/Database/secedit.sdb

ipv6 install

morre
关注
【sdx12】PC电脑不更新IPv6地址导致单独IPv6拨号的时候，PC无法访问外网问题分析及解决方案（sdx12使用SLAAC IPv6）
wgl307293845的博客
04-28 1453
所谓LSAAC，即Stateless Address Autoconfiguration，无状态地址自动配置。SLAAC技术是自动获取IP地址的技术，在IPv6中，除了配置使用HDCP外，还支持使用SLAAC技术获取IPv6地址，以达到设备即插即用的效果。SLAAC的实现依托于NDP协议中的RS报文和RA报文。在IPv6的NDP协议中，共有五种报文，而RS报文，即Router Solicitation，路由器请求报文，RA报文，即Router Advertisement，路由器公告报文。
ipv6修复工具_Rdpscan：一款BlueKeep快速扫描工具
weixin_28730403的博客
01-15 1221
这是一款快速的CVE-2019-0708漏洞扫描工具。目前，公共互联网上大约有900,000台机器容易受到这种漏洞的影响，这还是一个命令行工具。您可以下载源代码并自行编译，也可以从上面的链接下载一个用于Windows或macOS的预编译二进制文件。此工具完全基于https://github.com/zerosum0x0/CVE-2019-0708的rdesktop补丁。我只是修改了代码，...
ipv6解决方案手记！
10-20 770
xp下安装ipv6会出现error 0x800704b8的问题，google下解决问题，解决方案如下： 点击开始->运行，输入cmd回车 再输入以下两行命令即可：  esentutl /p %windir%/security/Database/secedit.sdb ipv6 install 既可安装！ 测试： ping ipv6.google.com ping ipv
为租户下的虚机提供IPv6 DNS服务(by quqi99)
技术并艺术着
11-03 3340
版权声明：可以任意转载，转载时请务必以超链接形式标明文章原始出处和作者信息及本版权声明 (http://blog.youkuaiyun.com/quqi99)问题当虚机运行下列代码时，我们需要考虑为tenant下的VM提供DNS服务:import dns import dns.resolver answers = dns.resolver.query('node1', 'AAAA') print answers............
IPV6 Windows XP
weixin_34241036的博客
01-06 155
从Windows XP开始，Windows操作系统已经内置了IPv6的支持，不过在默认状态下没有安装，可以按照下列步骤安装IPv6： 一、安装步骤（方法1） 进入“控制面板”/“网络连接”，鼠标右键点击“本地连接”，并从随后的菜单中选择“属性”； 注意：本例中的“本地连接”也可能显示成其他名称，请注意鉴别，切勿机械照搬！下同； ...
ceph ipv6部署
qq_15945247的博客
05-23 507
研发云跟踪单： #309674621、环境配置ipv6地址2、/etc/hosts配置主机名称和ipv6地址 安装 安装软件包 关闭防火墙、安装软件包等，与ipv4一致，略过 这里报错，是因为monmap中的地址还是ipv4地址，需要修改 重新执行mon create-initial并分发配置 检查 安装mgr 安装 osd 安装rgw 检查发现 ipv4地址和ipv6地址都启动了
20250717在荣品的PRO-RK3566开发板的Android13系统下解决点屏出现问题unsupport command data type: 217
南岭笑笑生之家
07-17 1054
摘要：开发者在荣品PRO-RK3566开发板的Android13系统下调试MIPI屏幕时遇到"unsupport command data type:217"错误。通过分析发现，问题出在设备树文件(rp-lcd-mipi0-7-1200-1920.dtsi)中的屏参初始化代码格式错误，其中Blank11部分将正确的"290007A0"错误地写成了"290011A0"。修正后，系统成功识别屏参并完成初始化。该问题凸显了在嵌入式开发中，屏参配置的精确性
appstore审核因 ipv6 被拒的问题
weixin_33961829的博客
12-13 319
2019独角兽企业重金招聘Python工程师标准>>> ...
App Store关于苹果IPv6审核被拒，解决方案（适合运维人员）
weixin_34092370的博客
03-02 408
相信上架App Store的基本都会遇到这样的问题，着实让人很头大的。出现这样的原因是，由于国内大部分IP目前都是使用IPv4，App Store审核时会先访问DNS服务器，获得iOS应用服务器的IPv6地址,再进行访问，如果DNS服务网无法成功解析到IPv6地址，出现在提交App Store审核时被拒的情况。 需要说明的是，这不是客户端...
5G网络故障修复全攻略：彻底解决cause=51 (PDU session type IPv6 only allowed)问题
[5G网络故障修复全攻略：彻底解决cause=51 (PDU session type IPv6 only allowed)问题](https://transitwirelesswifi.com/wp-content/uploads/2023/08/choose-access-point-names-on-the-5g-phone.jpg) # 摘要 本文...
[967629.879609] IPv6: ADDRCONF(NETDEV_CHANGE): vethbcc9ec1: link becomes ready [967643.522863] vethce510f2: renamed from eth0 [967643.554230] br-3f0ca603e031: port 3(vethbcc9ec1) entered disabled state [967643.557173] br-3f0ca603e031: port 3(vethbcc9ec1) entered disabled state [967643.561438] device vethbcc9ec1 left promiscuous mode [967643.561457] br-3f0ca603e031: port 3(vethbcc9ec1) entered disabled state [967643.635107] br-3f0ca603e031: port 3(vethbb8ee39) entered blocking state [967643.635114] br-3f0ca603e031: port 3(vethbb8ee39) entered disabled state [967643.635273] device vethbb8ee39 entered promiscuous mode [967643.635525] IPv6: ADDRCONF(NETDEV_UP): vethbb8ee39: link is not ready [967643.635529] br-3f0ca603e031: port 3(vethbb8ee39) entered blocking state [967643.635533] br-3f0ca603e031: port 3(vethbb8ee39) entered forwarding state [967643.930183] eth0: renamed from veth85d8a39 [967643.943653] IPv6: ADDRCONF(NETDEV_CHANGE): vethbb8ee39: link becomes ready [967655.041054] veth6281295: renamed from eth0 [967655.082783] br-3f0ca603e031: port 4(veth6d59721) entered disabled state [967655.084907] br-3f0ca603e031: port 4(veth6d59721) entered disabled state [967655.088992] device veth6d59721 left promiscuous mode [967655.089011] br-3f0ca603e031: port 4(veth6d59721) entered disabled state [967655.158622] br-3f0ca603e031: port 4(veth55add01) entered blocking state [967655.158626] br-3f0ca603e031: port 4(veth55add01) entered disabled state [967655.158750] device veth55add01 entered promiscuous mode [967655.158933] IPv6: ADDRCONF(NETDEV_UP): veth55add01: link is not ready [967655.158937] br-3f0ca603e031: port 4(veth55add01) entered blocking state [967655.158940] br-3f0ca603e031: port 4(veth55add01) entered forwarding state [967655.468755] eth0: renamed from veth34a3453 [967655.487007] IPv6: ADDRCONF(NETDEV_CHANGE): veth55add01: link becomes ready [967656.450917] veth85d8a39: renamed from eth0 [967656.491428] br-3f0ca603e031: port 3(vethbb8ee39) entered disabled state [967656.492801] br-3f0ca603e031: port 3(vethbb8ee39) entered disabled state [967656.494876] device vethbb8ee39 left promiscuous mode [967656.494887] br-3f0ca603e031: port 3(vethbb8ee39) entered disabled state [967656.585684] br-3f0ca603e031: port 3(vethe85c8f4) entered blocking state [967656.585692] br-3f0ca603e031: port 3(vethe85c8f4) entered disabled state [967656.585884] device vethe85c8f4 entered promiscuous mode [967656.586172] IPv6: ADDRCONF(NETDEV_UP): vethe85c8f4: link is not ready [967656.586178] br-3f0ca603e031: port 3(vethe85c8f4) entered blocking state [967656.586184] br-3f0ca603e031: port 3(vethe85c8f4) entered forwarding state [967656.880211] eth0: renamed from vethccff4cb [967656.889712] IPv6: ADDRCONF(NETDEV_CHANGE): vethe85c8f4: link becomes ready [967670.323098] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 5 [967670.323098] {1}[Hardware Error]: event severity: fatal [967670.323099] {1}[Hardware Error]: Error 0, type: fatal [967670.323099] {1}[Hardware Error]: fru_text: A4 [967670.323100] {1}[Hardware Error]: section_type: memory error [967670.323100] {1}[Hardware Error]: error_status: 0x0000000000000400 [967670.323101] {1}[Hardware Error]: node: 1 [967670.323101] Kernel panic - not syncing: Fatal hardware error! [967670.323102] CPU: 10 PID: 0 Comm: swapper/10 Kdump: loaded Tainted: G I --------- - - 4.18.0-240.el8.x86_64 #1 [967670.323103] Hardware name: Dell Inc. PowerEdge R740/0F9N89, BIOS 2.4.8 11/26/2019 [967670.323103] Call Trace: [967670.323104] <NMI> [967670.323104] dump_stack+0x5c/0x80 [967670.323104] panic+0xe7/0x2a9 [967670.323105] __ghes_panic.cold.30+0x21/0x21 [967670.323105] ghes_notify_nmi+0x26b/0x310 [967670.323106] nmi_handle+0x63/0x110 [967670.323106] default_do_nmi+0x4e/0x100 [967670.323107] do_nmi+0x128/0x190 [967670.323107] end_repeat_nmi+0x16/0x6a [967670.323108] RIP: 0010:machine_check+0x0/0x40 [967670.323109] Code: 00 00 48 89 e7 48 8b 74 24 78 48 c7 44 24 78 ff ff ff ff e8 c2 2f 66 ff e9 ed 02 00 00 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 <0f> 01 ca 6a ff f6 44 24 10 03 75 14 e8 2f 00 00 00 48 89 e7 31 f6 [967670.323109] RSP: 0018:fffffe00001b8fd8 EFLAGS: 00000046 [967670.323110] RAX: 0000000000000001 RBX: ffffffff8f929440 RCX: 0000000000000001 [967670.323111] RDX: 0000000000000000 RSI: ffffffff8f929440 RDI: 000000000000000a [967670.323112] RBP: 0000000000000002 R08: 0000000000000002 R09: 0000000000029600 [967670.323112] R10: 00078bfcda5c8c5c R11: ffff88eb1fd68c64 R12: 0000000000000001 [967670.323113] R13: ffffffff8f929538 R14: 0000000000000002 R15: 0000000000000002 [967670.323113] ? async_page_fault+0x30/0x30 [967670.323113] ? async_page_fault+0x30/0x30 [967670.323114] </NMI> [967670.323114] <#MC> [967670.323114] RIP: 0010:intel_idle+0x8d/0x130 [967670.323115] Code: 04 25 80 5c 01 00 48 89 d1 0f 01 c8 48 8b 00 a8 08 75 17 e9 07 00 00 00 0f 00 2d 0a 3c 5c 00 b9 01 00 00 00 4c 89 e0 0f 01 c9 <65> 48 8b 04 25 80 5c 01 00 f0 80 60 02 df f0 83 44 24 fc 00 48 8b [967670.323116] RSP: 0018:ffffb4f44671be40 EFLAGS: 00000046 </#MC> [967670.323116] cpuidle_enter_state+0x73/0x3f0 [967670.323117] ? menu_select+0x2e7/0x670 [967670.323117] cpuidle_enter+0x2c/0x40 [967670.323117] do_idle+0x24c/0x290 [967670.323118] cpu_startup_entry+0x6f/0x80 [967670.323118] start_secondary+0x1b1/0x200 [967670.323118] secondary_startup_64+0xb7/0xc0 啥意思
08-14
[Hardware Error]: error_status: 0x0000000000000400 // 错误状态码 Kernel panic - not syncing: Fatal hardware error! // 内核崩溃 ``` **关键分析**： 1. **错误类型**： - 内存硬件故障（`memory error`），...
iMX6ULL 软件定制应用笔记 -3个常见问题解决思路
ningmengzier的博客
12-31 824
本文以飞凌OKMX6ULL-S开发板为基础讲解，系统为Linux，一共总结了14个iMX6ULL小知识点，分三期完成。 iMX6ULL应用笔记目录 1.1管脚复用的参数配置方法（PINMUX） 1.2Windows下转换开机LOGO图片格式 1.38189es SDIO WIFI使用及测试 1.4 USB转串口芯片的支持（PL2303） 1.5 增加串口 1.6 串口配置DMA 1.7 LCD转LVDS模块 1.8 LCD转VGA模块 1.9 硬浮点运算 1.10 OTG...
[ 2830.840525][ T4357] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 [ 2830.842010][ T4357] Mem abort info: [ 2830.842793][ T4357] ESR = 0x0000000096000044 [ 2830.843685][ T4357] EC = 0x25: DABT (current EL), IL = 32 bits [ 2830.844787][ T4357] SET = 0, FnV = 0 [ 2830.845589][ T4357] EA = 0, S1PTW = 0 [ 2830.846408][ T4357] FSC = 0x04: level 0 translation fault [ 2830.847425][ T4357] Data abort info: [ 2830.848254][ T4357] ISV = 0, ISS = 0x00000044 [ 2830.849148][ T4357] CM = 0, WnR = 1 [ 2830.849937][ T4357] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000102693000 [ 2830.851162][ T4357] [0000000000000038] pgd=0000000000000000, p4d=0000000000000000 [ 2830.852472][ T4357] Internal error: Oops: 0000000096000044 [#1] SMP [ 2830.853593][ T4357] Modules linked in: virtio_rdma(E+) ib_uverbs(E) ib_core(E) xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nf_conntrack_tftp nft_fib_inet nft_fib_ipv4 nf t_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject bridge nft_ct stp llc nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_raw iptable_security rfkill ip_set nfnetlink ebtable_filter ebtables ip6tabl e_filter ip6_tables iptable_filter ip_tables sunrpc vfat fat arm_smccc_trng sch_fq_codel fuse ext4 mbcache jbd2 virtio_gpu virtio_dma_buf drm_shmem_helper crct10dif_ce ghash_ce drm_kms_helpe r sha2_ce sha256_arm64 virtio_net net_failover sha1_ce virtio_blk failover virtio_mmio dm_mirror dm_region_hash dm_log dm_multipath dm_mod virtio_pci virtio_pci_legacy_dev virtio_pci_modern_ dev virtio virtio_ring aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 2830.867784][ T4357] CPU: 7 PID: 4357 Comm: insmod Kdump: loaded Tainted: G E 6.4.0 #3 [ 2830.869442][ T4357] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 2830.870894][ T4357] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=–) [ 2830.872368][ T4357] pc : create_qp+0x90/0x238 [ib_core] [ 2830.873585][ T4357] lr : create_qp+0x1c4/0x238 [ib_core] [ 2830.874795][ T4357] sp : ffff80000c52b670 [ 2830.875802][ T4357] x29: ffff80000c52b670 x28: 0000000000000038 x27: 0000000000000000 [ 2830.877295][ T4357] x26: ffff8000014bc960 x25: ffff0000c3995000 x24: 0000000000000000 [ 2830.878795][ T4357] x23: ffff0000c39cad00 x22: 0000000000000000 x21: ffff8000014bc960 [ 2830.880291][ T4357] x20: ffff80000c52b750 x19: 0000000000000010 x18: ffffffffffffffff [ 2830.881776][ T4357] x17: 0000000000000020 x16: 0000000000000000 x15: ffffffffffffffff [ 2830.883276][ T4357] x14: 0000000000000000 x13: 3020737574617473 x12: 0000000000000001 [ 2830.884762][ T4357] x11: 00000000ffff7fff x10: ffff80000a043268 x9 : ffff80000848232c [ 2830.886260][ T4357] x8 : ffff80000c52b7b8 x7 : ffff80000146fb48 x6 : ffff0000c39928f8 [ 2830.887753][ T4357] x5 : ffff8000014bc960 x4 : 0000000000000000 x3 : 0000000000000000 [ 2830.889254][ T4357] x2 : 0000000000000000 x1 : 0000000000000dc0 x0 : 0000000000000038 [ 2830.890755][ T4357] Call trace: [ 2830.891658][ T4357] create_qp+0x90/0x238 [ib_core] [ 2830.892820][ T4357] ib_create_qp_kernel+0x50/0x128 [ib_core] [ 2830.894087][ T4357] create_mad_qp+0x9c/0x118 [ib_core] [ 2830.895318][ T4357] ib_mad_port_open+0x1bc/0x500 [ib_core] [ 2830.896569][ T4357] ib_mad_init_device+0x6c/0x1e0 [ib_core] [ 2830.897831][ T4357] add_client_context+0x13c/0x208 [ib_core] [ 2830.899111][ T4357] enable_device_and_get+0xd4/0x1b8 [ib_core] [ 2830.900409][ T4357] ib_register_device.part.0+0x104/0x1d8 [ib_core] [ 2830.901759][ T4357] ib_register_device+0x34/0x50 [ib_core] [ 2830.903018][ T4357] virtio_rdma_register_ib_device+0x90/0xb8 [virtio_rdma]
04-08
错误信息是“Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038”，看起来是一个空指针解引用的问题，发生在虚拟地址0x38。这种问题通常是因为代码中访问了一个未初始化或已经...
针对CVPR2019会议相关竞赛提供的标准测试数据集进行图像超分辨率重建的深度学习模型研究实现与性能评估项目_包含多种先进超分辨率算法如EDSRRCANESRGAN的PyTo.zip
12-26
针对CVPR2019会议相关竞赛提供的标准测试数据集进行图像超分辨率重建的深度学习模型研究实现与性能评估项目_包含多种先进超分辨率算法如EDSRRCANESRGAN的PyTo.zip
Chatpsy项目是一个专注于利用前沿科技解决当代青少年心理健康问题的开源创新平台_该项目深度融合脑电信号监测肌电信号分析心率变异性检测皮肤电反应采集等多模态生理数据感知技术_结合.zip
最新发布
12-26
Chatpsy项目是一个专注于利用前沿科技解决当代青少年心理健康问题的开源创新平台_该项目深度融合脑电信号监测肌电信号分析心率变异性检测皮肤电反应采集等多模态生理数据感知技术_结合.zip
liangdabiao_autogen-financial-analysis_18908_1766578238736.zip
12-26
liangdabiao_autogen-financial-analysis_18908_1766578238736.zip
基于LSTM的时间序列预测模型实现与优化探索_针对p2标签趋势预测的深度学习解决方案_通过PyTorch框架构建LSTM加线性层神经网络_利用滑动窗口技术构建序列长度为5的训练数据.zip
12-26
基于LSTM的时间序列预测模型实现与优化探索_针对p2标签趋势预测的深度学习解决方案_通过PyTorch框架构建LSTM加线性层神经网络_利用滑动窗口技术构建序列长度为5的训练数据.zip
基于TensorFlow高阶APIEstimator实现的深度学习模型训练评估预测通用代码库_包含主流CTR预估模型如FM_FFM_DeepFM_xDeepFM_DCN_PNN_.zip
12-26
基于TensorFlow高阶APIEstimator实现的深度学习模型训练评估预测通用代码库_包含主流CTR预估模型如FM_FFM_DeepFM_xDeepFM_DCN_PNN_.zip
XP环境下通过批处理安装IPv6的方法
1. IPv6的基本概念：IPv6是互联网协议版本6的缩写，它是为了解决IPv4地址耗尽问题而设计的下一代互联网协议。与IPv4相比，IPv6具有更大的地址空间，能提供几乎无限数量的IP地址，支持更有效的数据包处理，改善了对...
评论 1
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值