Network access error

[jnelsoninjax]

This is a fresh install of Win 7 Home Premium. No A/V and windows firewall disabled.

[offroadaaron]

Great post.

(I'll give you just as much info as you gave us)

[JaredFrost]

This is a fresh install of Win 7 Home Premium. No A/V and windows firewall disabled.

That sounds about right for a fresh install, seeing as you need to enable file sharing.

You also don't specify which system is giving this error, the Win 7 one trying to access another computer, or another computer trying to access this Win 7 system

So yes, more details are required.

[jnelsoninjax]

This error is coming from the fresh installed laptop. File sharing is enabled on both systems. The laptop in question is able to access the other computer on the network, which is really odd to me.

[+BudMan MVC]

I have seen this before, even on my own systems - I have looked into the reason yet. Prob has to do with uac or mismatch in credentials

i just drop to cmd and net use with user name and password and works just fine after that.

so for example net use * \\computername\share /u:username password

will map next open drive letter

But as mentioned already you are missing quite a bit of info. What username and passwords are you using to access the shares, what accounts are logged in? Passwords are the same?

What permissions do you have set on the sharing and or ntfs as well?

Troubleshooting file sharing issues can take some time over threads - its much easier to just take a look. I should have some time today from work, just PM and we can setup a teamviewer and be happy to take a look.

[jnelsoninjax]

^Thanks BudMan, I used the cmd and receive a message network name not found, system error 67. The damnest thing is I can access the computer from my computer. I am trying to login to my desktop from the laptop using my desktops user name/password.

[+BudMan MVC]

67 hmmm, that is an odd error

do a net view \\computer name

do you get 53 or 5 error?

Do you have a router between the 2 boxes doing nat?

[jnelsoninjax]

Getting 'Network path not found' error 53 when trying from my desktop to her laptop. Yes there is a router, not sure if it is doing nat? How do I tell.

[+BudMan MVC]

There should be NO router between your devices. Why would there be a router between them??

I am not talking about connecting to the same AP, or you common router wireless connection.

How are they boxes connected to your network.

If you have router that you believe your using as an AP -- and your not doing it right, then yeah you can have a issue.

So can you ping your desktop IP? If you can not resolve the name, its kind of hard to access any shares ;)

Draw/Explain how these boxes are connected, and post the output of their ipconfig /all

Also - right after you ping your desktop IP from your laptop, do an arp -a, and post those listing.. What does it show for the mac of your desktop?

[jnelsoninjax]

There is one PC connected to the router, my desktop. The other 2 computers are laptops and they access via wireless. The cable modem is plugged into the router.

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Generic Marvell Yukon 88E8056 based Ethernet Controller
   Physical Address. . . . . . . . . : 00-01-29-A7-99-8E
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 208.67.220.220
									   208.67.222.222
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{658C4069-3C82-47DE-AA78-F601E9091A68}:

   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* 9:

   Media State . . . . . . . . . . . : Media disconnected
   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

[+BudMan MVC]

And can you ping this 192.168.1.2 from your laptop?

You sure you just do not have AP isolation turned on? Depending on the router -- this could block wireless from talking to other wireless, and on some models block wireless from talking to wired. But does not stop wired from talking to wireless.

What is its IPconfig /all output?

If you not going to use ipv6, why not remove that stuff so your ipconfig /all is cleaner?

A simple will remove it all

reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255

The if you ever want it back like nothing happened just

reg delete hklm\system\currentcontrolset\services\tcpip6\parameters\ /v DisabledComponents /f

This will remove those other adapters your seeing your isatap and teredo, etc.

[jnelsoninjax]

OK, from the laptop I get error 67, network name cannot be found using the net use cmd. from her account (standard)

From the admin acct: error 5, access is denied

From admin: net use shows error 53 network path not found.

Netview yields Access is denied when trying to view my system.

[jnelsoninjax]

ipconfig /all from laptop:

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physical Address. . . . . . . . . : 78-E3-B5-5D-68-C8
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Ralink RT5390 802.11b/g/n WiFi Adapter
   Physical Address. . . . . . . . . : 94-39-E5-77-ED-52
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ce2:22a5:b0a1:d48a%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 241738692
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-81-89-C9-68-A3-C4-B3-9D-45
   DNS Servers . . . . . . . . . . . : 208.67.222.222
									   208.67.220.220
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{20919493-028B-42BC-91B3-B4AD8CEDA5F3}:

   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.{862F7A89-B602-4C88-8551-2FFE38B2DA80}:

   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:4137:9e76:1c44:ad5:b395:6b1c(Preferred)
   Link-local IPv6 Address . . . . . : fe80::1c44:ad5:b395:6b1c%13(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

[+BudMan MVC]

So how many time do I have to ask for a simple ping test?

you get access denied on \\computername then I would say you have share permissions wrong for access without auth, if that is what you want?

But you should still be able to access..

verify you can PING!!!

then do

net use \\computername\ipc$ /u: username password

example

[jnelsoninjax]

[sc302 Veteran]

I don't want to step on budmans toes here, but I would try forcing netbios on. Tcpip properties of the computer you can't resolve by pinging the name, wins tab, netbios on vs auto.

See if that helps.

[+BudMan MVC]

Netbios is already enabled - see from his post

Yeah its clearly a name resolution problem. And its wireless - broadcast is not working it seems. Try resetting your router.

Seen this a few times already here -- broadcast not working on over wireless. You can verify that with a sniff on both the desktop and the laptop -- see the broadcast packet go out, and then not see it on the client. If you see it on the client, then the client is not answering.

Access it via ip vs name ie do net view \\192.168.1.4

I have to look up the 67 error though, that doesn't make sense for simple can't find the name.. Should be simple error 53.

btw - post a screen shot of your share center settings for grins, your also in a home/private network not public right?

example

This will show current profile and if you have anything shared to everyone/anon, etc.

[c.grz]

The DNS server he's using is 208.67.220.220 which is external; shouldn't it be 192.168.1.1?

[sc302 Veteran]

Dns doesn't matter where it points in this case as long as it can resolve outside names. There is no internal dns server to check on internal names so it really doesn't matter where it is pointed. Name resolution is against netbios.

Budman, for the record, I don't care what ipconfig thinks. I have had issues where that it is enabled but forcing it on fixes the issue at hand. You have to admit, crap that happens to me isn't exactly by the book....and book answers don't always fix my issues.

[+BudMan MVC]

Well without a sniff it would be hard to say, but its clearly stated as being enabled - so that should mean its enabled ;)

What I have a few times here recently is broadcast not working over the wireless. Which I would think is more likely -- it can not hurt for sure to turn it to enabled if set for auto, etc.

As to the dns -- no there is no reason to point to his router if he doesn't want to.. I am not a fan of the soho routers dns forwarding/cache anyway -- they tend to die now and then and don't make anything any faster that is for damn sure. More of a convenience than anything else - just auto hand that out in dhcp, etc.

Now his name resolution issue would be mute if he ran an actual local dns with his machine names, etc. Now if he was dhcp I might say his router might do that - some do, but since he is static I highly doubt his router dns support dynamic updates, etc.

Just so what we are talking about jnelson, which I highly suggest you fire up wireshark so you can see this on your own network anyway.

Here is me trying to find a machine called \\testbox -- which does not exist btw.

Notice my box try dns first, adding my suffix local.lan - which clearly dns says sorry bud no record.

So then it broadcasts! the 192.168.1.255 address -- no response

So here is one that answers via broadcast, notice the 2 dns queries - first one is one I did directly with dig to make sure I removed it and it wouldn't answer ;) And then 2nd one is when I did the net view, then it broadcasted and got an answer

[jnelsoninjax]

I think that the issue might be the desktop... when I go to Network, nothing shows up, but I can manually input the address to one laptop and it works, but when I attempt to input the address to my daughters laptop I still get a message stating that windows can not find the computer. I checked out my advanced file sharing and discovered that network discovery was turned off and will not turn on... incidentally I can access my daughter's laptop via IP address but not name. But the reverse does not work (IP of my desktop from her laptop). Now suddenly my PC shows up on the network, but still remains non accessible (same error as before) but I am able to view the laptop through name and IP now.

[+BudMan MVC]

discovery has nothing to do with it - that's just if the browsing server is on or off

So did you try resetting your router?

Do a simple sniff to see if your broadcasting, and sniff on your other laptops to see if you see the traffic.

You sure your not just firewalling it?

Grab wireshark - and do a simple sniff while you do a net view.

But first thing I would do is RESET YOUR ROUTER!!!

Again going to network and not seeing anything is NOTHING to do with simple name resolution via broadcast.. That is the computer browser, completely different and has nothing to do with actually access your computers. Just a stupid LIST!!

[ybrett23]

reset the router

clear the arp cache

flush dns

and reset the tcp ip stack :)

[+BudMan MVC]

arp cache has nothing to do with broadcasting for netbios name, nor does dns.

I agree I asked him to reset his router a while back, I would even go as far as saying just use NO encryption as test. Then put it back, etc.

Broadcast traffic is group key, different than unicast over wireless - so that could be the issue???

You don't really know what is happening unless he does simple sniff that would take all of like 5 minutes. Download wireshark, its FREE install -- run it on both machines and do a net view \\computername

Then we could see if seeing broadcast or not.. Until you see what is actually on the wire we are just guessing!

[jnelsoninjax]

OK so I have no idea what I am looking at with wireshark. I did reset the router, I just failed to mention it.