WINNT 4.0, WIN95 : Can PING across network but cannot access resources.

[Michiel Byttebier]

Seeing a node in a network, but unable to access it's resources:

I have a similar problem

- Ping works all right from other PCs.
- From this one PC, I can see shares on other PCs.
- "Sharing drives & printers" is all right

HOWEVER:
- I cannot connect to network shares from this one WIN95 pc, neither from NT
or from any other PC's in the network
- I can reach a Vax over DECNET-pathworks although i cannot obtain
"licenses" to operate pathworks
- I cannot access shares on this PC from others.
- I can see all computers on 3 workgroups except this one in "network
neighborhood"

What can be wrong ?
Thanks for any reply
Michiel Byttebier

Carl Cox <cc...@appliedretail.com> wrote in message
news:7h0m5r$sfg$7...@nusku.cts.com...
> James;
>
> You didn't supply a lot of information beyond "it doesn't work", so a few
> questions are in order.
>
> 1. Is the NT Workstation running the Server Service?
> 2. Is the Win 95 box Client for Microsoft networks set to share files and
> printers?
> 3. Are the Workgroup names the same?
> 4. Can you find each other with Find Computer?
> 5. Do computers show in Net 'Hood?
>
> 15 more questions...
>
> --
> Carl Cox
> Systems Support Engineer
> Applied Retail Solutions, Inc.
> The opinions expressed are my own, not those of my employer.
>
> James T Waugh wrote in message <3733C3CD...@mediaone.net>...

> >I am trying to map drives and share files between an NT4.0 workstation
> >and a Windows'95 system. They are on the same LAN, same ethernet segment
> >and can ping each other. For some reason the drive mapping and file
> >share does not work.
> >Please help me.
> >JTW
> >
> >
>

[Lai Shu King]

which protocol you are using across different network. NetBEUI not ability
across the network to others.

[Alan Adams]

This may be very wide of the mark. However, in case it helps:

If you are running just TCP/IP as the common protocol (i.e. you don't
have Decnet on both machines, and you don't have NetBEUI on both, but
you do
have TCPIP, and in addition there is routing between the machines, then
you
have a mess like ours.

We use multiple class C networks on the same LAN cable and route between
them.
This breaks browsing and name resolution. Browsing is what you do when
you
look in Network Neighbourhood, name resolution is what you do when you
click on
a displayed system, or type \\<name> into Run etc. Different effects can
cause
one or the other to fail.

You may not know that you can (often) force a connection by using for
example
\\193.154.123.65 typed into the Run command (Start-> Run). This bypasses
name resolution and DNS and Wins address lookup. You can also use the
same
mechanisnm in Map Network Drive.

If this works it might in itself be a solution.

Next up is name resolution. If you can, you should use WINS. This does
work
across routers. Without Wins, resolution uses broadcasts, which don't
pass
routers. However, in a multiprotocol situation you may have an
additional
protocol such as Decnet which will work. (Multiple IP on a Lan is
separate
networks. The same machines running Decnet or NetBEUI are one network.)

Browsing always uses broadcasts, unless you have used the LMHOSTS
mechanism
to direct the messages (and which I've been unable to make work.
Probably
my fault.) However you can, as we have, get the situation where the IP
browse
master for your network is also running Decnet and hence knows about
machines
outside your broadcast domain. Hence you can browse them, but get
"network name not found" when you try to open them. As the browser
function
moves around, due to machines rebooting, the behaviour changes. Fun...

As I said, this may be totally irrelevent to you. More information would
help.

Alan Adams.

Michiel Byttebier wrote:
>
> Seeing a node in a network, but unable to access it's resources:
>