Same problem.
I resolve this problem, disabling ipv6 on the network interfaces.
Unable to access LAN, hostnames always have mshome.net appended.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I can no longer access the intranet on our LAN. If I ping the hostname of one of the servers I get the following:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\chris>ping fuji
Pinging fuji.mshome.net [65.55.39.12] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 65.55.39.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Previously, mshome.net was not appended. This seemed to change last week after installing the latest Windows updates. Other computers on the LAN do not have this problem. Output from ipconfig:
Microsoft Windows [Version 6.0.6002]Copyright (c) 2006 Microsoft Corporation. All rights reserved.C:\Users\chris>ipconfig /allWindows IP ConfigurationHost Name . . . . . . . . . . . . : chris-mobilePrimary Dns Suffix . . . . . . . :Node Type . . . . . . . . . . . . : HybridIP Routing Enabled. . . . . . . . : NoWINS Proxy Enabled. . . . . . . . : NoDNS Suffix Search List. . . . . . : mshome.netEthernet adapter Local Area Connection 2:Media State . . . . . . . . . . . : Media disconnectedConnection-specific DNS Suffix . :Description . . . . . . . . . . . : TAP-Win32 Adapter V9 Physical Address. . . . . . . . . : ****DHCP Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesWireless LAN adapter Wireless Network Connection:Media State . . . . . . . . . . . : Media disconnectedConnection-specific DNS Suffix . :Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection Physical Address. . . . . . . . . : ****DHCP Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesEthernet adapter Local Area Connection:Connection-specific DNS Suffix . : mshome.netDescription . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast EthernetController Physical Address. . . . . . . . . : ****DHCP Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesLink-local IPv6 Address . . . . . : fe80::b491:89e4:7e21:2c1e%9(Preferred)IPv4 Address. . . . . . . . . . . : 192.168.251.110(Preferred)Subnet Mask . . . . . . . . . . . : 255.255.255.0Lease Obtained. . . . . . . . . . : June-14-10 11:16:35 AMLease Expires . . . . . . . . . . : June-21-10 9:55:34 AMDefault Gateway . . . . . . . . . : 192.168.251.1DHCP Server . . . . . . . . . . . : 192.168.251.1DHCPv6 IAID . . . . . . . . . . . : 201332165DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-6B-B1-08-00-15-C5-82-7F-43DNS Servers . . . . . . . . . . . : fe80::d9b3:910c:e8b8:60e2%924.200.241.3724.201.245.7724.200.243.189Primary WINS Server . . . . . . . : 192.168.251.5NetBIOS over Tcpip. . . . . . . . : EnabledConnection-specific DNS Suffix Search List :mshome.netC:\Users\chris>
Windows for home | Previous Windows versions | Internet and connectivity
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Anonymous
Answer accepted by question author
Anonymous
Do you know when this problem began (with the updates)? Try a System Restore to a point in timeBEFORE the problem began. Here's the procedure: http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/. Be sure to check the box to show more than 5 days of restore points. If the first attempt fails, then try an earlier point or two. NOTE: You will have to re-install any software and updates you installed between now and the restore point, but you can use Windows Update for the updates. Use the recovery disk if the system prompt doesn’t work. The recovery disk works a bit different from the above procedures but if you follow the prompts from the System Restore menu option with the above information you should be able to restore with no problems. If that fixes the issue, temporarily disable automatic Windows Updates until the issue with these particular updates is resolved - then you can turn it back on.
If that resolves the problem, you still have a problem with the updates (and even if it doesn't resolve the problem, you have a problem with the updates).
Please repost your question in the Windows Update Forum at:http://social.answers.microsoft.com/Forums/en-US/vistawu/threads where experts in updates will be happy to assist you. Please post with the info requested here: What to post in the Windows Update forum
I hope this helps.
Good luck!
Lorien - MCSE/MCSA/Network+/A+ --- If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.
4 additional answers
Sort by: Most helpful
-
Anonymous
2010-07-05T17:08:34+00:00 Thanks Alex, disabling ipv6 resolved the problem for me.
-
Anonymous
2010-06-21T16:04:06+00:00 i had the same issue after i updated last week. i used the disable ipv6 option and i can now access the intranet in our network.
I hope this issue gets resolved next update.
thanks
-
Anonymous
2010-06-16T07:43:32+00:00 i seem to have the same problem.
They occured 3 times already. Always after a microsoft update.
I takes my computer 24 hours to stop using the suffix.
At least, when i logon the next morning the problem is gone (??). I have already tried reboots, but that didn't seem to work.
Going back using the restorepoint option will fix the problem ot the moment.
Regards,
Eric
Willing to learn everything about Sharepoint there is to learn. My blog