9x cant access W2KPro

From: Phil (macgyver1@core.com.ignorethislastdot)
Date: 08/31/02 

From: "Phil" <macgyver1@core.com.ignorethislastdot>
Date: Sat, 31 Aug 2002 14:47:52 -0700

I have posted before on this one, and
still I am unable to resolve the problem.
We recently Upgraded our old peer-to-peer
thinnet cable bus network to a cat5 10/100
fast ethernet network with switch (star).
We have also replaced two machines with
new faster machines with Windows 2000
Professional installed. I have had no
problems getting the two new machines to
share files and resouces. But I am unable
to log into any of the resources on the W2KPro
machines from any of our older machines running
Win95 & Win98, which are the only other two
computers on the network. The W2KPro machines
can read from the 9x machines fine, even use
the printers on those machines. When I try to
access the W2KPro machines from the 9x machines
it asks for a password, which when I enter an
incorrect password it queries for the password
again, when I enter the correct password though,
all it does is lets me look into an empty folder
, drive whatever. I have file & print sharing
set up on all computers, tcp/ip is configured
correctly, users & passwords have been set up
and assigned to groups, username and password has
been set up on 9x boxes as well, but still nothing.

I have been watching the group now for some time,
and have seen many people with similar problems, I
have tried all of the solutions mentioned and none
have solved our problem.

Some of the fixed I've tried are:
-double checking ip addresses (manually set)
-double checked all share/rights/permissions
 logged on as administrator
-have allowed everyone full access/administrator
 rights just to see if I could access anything
 (I am not stupid I taken away those permissions)
-tried mapping drives
-looked for adclient to install on older machines
 on W2KPro CD, not there or on HDD
 (my guess that this is probably what I need to
  solve problem? Would be my luck.)
-tried using netbios & netbeui, no good.
-not using DHCP, so the only place I have
 ip's in DNS is the single machine that use dial-up
 out of (no jokes, it's small company) for the proxy
 server (yes, it's on the 95 machine)
-obviously, no Domain Controllers exist on the
 network we are using
-have uninstalled & reinstalled protocols & services
 and started from scratch
-several other things that I can not remember off
 the top of my head right now.

and I am ABLE TO Ping the W2KPro machines from the
Win98 & Win95 machines successfully!

So now that I have rambled on too much,

CAN ANYBODY HELP ME????

I appreciate any and all suggestions, really!

Thanks,
Phil
e-mail: macgyver1@core.com

Relevant Pages

  • Re: XP to Vista -- only halfway there
    ... concerning networks that combine Vista and XP machines. ... I am setting up an inhouse network that links together three machines, ... by 1) a misconfigured firewall or overlooked firewall (including stateful ...
    (microsoft.public.windows.vista.networking_sharing)
  • 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: Audacity and Gentoo
    ... can only pick up radio 4 when using the TV aerial to ... I freak if my machines disagree by more than about 50 ... > ADSL cable, 2 power cables, one network ...
    (uk.comp.os.linux)
  • Re: Active Directory Setup Advice
    ... A domain is really an entity with a single security remit. ... seen as on the same network it will be like one big network. ... Under one domain all machines have to be unique in naming scheme. ... sub domains you can have same names under different domain. ...
    (microsoft.public.windows.server.active_directory)
  • 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)