Re: Home networking

Andy,

I recently went throught the same problem. I kept a log of the different
"fix" ideas I collected off of newsgroups. Go through the stuff below and I
hope it helps.

JG

....do not have permission to use network resource.

RESOLUTION
To resolve this issue, make sure that NetBIOS over TCP/IP is turned on and
the Computer Browser service is running on each computer in the workgroup.
To do this, follow these steps.
Back to the top

Step 1: Turn on NetBIOS over TCP/IP
1. Click Start, click Control Panel, and then click Network and Internet
Connections.
2. Click Network Connections.
3. Right-click Local Area Connection, and then click Properties.
4. Click Internet Protocol (TCP/IP), and then click Properties.
5. Click the General tab, and then click Advanced.
6. Click the WINS tab.
7. Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click
OK two times.
8. Click Close to close the Local Area Connection Properties dialog box.
9. Close the Network Connections window.

Back to the top

Step 2: Start the Computer Browser service
1. Click Start, right-click My Computer, and then click Manage.
2. Double-click Services and Applications.
3. Double-click Services.
4. In the right pane, right-click Computer Browser, and then click Start.
5. Close the Computer Management window.



1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then double-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the right pane, double-click restrictanonymous.
4. Make sure that the value in the Value data box is set to 0, and then
click OK.
5. Close Registry Editor.
6. Restart the computer.




TO ACCESS COMPUTERS IN YOUR NETWORK IN WIN XP Problem: While accessing My
Network Places, I was getting the message : "(XXXX) 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.

To solve the problem you must add:

"NWLink IPXSPXNetBIOS Compatible Transport Protocol" to the "Network
Properties" list on each computer of the network.

The error message is misleading in that it has nothing to do with
permissions or servers or logging on as administrator. Note: To add "NWLink
IPXSPXNetBIOS Compatible Transport Protocol" open your Network Connections
as explained below:

1 - Go to Control Panel, and select "Network Connections";

2 - Right-click with your mouse your Network Connection and select
"Properties";

3 - On the "Connection Properties" screen, select the "Install" tab;

4 - On the "Select networking Component" screen select "Protocol"
double-click the Add..." Tab;

5 - On the "Select Network Protocol" screen, select "NWLink IPXSPXNetBIOS
Compatible Transport Protocol" and click the "OK" tab to install the
protocol. The steps above have to be repeated on every computer present in
the Network.


Workgroup is not accessible
General
If you get one of these symptoms or error messages or a similar one:

You cannot access shares on other computers.
You cannot locate other computers in the workgroup.
When you double-click the workgroup in Network Neighborhood or My Network
Places, you get the error message: Workgroup is not accessible. You may not
have permission to use this network resource.
Workgroup is not accessible. The list of servers for this workgroup is not
currently available.
Perform the following procedures, which could perhaps cause this problem,
and read also the chapter, "Network path not found". Retest after each
procedure. Reboot after making nontrivial changes.

If you have Service Pack 2 or higher installed, make sure the File and
Printer Sharing exception is enabled in the firewall. Reboot to allow the
browser service to start or start it manually (see below), but you may still
have to reboot both computers.

Check the IP addresses of the two computers that cannot connect to each
other. They should be in the same subnet, i.e. the first three (or two or
one, depending on the subnet mask) numbers should be identical. A particular
cause can be Internet Connection Sharing (ICS), because enabling this
changes the IP address to 192.168.0.1. All other computers should be set to
obtain their IP addresses automatically (through DHCP) and may have to be
rebooted.

Check whether NetBIOS over TCP/IP is enabled. It should be for almost all
small and home networks. You can find this setting in the properties of the
LAN connection.
Double-click on the Internet protocol (TCP/IP), click on the Advanced button
in the lower right, click on the WINS tab and activate Netbios over TCP/IP.
You can later test whether the Standard setting is sufficient and use that
if it works. A more detailed description can be found in the chapter
"Netbios over TCP/IP".

Also make sure that the TCP/IP NetBIOS Helper service is running and has the
proper start type. Select Administrative tools, Services, and change the
Start setting for the TCP/IP NetBIOS Helper service to Automatic. Without
this service NetBIOS over TCP/IP will not function. Again a more detailed
description can be found in the chapter "Netbios over TCP/IP".
Have you really checked the NetBIOS node type as described in the form at
the top?

Make sure the computer browser service is running (see the special chapter
below). If you have to start it, reboot both computers.

If you notice that computers running older operating systems than Windows XP
disturb the computer browser system, you can try to disable the browser
service on those computers by stopping the service and setting its start
type to Disabled. Note, however, that you always need at least one computer
that can become a browser, otherwise Network Neighborhood or My Network
Places will not work. See also the special chapter on the computer browser
service below.

Make sure you have only one transport protocol installed, namely TCP/IP.
Remove, disable, or at least unbind (remove all bindings from) other
transport protocols like IPX (NWLink) and NetBEUI.


Uninstall third party client software that can interfere with the networking
settings. Such software could have come with network adapters or with a
router.

If you had other networking clients installed, like certain Netware clients,
you may be in for a long, bumpy ride. Some do damage that is almost
impossible to repair. You may want to try a repair installation of Windows
XP (if you have Internet Explorer 7 installed, first read, "How to perform a
repair installation of Windows XP if Internet Explorer 7 is installed" at
http://support.microsoft.com/kb/917964/), followed by applying Service Pack
2 again, or, better, a repair installation with a slipstream version of
Windows XP with Service Pack 2 already integrated. See the very first
chapter above for details.
Rid the computer of adware and spyware. For example, run Spybot Search &
Destroy. Please see the chapter "Winsock corruption" for details.

Repair the Winsock with the command: netsh winsock reset (This removes all
third party Layered Service Providers-LSPs. Please see the chapter "Winsock
corruption" for details.)

Repair the IP stack with the Repair command or with the command: "netsh int
ip reset c:\resetlog.txt" without the quotes. Please see the chapter
"Winsock corruption" for details.

If the loopback feature is enabled in a connected router, disable it. You
may even need a firmware upgrade.
Change the workgroup name in all computers to a new, simple, short, perhaps
even all upper case one, to make sure there aren't any problems there. You
can later change it back.

Check all NetBIOS names for possible duplicates. For example, if the
workgroup name coincides with a user or computer name, this could cause the
problem. Try opening a command line window and issuing the command: net view
Issue the command: net view \\computername, where computername should be
replaced with one of the names displayed with the simple net view command.
Check all names for possible duplication.

Check your router's diagnostic and information pages for NAT information,
like which computer has which IP address. Any duplication here could point
to the problem.

Disable, better uninstall or upgrade, all antivirus software and third party
firewalls.

If all this doesn't help, remove all networking components, reboot, then set
them up again and work through this checklist once more.

Two of these points are also explained in the following Microsoft Knowledge
Base article.

You cannot access shared files and folders or browse computers in the
workgroup
http://support.microsoft.com/kb/318030/

"Andy" <Andy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:31D6C505-00F4-4192-89C7-372B26B6DC27@xxxxxxxxxxxxxxxx
I've got a Dell desktop with MCE 2004 and a Fujutsu laptop with XP Home.
When they were connected by an ethernet cable they could be on the same
workgroup and share files.

Now I've got a US Robotics wireless router ....
Desktop is wired into it
Laptop is wireless using a USR card.
Firewalls are turned off

However, while the desktop can ping the laptop and share the files the
laptop cannot see the desktop! A ping returns no response and a net view
returns system error 53.

Whe I try to view network computers on the XP Home I get the message that
my
home netowrk is not accessible - I don't have permissions etc - but it
worked
fine with a direct connection and the network key etc is correct as both
computers can ping the router and access the internet.

When they were wired they allocated themseves IP addresses where-as when
they go through the router they take IP addresses that it issues them
with.
Could this make a difference?

I've read something about enabling simple filesharing but that is already
enabled on the MCE and is not an option I can find on XP Home.

Does anyone know how I can sort this out and get the router notwork
working
properly?

Am I being stupid??

Thanks in advance


.