W98 to XP connection problem

Two desktop PCs:
1. running W98 SR2 with a wireless PCI adapter
2. running XP with PCI adapter cabled to wireless router.

Both have shared drives and printer sharing is permitted.

Network Neighborhood:
- on W98 PC, clicking on Entire Neighborhood -> "Cannot browse network" and
its properties are "unavailable".

- on the XP PC network Neighborhood shows the W98 PC but cannot access its
files: "... is not
available. ..... Network path not found".

********YET!!, when searching for the XP PC by name, it is found (!) AND W98
PC can see the XP PC and open its files. (On the XP searching for the W98 PC
also finds it but cannot open it).

IP numbers etc. seem correct. What could be the problem?

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

Jeff

I run a similar set up. I usually just run the xp network setup wizard from
the xp installation disk in the w98 machine, follow the prompts and every
things up and running.

A couple of things to check:

1. Is the work group name the same on both machines.
2. Are either of the machines running a firewall.
3.Can you ping the ip addresses in both directions.

Regards

Jon
"Jeff Malka" <(E-Mail Removed)> wrote in message
news:PDHGb.39199$A%(E-Mail Removed)...
> Two desktop PCs:
> 1. running W98 SR2 with a wireless PCI adapter
> 2. running XP with PCI adapter cabled to wireless router.
>
> Both have shared drives and printer sharing is permitted.
>
> Network Neighborhood:
> - on W98 PC, clicking on Entire Neighborhood -> "Cannot browse network"
and
> its properties are "unavailable".
>
> - on the XP PC network Neighborhood shows the W98 PC but cannot access its
> files: "... is not
> available. ..... Network path not found".
>
> ********YET!!, when searching for the XP PC by name, it is found (!) AND
W98
> PC can see the XP PC and open its files. (On the XP searching for the W98
PC
> also finds it but cannot open it).
>
> IP numbers etc. seem correct. What could be the problem?
>
> --
>
> Jeff McPherson
> Email address deliberately false to avoid spam
> (E-Mail Removed)
> Outgoing mail is certified Virus Free by AVG
>
>
>

"Jeff Malka" <(E-Mail Removed)> wrote in
news:PDHGb.39199$A%(E-Mail Removed):

> Two desktop PCs:
> 1. running W98 SR2 with a wireless PCI adapter
> 2. running XP with PCI adapter cabled to wireless router.
>
> Both have shared drives and printer sharing is permitted.
>
> Network Neighborhood:
> - on W98 PC, clicking on Entire Neighborhood -> "Cannot browse
> network" and its properties are "unavailable".
>
> - on the XP PC network Neighborhood shows the W98 PC but cannot access
> its files: "... is not
> available. ..... Network path not found".
>
> ********YET!!, when searching for the XP PC by name, it is found (!)
> AND W98 PC can see the XP PC and open its files. (On the XP searching
> for the W98 PC also finds it but cannot open it).
>
> IP numbers etc. seem correct. What could be the problem?
>

I think you're going to need a setup disk that the XP Wizard creates that
allows the XP machine to access non NT based O/S when installed.

I conversed with a couple of other people about this issue between XP and
Win 9'x O/S and File and Print sharing, that is not even happening
successfully even on an all wired connection.

XP can see and access Win 9'x but Win 9'x cannot access XP. And it's the
other way around too. Then some work period both ways The MS specs for
connections for non NT based machines to NT based OS is to use NWlink
IPX/SPX NetBios compatible on NT based O/S and IPX/SPX over NETbios on
Win 9'x O/S(s).

Some people have reported just using Netbeui to Netbeui works and some
don't.

It's kind of messed-up.

Duane

In message <Xns945CB1A20F425darnold92insightbbco@216.148.227. 77>, Duane
Arnold <(E-Mail Removed)> writes
>I think you're going to need a setup disk that the XP Wizard creates
>that allows the XP machine to access non NT based O/S when installed.

A further complication: if you mess with any file permissions in the XP
shared directories networking can fall over, sometimes to the point of
crashing *other* machines on the network! Unfortunately the default
settings appear to have dubious security ;(

--
Paul Shirley: email anti-spammed