Networking Problems XP, ME & 95 PCs

From: Adrian White (awhite_at_demeter.demon.co.uk)
Date: 03/01/05


Date: Tue, 1 Mar 2005 02:01:57 -0000

Hi Folks,

Couple of problems I hope you folks can help out with. One simple problem
(I think), one somewhat more complicated that I'm still trying to get my
head around and will post later should I fail to resolve it myself.

So firstly the 'simple' problem.

I have been asked to look at a small home-office network which consists of 1
server running Windows XP Home Edition with SP2 installed and two clients, 1
of which is running Windows 95 and the other which is running Windows ME. A
notebook PC is usually bought into the office once a week or so to be
connected to the network for a quick bit of file dumping to the server; this
machine is also running Windows XP Home Edition with SP2.

The Server is a Dell Dimensions which is connected by it's built-in NIC to a
standard 10/100 3com hub. The Windows 95 & ME stations are home-brews
fitted with DEC 305 NICs. All are linked to the hub Via CAT 5. The
Fujitsu-Siemens notebook is hooked into the hub via it's CAT 5 port using a
spare hub lead.

All the machines are running IPX/SPX as the network protocols (running
TCP/IP causes problems with the Server when using DUN, hence IPX/SPX),
obviously MS Client for Networks and MS File & Print sharing is enabled.
Naturally all PCs have their individual names and all are members of the
same work group (it's a non-domain network).

The server has a number of shared folders (simple file sharing) and a shared
printer which the two home-brews and the notebook can access with no
problem. These can be accessed when both browsing Network Places and when
mapping a network drive. The Windows 95 & ME machines can also see one
another on the network and access shared resources in a similar fashion as
can the two XP machines see one another's shared resources.

However, neither of the XP machines (the Server and the Notebook) can see
either of the Windows 95/ME machines. Browsing their Network Places just
reveals themselves as part of the workgroup network with no sign of the
95/ME machines. Mapping the shares on either of the 95/ME machines to the
XP machines obviously results in no joy what so ever (path not found).

Some I have spoken to have suggested that the Network Browser may cause
problems when running on all machines in a mixed OS network such as this.
However I have tried disabling the computer browser on the XP machines and
the ME machine in turn neither of which actions have resolved the problem.

I have to confess to being a bit of an old fart (as they say here in the UK)
in the wonderful world of networking cutting my teeth as I did on Vax
servers (DEC Pathworks, ahhh, true-love !). So I'm hoping that you clever
folks out there will be able to help out with what is probably a simple
problem ( I Hope !!).

Many thanks for taking the time to read this posting.

Take care.

Ade

P.S. The other problem is much more complicated, hoping to resolve this
myself but if not you'll be hearing from me again !



Relevant Pages

  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.win2000.networking)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Connecting from Suse to windows workgroup on
    ... > pool of IPs) and I have just installed a Suse 9.3 Enterprise Server ... > From Suse pinging 127.0.0.1 works but no other machines on the Lan. ... problem with the network card or cabling... ...
    (alt.os.linux.suse)