Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3454
  • Last Modified:

Home Network was working now \\computername is not accessible. You may not have permission

My home network has One XP Pro machine (ICS) and master browser.  Two Windows ME and one Windows 98 Plus.  It has been working failry well for over a year.  Recenlty while access one of the other computers on the workgroup, it stopped.  I say this because there were no software updates (MS or other) that were installed imediatley before the netwrk stopped working.
I have tried and confirmed: Guest account on Win XP pro, TCP/IP NetBIOS setting enabled and not default on WINS, try turing simple file sharing on and then off, tried recreating network, and a few other hints from the newsgroups, i.e. server service is running, etc.

I can "see" the other computers in the Workgroup window but when I try to access them I get "\\computername is not accessible.  You may not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions."

The other workgroup computers can access each other to share printers and files.

I am really flustered and have no other ideas.  Help?
0
arneberg
Asked:
arneberg
  • 13
  • 8
  • 6
  • +1
1 Solution
 
stevenlewisCommented:
>I can "see" the other computers in the Workgroup window but when I try to access them I get "\\computername is not accessible.
which machine gives this error
If, while trying to access shares on the XP box from one of he other boxed check
on the  box
Run local security policy editor from control panel admin tools and set the local policy, Network Access: Let everyone permissions apply to anonymous users, to enabled and make sure guest account is enabled


also check all boxes for spyware/malware
http://patrick.kolla.de/spybotsd.html
PestPatrol
http://pestpatrol.com/
ad aware
www.lavasoft.de
hijack this
http://www.spywareinfo.com/downloads.php
0
 
arnebergAuthor Commented:
I regularliy run PestPatrol as well as ad aware.  I also use NAV and NIS.  I have disabled the firewall in ICS and NIS as well as disabled NAV and still get the error.  On the WinXP Pro computer, I checked the local policy settings for network access and everyone has access as before.  Guest account is enabled.

I am on the WinXP Pro computer when I "see" the other computers in the workgroup.  when I double click one of these other computers is when I get the error.
0
 
lrmooreCommented:
Do you have Netbios over TCP/IP enabled on the XP box?
http://support.chartermi.net/support/pipeline/windows/winxp_network.html
Although this link says to set netbios over tcp/ip to "default", follow the instructions below and set to "enable"
Enable NetBios over TCP/IP in WIndows XP
Step 1: Turn On NetBIOS over TCP/IP
Click Start, click Control Panel, and then click Network and Internet Connections.
Click Network Connections.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click the General tab, and then click Advanced.
Click the WINS tab.
Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click OK two times.
Click Close to close the Local Area Connection Properties dialog box.
Close the Network Connections window.
reboot
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
lrmooreCommented:
Forgive me, I re-read your post and you have checked the netbios settings....
If you can't access a Win98 system from XP then 99% of the time it is because netbios is not enabled.
If you can't access XP from Win98 then it is permissions (open Guest acct)
Do you have an old lmhosts or hosts file with old ip addresses for these systems?
Have you tried a new LMHOSTS file?
0
 
arnebergAuthor Commented:
I have checked the Guest account the users have permission and the account is enabled.  I should clarify that ALL the other workgroup computers (they are Win 98 and Win ME) can see AND access each other with no problem.  They can not see the Win XP Pro computer.  The Win XP pro computer can see the others in the workgroup but can not access them.  At first it sounded like a firewall problem on the XP computer but I have tripled checked and made sure no firewall is running.

By the way I find only the sample LMhost file (lmhost.sam) in C:\WINDOWS\system32\drivers\etc and no lmhost file that contains any old IP addresses.  The only file that seems to get updated when I reinstall the network is the host.ics file.  Is there another lmhost file location I am missing?

IN addition, the host.ics file for intenet connection sharing does list the workgroup computers IP addresses but uses a "standard" name for each of them that looks like:

192.168.0.152 Sam.mshome.net
192.168.0.136 computer.mshome.net

etc.

my workgroup name is ACE so I am not sure why it does not show as

192.168.0.152 sam.ace.net

0
 
arnebergAuthor Commented:
One more thing.  I can not ping the ip addresses on any of the computers that show up in the Win XP Network Neighborhood workgroup.  I can ping myself on the Win xp but no others.  On the other workgroup computers I can ping all the other computers (as said before though, the WinXP machine does not show in the workgroup on any of the other computers)

I have tried adding a lmhost file and configured WINS to look for it with no success.
0
 
lrmooreCommented:
Look at print out of C:\>ipconfig /all on XP and compare to the others. You may have the subnet mask wrong, or not getting an IP address..
It should be 192.168.0.1 if you have ICS enabled..

Do you have ICS enabled on the wrong interface?


0
 
arnebergAuthor Commented:
Thanks.  I looked and all IP addresses look fine and the subnet mask matches the others.  This has been really weird as I said, it was working and then it just stopped mid stream.  No settings look different than when it was working.  For what its worth, the Ethernet adapter Network Bridge (MAC Bridge Miniport) with Dhcp Enabled...No  and the Default Gateway is blank.  The ICS is on the proper adaptor also.
0
 
lrmooreCommented:
>Ethernet adapter Network Bridge
Try removing the bridge in device manager...
0
 
arnebergAuthor Commented:
I removed and then reinstalled the bridge with no effect on problem. This must be something obvious as I now am completely stumped.
0
 
lrmooreCommented:
Remove the bridge, but don't reinstall it. You don't need a bridge connection.
0
 
arnebergAuthor Commented:
I have a 1394 Net Adapter that is bridged with the local area connection.  When I use the network wizard it bridges these together.  If I don't bridge these, I don't see the other computers in the work group at all, ever.
0
 
stevenlewisCommented:
was working and now it's not
try a system restore, and go back to when it was working
system restore is a two way street, if it doesn't help, you can go back to the future (now)
0
 
arnebergAuthor Commented:
Thanks.  I tried a system restore the first day I ran into this problem.  It didn't help.  Is there a registry setting that contains the dns type data?
0
 
stevenlewisCommented:
No, but there is a command to flush it
ipconfig /flushdns
run from a command prompt

any firewalls involved?
0
 
arnebergAuthor Commented:
No firewalls.  I doubled checked Windows XP ICS firewall is not running.  I have Norton Internet Security but it is disabled.  I tried flushing the dns cache also.

When I go to one of the other workgroup computers and change its name, and then return to the Windows XP computer, I see the new computer in the workgroup.  But as always I get the: "\\Computername is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out
if you have access permissions.

The network path was not found."

message.  It sure sounds like a firewall problem but I can't figure out why I can see the workgroup computers so easily but not access them from the WinXP box.  Of course, I still can't see the WinXP box from any of the other workgroup computers.  Do you think I should waste my $ and call MS support?  I am afraid they will just give me the start from a clean install approach and I can't afford that much downtime.  Furthermore, if it happens again then I will not know how to fix it specifically.
0
 
lrmooreCommented:
I would try uninstalling the Norton Internet Security before I wasted money with Msoft
0
 
stevenlewisCommented:
before uninstalling Norton, enable it, and allow everything to pass
0
 
stevenlewisCommented:
NIS = firewall
Key Features
Norton AntiVirus™
   
  Norton™ Personal Firewall
   
  Norton™ Privacy Control
   
  Norton AntiSpam™
   
  Norton™ Parental Control
0
 
arnebergAuthor Commented:
OK. I tried enabling everything and then I gave up and uninstalled NIS.  Still no luck.  I give up.
0
 
stevenlewisCommented:
0
 
arnebergAuthor Commented:
Yea. I just read about it earlier and gave it a try.  NG (no good)
0
 
arnebergAuthor Commented:
The MS Networking newsgroup is showing a lot of recent activity regarding this sort of behavior.  I beleive that it may have something to do with the last security hotfix by MS.  I am going to try and unistall the hotfix and will let you know.
0
 
arnebergAuthor Commented:
Removing Hotfix did not work.
0
 
arnebergAuthor Commented:
I resolved this issue myself.  I reinstalled the software for my Intel LAN adapters.
0
 
stevenlewisCommented:
Glad you got it working
go here
http://www.experts-exchange.com/Community_Support/
and request a refund
include a link to this question in the body of that one
Steve
0
 
stevenlewisCommented:
How about a PAQ with a refund, some good info here
0
 
SpazMODicCommented:
PAQed, with points refunded (500)

SpazMODic
EE Moderator
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 13
  • 8
  • 6
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now