Jump to content

Home network access problems...


Waylander
 Share

Recommended Posts

I have found that my netbook [windows 7] is able to see my XPPro desktop in "network" but I cannot connect to it.

I get an error saying Windowsn cannot access \\desktop; check name etc etc. I get error code 0x80070035

I can also see the netbook from the desktop and can log into this no problem and transfer files from desktop to netbook. I want to be able to access my shared folder from the netbook.

As I can see them and can do it 1 way I am assuming it is a firewall issue.

I have allowed the ipaddress of the of the netbook on the desktop firewall [Zone Alarm] and get no blocked access warning

Netbook have PCtools and from what I can see the ipaadress of desktop is allowed [haven't worked out how to create a rule to explicitly allow an ipaddress in PCT yet].

Turning netbook FW off doesn't help either

EDIT: I should add that I can communicate freely between the desktop and my vista laptop so simple file sharing etc is off

Link to comment
Share on other sites

You probably don't have NETBIOS over IP enabled on the laptop. Also, what's the name of the laptop? YOu haven't put any illegal characters in it or made it quite long have you?

Can you try connecting by IP address rather then name (\\19.168.10.1 rather than \\netbook - replace the address with the actual address of you machine, obviously).

Do an IPCONFIG /all and paste the results here +++

Don't have my Win7 laptop with me as I'm on my Mac but I'm sure we can sort easily enough.

Edited by Mac
Link to comment
Share on other sites

  • 2 weeks later...

really sorry for the delay Mac but had a run of serious health scares at home that distracted from this.

Here is the ipconfig/all details:

Microsoft Windows [Version 6.1.7048]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Waylander>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Waylander-Netbook

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter

Physical Address. . . . . . . . . : 06-24-2B-1D-75-D7

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast Ethernet

Controller

Physical Address. . . . . . . . . : 00-13-77-D3-6F-8A

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)

Physical Address. . . . . . . . . : 00-22-69-D5-0B-DF

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Adapter

Physical Address. . . . . . . . . : 00-24-2B-1D-75-D7

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::bcee:18e3:3a16:7075%12(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.0.6(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : 04 April 2009 17:43:29

Lease Expires . . . . . . . . . . : 07 April 2009 17:43:29

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DHCPv6 IAID . . . . . . . . . . . : 201335851

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-47-51-23-00-24-2B-1D-75-D7

DNS Servers . . . . . . . . . . . : 192.168.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 9:

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

Tunnel adapter Local Area Connection* 2:

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

Tunnel adapter isatap.{5853E8C1-63A4-4510-85B9-3E23A645BE39}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

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:d5c7:a2d6:180e:131b:a53b:6846(Pref

erred)

Link-local IPv6 Address . . . . . : fe80::180e:131b:a53b:6846%17(Preferred)

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{69352868-7C82-4126-8A33-B3BABC97AA4A}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{24CD9BB6-0012-4A79-9612-BAB06EEF4121}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

C:\Users\Waylander>

Hope that throws up some clues.

The desktop is called "Thomas" and also has a fixed ipaddress [192.168.0.2]

Link to comment
Share on other sites

If you give the error code a google many people are having the same problem and it seems few fix it.

It seems to be a combination of firewall problems and routing issues within the different OSes. :o

Some of this might help. 0x80070035 Vista Ultimate and Vista Home Premium error - Windows Vista Network

[for a change:p] I did an extensive google review of the error code before posting. The vast majority seemed to be using NIS.

Bear in mind I already have a laptop [running KIS] with Vista HP which works like a charm on this network with the desktop. Admittedly I have not yet had the laptop and netbook on at the same time to see if it works Win7 to Vista.

It is very frustrating. I could uninstall the FW on the netbook to see if that helps but it would be an off FW issue that allows inbound connections but blocks an outbound...

Link to comment
Share on other sites

Fair point :roflmao:

I'd first try and separate an issue with naming from addressing.

Do you have any issues if you use the hosts IP address? I.e. from a DOS prompt:

net use j: \\<ipaddress>\<sharename> /user:<username> <password>

Link to comment
Share on other sites

Sorry the numbers were just padding.

net use J: \\<ipaddress>\C$ /user:<machinename>\<username> <password>

So if your target machine is call DAVE with an IP address of 192.168.1.1:

net use J: \\192.168.1.1\c$ /user:DAVE\administrator AdminPassword

If this works then you know your issue is with name resolution, if it doesn't then it's more fundamental.

Link to comment
Share on other sites

After FINALLY enterring everything in the correct case [lots of path not recognised errors] I got a:

system error 234 has occured.

more data is available.

I googled it and got this MS KB article: Server Service Fails with System Error 8 or System Error 234

which obviously means jack-all to be but how can I have too many things in the registry on a virgin netbook install?

Link to comment
Share on other sites

Update.

I have also just turned on the laptop [Vista HP] - all 3 machines are identifiable on the network and what is most weird is that I can log into the laptop from the netbook and vice versa. Still cannot log into the desktop from the netbook so:

-desktop: can log into laptop and netbook

laptop: can log into desktop and netbook

netbook: can log into laptop but not desktop. I have checked the desktop logs and there is defo no error or blocking by the desktop FW

Link to comment
Share on other sites

I googled it and got this MS KB article: Server Service Fails with System Error 8 or System Error 234

which obviously means jack-all to be but how can I have too many things in the registry on a virgin netbook install?

It's worth running up regedit to check the path in that KB article:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionPipes

If it looks like anything can be removed then do so - obviously taking a backup first.

The other thing the KB mentions is service pack / windows update - worth a try.

Ultimately you need the "Server Service" to start. Right click "Computer", choose Manage and check the list of services. "Server Service" needs to be running, but until you clear up that registry hive or apply a MS service pack/fix I think you'll have problems starting this service.

Chris

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...