Mshome 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 list of servers for this workgroup is not currently available
Not sure what to try next.
We've 2 computers - XP - and connect via router.
If this isn't the right forum to ask this on... plse advise?
Thanks - kirk
--
kirkm
------------------------------------------------------------------------
kirkm's Profile: http://forums.techarena.in/members/111524.htm
View this thread: http://forums.techarena.in/windows-xp-support/1208373.htm
Following through the points in this link may help. Don't overlook the
second page.
http://forums.techguy.org/networking/437989-pc-not-seen-mshome-network.html
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
It did remind me to try Ping, and it turns out both computers can Ping
themselves and each other. But there's nothing in 'My Computer'
/explorer.
So I don't know where to from here... hope a Genius shows up? :)
Cheers - Kirk
When troubleshooting these network problems the first step is always to
make sure that the firewalls are not at fault. While you try to fix
this disable the firewalls, this is an important first step, there is no
sense trying to diagnose and fix this unless you are 100% sure that the
firewalls are completely eliminated as a possible source of the problem.
After you have eliminated the firewall as a possible source you can try
to ping the computers by name and by IP address and see what happens.
If you can't ping by name but can ping by address this is probably a
network browser problem. The NET VIEW command is also most helpful when
troubleshooting these browsing problems, issue the command at a Command
Prompt and note the results of the command.
Usual causes for this "Workgroup is not accessible..." problem:
1- The firewall is blocking traffic.
2- The firewall is blocking traffic. I already said that? Double
check and make doubly sure that the firewall is not blocking traffic.
3- File and Printer sharing is not enabled.
4- The browser service is not running.
5- TCP/IP NetBIOS Helper service (NetBT) is not running.
6- (XP Home only) The Guest account is disabled.
Restricting access over anonymous connections can also cause browser
problems:
http://support.microsoft.com/kb/913628
Error message when you try to access a Windows XP-based network
computer: "You might not have permission to use this network resource"
John
"I *don't* have a firewall to turn off" Meaning? Have you disabled the
Windows Firewall? Are you relying on a hardware firewall?
What is your router make and model? Have you tried switching it off for
10 seconds plus. Then restart your computer and switching the router on
before the reboot is started?
Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Certainly have been busy and it's good to eliminate a few things.
To answer questions,
2x XP Pro
Router is DSL G604T. Have rebooted/reset everything.
No conflicts or trouble in Device Manager
The various services required are all running 'automatically'.
By 'don't have a firewall' I meant other than the XP one. Disabling it
makes
no difference. But - is there one in the Router? I'm about to ring
their Help line and find out.
Running Net View showed an error though. It may shed a clue?
Here's the netview and confg/all dumps from both computers -
---
COMP 1
------
net view
System error 6118 has occurred.
The list of servers for this workgroup is not currently available
ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : kirk
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-1D-7D-C2-39-B1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.1.1.3
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.1.1.1
DHCP Server . . . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 10.1.1.1
Lease Obtained. . . . . . . . . . : Monday, 6 July 2009 2:43:43
p.m.
Lease Expires . . . . . . . . . . : Monday, 6 July 2009 3:43:43
p.m.
COMP 2
------
net view
Server Name Remark
-------------------------------------------------------------------------------
\\JILL88
\\KIRK
The command completed successfully.
ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : jill88
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-0C-76-5E-49-51
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 60.234.1.1
60.234.2.2
--
Any further suggestions welcome :)
I really appreciate you guys helping.
Thanks - Kirk
System error 6118 has occurred. The list of servers for this workgroup
is not currently available
SYMPTOMS: 1) After enabling ICS/ICF, you can't see any computes on My
Network places. If you try, you may get "workgroup is not accessible".
2) If you use the net view command, you may receive "System error 6118
has occurred. The list of servers for this workgroup is not currently
available." message.
Resolutions:
1) This behavior can occur if you enable the ICF that will closes the
ports for file sharing by default. To open these ports, right-click the
network connection that is firewall protected>
Properties>Advanced>Settings>Service Tab>Add, Enter 127.0.0.1) for the
required Internet Protocol (IP) number. Enter UDP ports from 135 through
139, and TCP ports from 135 through 139 one by one (the external and
internal port numbers should be identical).
After reaching 'Settings" there's no Sevice Tab or Add options.
2) This may occur if the workgroup name and the domain name are the
different.
Didn't think I had a Domain name. Should I make it MSHOME? How's that
done?
3) No master browser. Starting Computer Browser Service on one of
w2k/xp computers should fix the problem
Definately running on both computers.
COMPLETELY DISABLE THE FIREWALLS WHILE YOU TROUBLESHOOT THE PROBLEM!
This can never be said often enough, all too often people run around in
circles for an eternity trying to resolve network problems only to
finally find out that the firewalls are blocking things! If the
firewall is disabled the above closed ports problem is a non issue.
> 2) This may occur if the workgroup name and the domain name are the
> different.
>
> Didn't think I had a Domain name. Should I make it MSHOME? How's that
> done?
You don't want any domains, both of your machines should be in the same
workgroup. Right click on My Computer and then click on Properties. In
the Computer Name tab click on "To rename this computer or join a domain..."
John
On both machines make sure that the DHCP Client service is set to
Automatic and in the Local Area Connection Properties make sure that the
machines are obtaining their IP addresses automatically (in the TCP/IP
Properties). Or, if you want to use static addresses, keep the machine
in the same address range and in the same subnet.
John
You're onto it! 100% success this end. The clue was the differences in
each
computers setup. They were manually configured and after the re-install
mine, reverted to the automatic (default, I guess) method.
Entering the right details in again and rebooting restored everything
nicely. I'd like to think I've learned from this - but it was probably a
fluke! But at least it's away again... thanks to you and Gerry for
your help and interest.
Cheers - Kirk
John