Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / Networking and Web / November 2004

Tip: Looking for answers? Try searching our database.

xp home -> xp home

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
alfoilman - 29 Nov 2004 10:09 GMT
I have 2 pc's with a perplexing problem. Setup is as follows :

Machine a has two network cards, one for the lan ( hub ) and one for cable
modem. After a major problem with a firewall program we formatted and went
from w2000 to xp home. All networking from and to both machines and inet
sharing from machine a prior to this worked fine. Both machines could see
each other, transfer files etc and machine b could access the net via ics on
machine a with no problems at all.

After installation of xp home, the network became a one way thing only.
Machine a can see machine b and can access it's shared drives etc, even with
no account login ever asked for, no account on machine b of any shape or sort
other than the one that auto logs in, guest account is even turned off. logon
on machine a is very different from that of machine b. I did try adding user
accounts etc but it made no difference at all.

Machine b can access the net via machine a's ics arrangement but cannot even
see itself in the workgroup list of computers let alone access machine a.
Message seen is as follows :

' Home 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.'

As the user logged on has admin I cannot see for the life of me why it will
not work.

I have tried the network wizards, setting the ip's etc manually, 192.168.0.1
on  machine a's lan nic card, 192.168.0.5 on machine b, subnet numbers are
all right etc obviously as machine a can access machine b. I have tried
disabling the modem nic just to get the lan working, tried different ports in
the hub, all of which was wasted as machine b can go through machine a to the
net.

Any help will I am sure not only help me but countless dozens of others who
have the same problem of the one machine can access but not both dilemna.

regards to all

John
alfoilman - 29 Nov 2004 10:21 GMT
update :)

I can now see machine b in the workgroup but have this messgae which seems
to be the same for many others

\\elmo 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. Logon failure: the user has not been granted the
requested logon type at this computer

I notice there was a post for xp pro to fix this, is there a way for xp home
.

regards

John

> I have 2 pc's with a perplexing problem. Setup is as follows :
>
[quoted text clipped - 37 lines]
>
> John
Ron Lowe - 29 Nov 2004 12:27 GMT
> update :)
>
[quoted text clipped - 14 lines]
>
> John

By a strange co-incidence, some of us have been discussing this problem
off-line.
I wonder if you'd be kind enough to be a guinnea-pig for a little
experiment?

This error ought not occour on XP home.
It has Simple File Sharing hard-wired, and this makes all
sharing work through the Guest account behind-the scenes.

For come season, a security setting is getting accidentally set,
which prohibits Guest access across the LAN.
This is easy to fix on XP pro, but the necessary commands
are missing in XP Home.

Before we try this experiment, the first thing you should try is to
re-run the Network Setup Wizard on \\elmo. Often, that fixes up
the permissions correctly.   However, I suspect it won't fix this particular
one.

If you still get the error:

>Logon failure: the user has not been granted the
> requested logon type at this computer

then it's time to try this experiment.

First, on \\elmo, download and install the:
Windows Server 2003 Resource Kit Tools
http://go.microsoft.com/fwlink/?LinkId=4544

Once the install has finished, go to:

Start | All Programs | Windows Resource Kit Tools | Command Shell

Enter these commands, exactly as they appear here:

  net user guest /active:yes
  ntrights  +r SeNetworkLogonRight  -u Guest
  ntrights  -r SeDenyNetworkLogonRight  -u Guest

You should be notified that the rights have been succesfully granted or
revoked.

See if you can connect to this machine now.
Several of us watch with interest...

Signature

Best Regards,
Ron Lowe
MS-MVP Windows Networking

flisher - 29 Nov 2004 20:51 GMT
I had an indentical problem with 2 machines on Windows XP Home and this fix
worked !!  Thank you so much !  I have been up all weekend trying to figure
this out and I'm pretty sure I've tried every other solution out there.  

> First, on \\elmo, download and install the:
> Windows Server 2003 Resource Kit Tools
[quoted text clipped - 15 lines]
> See if you can connect to this machine now.
> Several of us watch with interest...
alfoilman - 29 Nov 2004 21:23 GMT
I tried the fix with no luck unfortunately although the message now changes a
bit from

"  \\elmo 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. Logon failure: the user has not been granted the
requested logon type at this computer "

to

"  \\elmo 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. Access denied "

I figure it must be getting very close now. It is so stupid tho that one way
it works yet the other way it doesn't and other than lan ip's both machines
are set the same.
Really do appreciate the help and am sure it's only going to be a short
matter of time before it gets sorted.

regards

John
Ron Lowe - 29 Nov 2004 22:31 GMT
>I tried the fix with no luck unfortunately although the message now changes
>a
[quoted text clipped - 24 lines]
>
> John

This has moved things along.
The guest account is no longer blocked at the front door, we're getting past
that.

Now, we are falling foul of either share permissions or NTFS permissions.

At his point, it may be worth re-running the network setup wizard.

Try un-sharing any shares you have created;
Run the Network Setup Wizard once again;
Re-share a folder as a test ( create a test folder if you like ),
and choose a simple share name.

Then try to connect from the other machine.
But not by browsing to \\elmo.
In the first instance, try to connect by mapping a network drive.
On the other machine, use windows explorer.
Tools \ Map network drive.
In the Folder box, enter \\elmo\sharename

Now what happens?
Do you get a prompt to supply any password?
What exactly does it say?

Signature

Best Regards,
Ron Lowe
MS-MVP Windows Networking

alfoilman - 30 Nov 2004 05:59 GMT
> This has moved things along.
> The guest account is no longer blocked at the front door, we're getting past
[quoted text clipped - 19 lines]
> Do you get a prompt to supply any password?
> What exactly does it say?

Well,

you will be very happy to know that fixed the problem. For whatever reason
it seems that you need to map the share to a drive on the machine that cannot
access the other machine via explorer through  My network places / microsoft
windows network / workgroup name. By mapping the 2 drives on the other
machine I now have full access to all files and am very happy :)

To coin a phrase, you rock dude :))))))))

This however does still not let me play lan games if machine A is serving
them, but that too will come :) I'd be keen to hear any other ideas to solve
this little problem you may have, installing other programs to do the job (
sygate ) seems a waste if xp should be able to do it.

Your help is much appreciated

regards

John
Carey Holzman - 30 Nov 2004 07:16 GMT
Sounds like this is your fix:

On the XP machines, click Start, click Run, type REGEDIT (hit enter)

Go to the following reg key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA

Look for "RestrictAnonymous" and ensure it is set to 0.

Reboot for changes to take affect

Carey

>> This has moved things along.
>> The guest account is no longer blocked at the front door, we're getting
[quoted text clipped - 45 lines]
>
> John
alfoilman - 30 Nov 2004 08:39 GMT
And oh my god, we have connection, elmo had a 1 for that value. It's all
fixed, YAY !!!!!!!!!!!!!!!! Now to get all the info together and type it up
so i don't lose it for next time i have to go through this.

Thankyou Carey for that final fix and Ron Lowe and Steve Winograd for all
your great help guys. Let's have a collective ' You guys ROCK ' :)

regards

John

> Sounds like this is your fix:
>
[quoted text clipped - 59 lines]
> >
> > John
Carey Holzman - 30 Nov 2004 23:55 GMT
Sounds like Ron, Steve and I each provided a little piece of your puzzle.

Glad to hear you got it working!

Carey

> And oh my god, we have connection, elmo had a 1 for that value. It's all
> fixed, YAY !!!!!!!!!!!!!!!! Now to get all the info together and type it
[quoted text clipped - 76 lines]
>> >
>> > John
Steve Winograd [MVP] - 29 Nov 2004 12:42 GMT
>update :)
>
[quoted text clipped - 12 lines]
>
>John

If Elmo runs XP Home, run the Network Setup Wizard on it.  That
usually solves the problem.

If that doesn't work, try this procedure, developed by Oli Restorick,
Ron Lowe, and me yesterday in response to a similar message:

1. Download and install the Windows 2003 Server Resource Kit Tools
from http://go.microsoft.com/fwlink/?LinkId=4544 .

2. Click Start | All Programs | Windows Resource Kit Tools | Command
Shell.

3. Type these lines at the command prompt to grant network logon
rights to the Guest account.  The second and third commands are
case-sensitive, so type them exactly as shown.  Note the "+r" in the
second one and the "-r" in the third one:

  net user guest /active:yes
  ntrights  +r SeNetworkLogonRight  -u Guest
  ntrights  -r SeDenyNetworkLogonRight  -u Guest
Signature

Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see.  I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Steve Winograd [MVP] - 29 Nov 2004 12:38 GMT
>I have 2 pc's with a perplexing problem. Setup is as follows :
>
[quoted text clipped - 37 lines]
>
>John

1. On the original or SP1 version of Windows XP, disable the built-in
Internet Connection Firewall on the local area network connection --
it's for use only on a direct modem connection to the Internet.  On
the SP2 version, enable the exception for file and printer sharing in
the Windows Firewall.

2. Use only one protocol for File and Printer Sharing.  If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them.  Details here:

Windows XP Network Protocol2
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on both computers:

 a. Open the Network Connections folder.
 b. Right click the local area network connection.
 c. Click Properties.
 d. Double click Internet Protocol (TCP/IP).
 e. Click Advanced.
 f. Click WINS.
 g. Click the Enable NetBIOS Over TCP/IP button.

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output.  If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem.  It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network, for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

  HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

  NodeType
  DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
Signature

Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see.  I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Steve - 29 Nov 2004 19:53 GMT
I dont seem to be able to programe share when networked (2 pc's) with XP
Home...... HELP!!!

> >I have 2 pc's with a perplexing problem. Setup is as follows :
> >
[quoted text clipped - 89 lines]
> TCP/IP and NBT Configuration Parameters for Windows XP
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.