Error 0x80070035 after changing motherboard

Patrese

Member
Jul 12, 2005
82
0
66
I've lost most of my Saturday trying to figure out what happened here.

I had a perfectly working home network composed by a desktop (Windows 7 Professional x64) and a notebook (Windows 7 Home Premium x64) connected by the TP-LINK TL-WR941ND router. After I bought a new motherboard, something went wrong. It was a Abit IP35 before (Realtek NIC), and now it is a Asus P5Q (Atheros NIC). I made a clean install to change the motherboards using the latest drivers, and updated the router firmware and reconfigured it just in case, but the problem persists.

- The desktop enters the internet and the shared folders of the notebook, no problem at all.
- The notebook enters the internet normally, but gets an error 0x80070035 when I try to enter any of the desktop's folders, including the ones on the domestic group.
- When I try to reach the desktop through its IP on the start menu, I get an error...
- Pinging the IPs gives no errors, though.

I've read a bunch of threads about this sort of error, but none of those actually helped. Here's my ipconfig /all log:

Host Name . . . . . . . . . . . . : JB2-X2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PC
thernet NIC (NDIS 6.20)
Physical Address. . . . . . . . . : 00-17-3F-9B-D5-97
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6805:48e9:79d3:b08d%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.169.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, 5 Setember 2010 02:42:34 AM
Lease Expires . . . . . . . . . . : Sunday, 5 Setember 2010 04:42:34 AM
Default Gateway . . . . . . . . . : 192.169.1.1
DHCP Server . . . . . . . . . . . : 192.169.1.1
DHCPv6 IAID . . . . . . . . . . . : 234890380
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-14-B5-37-00-24-8

DNS Servers . . . . . . . . . . . : 192.169.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface: {4E871A65-F3A7-4117-A439-167C8F6D9BCD}

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:18dc:e427:42c4:4488(Preferred)
Link-local IPv6 Address . . . . . : fe80::18dc:e427:42c4:4488%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{480155F1-9F23-421C-91A2-6CD8968923AA}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

And the nbtstat -n

Name Type Status
---------------------------------------------
JB2-X2 <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
JB2-X2 <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

Thanks in advance!
 

ch33zw1z

Lifer
Nov 4, 2004
38,779
19,369
146
I may be wrong here, but an IP address of 192.169 would be a public IP address? IE, not the private 192.168 non-Internet routable address. Was this always your config?

Also, try disabling/checking firewall rules.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
I may be wrong here, but an IP address of 192.169 would be a public IP address? IE, not the private 192.168 non-Internet routable address. Was this always your config?

Also, try disabling/checking firewall rules.

Yep, the whois info says it's owned by PSG.com.
 

Patrese

Member
Jul 12, 2005
82
0
66
I may be wrong here, but an IP address of 192.169 would be a public IP address? IE, not the private 192.168 non-Internet routable address. Was this always your config?

Also, try disabling/checking firewall rules.

Yep, the whois info says it's owned by PSG.com.

Whoa, that's scary. Here's the deal: my ISP routes its modem configuration to the same address (192.168.1.1), so the only way my ISP would play along with my router was changing the router config to 192.169.1.1. Since I'm clueless about network stuff, looks like I made a real bad mistake when I changed the address to 169 and will correct it NOW. Thanks guys.

@topic: I've already disabled the firewall on both computers and the problem persists... :( Any other ideas?
 

RebateMonger

Elite Member
Dec 24, 2005
11,586
0
0
File Sharing is enabled on the desktop? And it's set for a "Work" or "Private" (I can't remember which is used in Win7, but the result is the same) network?
 

JackMDS

Elite Member
Super Moderator
Oct 25, 1999
29,516
408
126
File Sharing is enabled on the desktop? And it's set for a "Work" or "Private" (I can't remember which is used in Win7, but the result is the same) network?
Home Network

Work Network

Public Network.

Work Network is the best choice (even if you are a gamer and never works :sneaky:).


:cool:
 

VirtualLarry

No Lifer
Aug 25, 2001
56,570
10,200
126
Whoa, that's scary. Here's the deal: my ISP routes its modem configuration to the same address (192.168.1.1), so the only way my ISP would play along with my router was changing the router config to 192.169.1.1. Since I'm clueless about network stuff, looks like I made a real bad mistake when I changed the address to 169 and will correct it NOW. Thanks guys.

Yeah, should have changed it to 192.168.2.1.
 

Patrese

Member
Jul 12, 2005
82
0
66
Thanks for all the responses. Nothing new to report, unfortunately. Here's the day recap:

- IP address changed to 192.168.2.100 Not public anymore, big thanks to everybody who brought this to my attention. Funny thing is that with the Abit IP35 the network worked perfectly using the 192.169 IP...

- Network is configured as "Home" on both computers. There's also a Public Group set up and both the computers "see it". Only the desktop can browse the files, though: the notebook gets the error code above. :( Why a "work" network is better? Don't think it will solve my issue, but it'd be good to know that.

- Pinging the IP on both the notebook and desktop shows no errors, but I can't access the desktop by typing \\192.168.2.100 on its start menu.

Question: Buying an offboard NIC with Intel or Realtek chipsets would bring me any chance of restoring my network? The reputation of the Atheros chipset of the P5Q is hardly inspiring, specially on Windows 7.

Formatting the notebbok maybe? Anything else I can to to at least try to troubleshoot this annoying issue?
 

bad_monkey

Member
Aug 31, 2010
59
0
0
Will you post the relevant portions of ipconfig for both the desktop and the notebook? If all the IP addresses look good then I would recommend checking out this post by JackMDS.
 
Last edited:

Patrese

Member
Jul 12, 2005
82
0
66
For some bizarre reason I could not identify, there were 271 Microsoft "6to4" adapter devices installed on my notebook. Seems to be a rather normal thing on Windows Vista/7 using Google search as a parameter. Shame on you, MS.

Using "devcon remove *6to4mp" I uninstalled them all and bingo, it worked again. Thanks a lot for all the responses!