Networking Problem

I have tried to network 2 winxp pentium computers through a
router.Both computers can access the internet through the router .
I have used the setup wizard on both computers a number of times .I
get the same results in that when I get to the MSHOME icon the
computer goes no further and I get a window with the folling .

"Mshome not accessable .You might not have permission to use this
resource.Contact the adminstrator of the server to find out if you
have access permissions.
The list of servers for this workgroup is not currently available "

This window shows up on both computers .Im sure that I have missed
something.

Ive done searches on Google and can find lots of references to this
problem but cant seem to zero in on the fix .

HELP>>>>TIA

Flipper

I've noticed this too.

Can you ping the other computer? (Assuming you're using TCP/IP)

If you can, you can try accessing the computer's files by typing \\192.168.1.1
for example in the Run box.

This is the only way I can currently access my WinNT machine from Windows XP

OleDawg wrote:
> I have tried to network 2 winxp pentium computers through a
> router.Both computers can access the internet through the router .
> I have used the setup wizard on both computers a number of times .I
> get the same results in that when I get to the MSHOME icon the
> computer goes no further and I get a window with the folling .
>
> "Mshome not accessable .You might not have permission to use this
> resource.Contact the adminstrator of the server to find out if you
> have access permissions.
> The list of servers for this workgroup is not currently available "
>
> This window shows up on both computers .Im sure that I have missed
> something.

I've sometimes noticed that it works much better if you share your resources
through the administrator account, rather than any other account, even if
those accounts have administrator-level privileges.

If that fails then as somebody else has pointed out, use the IP address of
the other computer directly.

Yousuf Khan

Thanks for the come back .Its fixed .The first suggestion that I tried
was to install ipx/spx protocol (tcp/ip was already installed ).It
worked .Each computer saw the other immediately .Note that there were
other comments that the new protocol was not needed if tco/ip was
installed ,but it worked on this inatallation .
Thanks again

Flipper

On Mon, 12 Jul 2004 18:52:05 GMT, "Yousuf Khan" <(E-Mail Removed)>
wrote:

>OleDawg wrote:
>> I have tried to network 2 winxp pentium computers through a
>> router.Both computers can access the internet through the router .
>> I have used the setup wizard on both computers a number of times .I
>> get the same results in that when I get to the MSHOME icon the
>> computer goes no further and I get a window with the folling .
>>
>> "Mshome not accessable .You might not have permission to use this
>> resource.Contact the adminstrator of the server to find out if you
>> have access permissions.
>> The list of servers for this workgroup is not currently available "
>>
>> This window shows up on both computers .Im sure that I have missed
>> something.
>
>I've sometimes noticed that it works much better if you share your resources
>through the administrator account, rather than any other account, even if
>those accounts have administrator-level privileges.
>
>If that fails then as somebody else has pointed out, use the IP address of
>the other computer directly.
>
> Yousuf Khan
>

OleDawg wrote:
> Thanks for the come back .Its fixed .The first suggestion that I tried
> was to install ipx/spx protocol (tcp/ip was already installed ).It
> worked .Each computer saw the other immediately .Note that there were
> other comments that the new protocol was not needed if tco/ip was
> installed ,but it worked on this inatallation .
> Thanks again

The old Novell IPX/SPX networking protocol had one big advantage over
TCP/IP, and that advantage was that it was selfconfiguring within the local
network. Pretty much all network cards would be assigned their own network
addresses without the need external services such as DHCP, DNS, etc.
Understandable, given that TCP/IP's background is as a networking protocol
for Wide Area Networks (WANs), while IPX was a protocol for Local Area
Networks (LANs). These days TCP/IP is also used within LANs to keep the
protocol stack simpler.

If you found that IPX worked for you, then you might find that another
protocol designed for local area networks, might do equally well for you,
which is Microsoft's NetBEUI protocol. And it might have lower resource
requirements too, since it was Microsoft's own protocol in the past.

Yousuf Khan

On Tue, 13 Jul 2004 17:04:31 GMT, "Yousuf Khan" <(E-Mail Removed)>
wrote:

>OleDawg wrote:
>> Thanks for the come back .Its fixed .The first suggestion that I tried
>> was to install ipx/spx protocol (tcp/ip was already installed ).It
>> worked .Each computer saw the other immediately .Note that there were
>> other comments that the new protocol was not needed if tco/ip was
>> installed ,but it worked on this inatallation .
>> Thanks again
>
>The old Novell IPX/SPX networking protocol had one big advantage over
>TCP/IP, and that advantage was that it was selfconfiguring within the local
>network. Pretty much all network cards would be assigned their own network
>addresses without the need external services such as DHCP, DNS, etc.
>Understandable, given that TCP/IP's background is as a networking protocol
>for Wide Area Networks (WANs), while IPX was a protocol for Local Area
>Networks (LANs). These days TCP/IP is also used within LANs to keep the
>protocol stack simpler.
>
>If you found that IPX worked for you, then you might find that another
>protocol designed for local area networks, might do equally well for you,
>which is Microsoft's NetBEUI protocol. And it might have lower resource
>requirements too, since it was Microsoft's own protocol in the past.
>
> Yousuf Khan
>
Thanks .In getting the network going I ended up with 3 protocols
installed .

netbios
ipx/spx
tcp/ip

Now thats probably not good ,but the ststem is working so Im leaving
it alone .
I have one other thing that makes me wonder . When I open the network
neighborhood ,I see all the drives on both computers listed ???

Flipper

OleDawg wrote:
> Now thats probably not good ,but the ststem is working so Im leaving
> it alone .
> I have one other thing that makes me wonder . When I open the network
> neighborhood ,I see all the drives on both computers listed ???

Your own computer is also part of the network neighbourhood afterall.

Yousuf Khan

On Tue, 13 Jul 2004 23:20:18 GMT, "Yousuf Khan" <(E-Mail Removed)>
wrote:

>OleDawg wrote:
>> Now thats probably not good ,but the ststem is working so Im leaving
>> it alone .
>> I have one other thing that makes me wonder . When I open the network
>> neighborhood ,I see all the drives on both computers listed ???
>
>Your own computer is also part of the network neighbourhood afterall.
>
> Yousuf Khan
>
Makes since ! TNKS

Flipper

Another question.Do need all of the protocols installed ,or just the
one that got me working (ipx/spx.I guess I could try deleting them to
find out but Im afraid I might screw things up again after it took me
so long to get it fixed.

Flipper

On Tue, 13 Jul 2004 23:20:18 GMT, "Yousuf Khan" <(E-Mail Removed)>
wrote:

>OleDawg wrote:
>> Now thats probably not good ,but the ststem is working so Im leaving
>> it alone .
>> I have one other thing that makes me wonder . When I open the network
>> neighborhood ,I see all the drives on both computers listed ???
>
>Your own computer is also part of the network neighbourhood afterall.
>
> Yousuf Khan
>

OleDawg wrote:
> Another question.Do need all of the protocols installed ,or just the
> one that got me working (ipx/spx.I guess I could try deleting them to
> find out but Im afraid I might screw things up again after it took me
> so long to get it fixed.

No, I'd just go with whatever is working. I was just suggesting NetBEUI as
an alternative to IPX/SPX, because it might be lower overhead, but it really
doesn't matter, as long as it's working.

Yousuf Khan