RE: Win98 Machine

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Unfortunately that did not help. This is what the dialog box says when i try
to connect to the win98 machine from my Xp PC.

=====================================================
"\\K-tan is not accessible. You might not have permissions to use this
network resource. Contact the administrator of this server to find out if you
have access permissions.

The account is not authorized to log in from this station"
=====================================================

Ill have another look at the XP machines that can connect, but i am open to
any suggestions if anybody has any?

Thanks


"RobertNC" wrote:

> On the XP machines that can't connect to the 98 machine, check if "Simple
> file sharing" is turned on. If so, turn it off and see if that fixes it. You
> can also double check the setting on the XP machines that can connect to the
> 98 machine just to be sure.
>
> Click Start | My Computer | Tools | Folder Options | View.
> Scroll to the bottom of the list of advanced settings and un-check Use
> Simple File Sharing (Recommended).
> Click OK.
> --
> Bob
>
>
> "cjupiter" wrote:
>
> > A little bit of reverse engineering
> >
> > 8 PC's joined to a Small Business Server Domain.
> >
> > One of the PC's is a Win98 machine while the other 7 are all XP machines. At
> > the moment the Win98 PC has a printer connected to it. The printer is being
> > shared with everyone. 3 XP machines require to use this printer so they have
> > access to the Win98 machine some how. Whereas the other 4 XP machines can not
> > access the Win98 computer. The person who set the domain up to work this way
> > has gone away and i need to know how i can setup the other XP machines so
> > they can access the Win98 machine and then in turn access the printer.
> >
> > Another piece of information is that when I setup an XP machine in place of
> > the Win98 machine, and plugged the printer into that machine, the 4 XP
> > computers that couldnt see the Win98 PC can now see the replaced XP PC, but
> > the 3 XP machines that could originally see the Win98 PC can not see the
> > replaced XP machine.
> >
> > So im assuming that either something on the Server machine has been setup to
> > give the users of the 3 XP machines special access to the Win98 machine with
> > the printer. What would be these special privelages because i can not seek
> > them out.
> >
> > THanks
.



Relevant Pages

  • Re: Can I set up dual boot this way
    ... > operating systems due to programs that will not run under XP?" ... you're covered with the Win98 setup that you retained. ... clean install - reinstall everything (this will be tricky if you ...
    (microsoft.public.windowsxp.newusers)
  • Re: I give up...........
    ... That said, If I may, here is the way I normally install Win98 on a system. ... If it hangs somewhere during the ... running the setup from there accomplishes several things. ... Again I appologize if I'm suggesting something you've already tried. ...
    (alt.sys.pc-clone.dell)
  • Re: NT 4.0 Stand alone Server Un-securing
    ... Win98 can "connect as," too. ... setup to enter a login ID and password, try mapping a permanent drive to the ... server, ideally through a login script or a batch file in the system ...
    (microsoft.public.security)
  • Re: VB6: Probleme mit Winsock Steuerelement
    ... Das eine ist ein kleines Testprogramm, welches ich für das Winsock Problem benutzt habe. ... So, wenn ich nun auf einem frischen Win98 die kleine Winsock Anwendung installiere, dann geht alles. ... Wie sollte man denn nun eigentlich ein Setup bauen? ... Wenn ich nun darauf ein Setup baue, werden dann meine DLLs und OCXen genommen und sind diese auf einem Win98 Rechner nicht mehr lauffähig? ...
    (microsoft.public.de.vb)
  • accessing the I386 folder
    ... programs, from control panel, without needing to insert ... i remember when using win98 i was able to copy the win98 ... folder from the setup disk to the HDD, ... XP control panel, without having to keep putting in my xp ...
    (microsoft.public.windowsxp.setup_deployment)