1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

LAN connection problem between Windows XP and Windows 98

Discussion in 'Windows XP' started by JSS3rd, 2002/11/18.

Thread Status:
Not open for further replies.
  1. 2002/11/18
    JSS3rd Lifetime Subscription

    JSS3rd Geek Member Thread Starter

    Joined:
    2002/06/28
    Messages:
    2,221
    Likes Received:
    27
    I have three computers: XP Pro desktop and laptop (both NTFS), and Win98 SE desktop (FAT32) connected on an ethernet LAN via a router. Until recently, I was able to see files and folders on each of the other two computers from any of the three, and to print to either of the two printers (one parallel, one USB) connected to the XP desktop.

    For reasons unknown, I am no longer able to access the XP desktop computer (or the printers) from the Win98 computer, although I can access the XP laptop, and I can access the Win98 desktop from both of the XP computers. Instead, I get a password requester on the Win98 screen, stating:

    You must supply a password to make this connection:

    Resource: \\DESKTOP-XP\IPC$


    No password has ever been used in the past and, although DESKTOP-XP is the name of the XP desktop computer, no file or folder named IPC$ (or just IPC, for that matter) exists on either computer, nor is there a registry key referring that name on either computer.

    I should add that I am the only user of these computers, and all are free of viruses, spyware, etc.

    Any ideas or suggestions would be greatly appreciated.

    Jim
     
  2. 2002/11/18
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Yes it has. But automatically taken from the logon to the 9x box.

    This particular error is telling you the XP system has no clue who is trying to connect so is not allowing it.

    IPC$ - frustrating to try to find any information about this critter. The IPC is for interprocess communication and the $ indicates it is an administrative item. IPC is more of a method than a thing. Just remember an IPC$ network connection error means the PC can't figure out who you are.

    Win98 could care less "who" wants to connect so it isn't an issue there.

    All the NT operating systems demand to know "who" and must either recognize the logged on user or have you specify when you try to connect.

    Easiest fix is to make sure the 98 logon username and password are on both the XP systems as a user and that you always log on to the 98 PC with the username/password.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2003/01/28
    JSS3rd Lifetime Subscription

    JSS3rd Geek Member Thread Starter

    Joined:
    2002/06/28
    Messages:
    2,221
    Likes Received:
    27
    Hi Newt,

    Sorry I took so long to get back on this, but I only recently discovered the answer. When I said that no password had been used in the past, I spoke correctly ... neither of the XP computers has ever used a password, for anything. The Win98 computer requires a password for logon, just because it's on a LAN, but that's not the password the system seems to be looking for.

    While dealing with an entirely different problem, I discovered, quite by accident, that checking the Use Simple File Sharing box on the View tab in Folder Options (on the two XP computers) gave me complete access across the LAN, including the printers.

    Jim
     
  5. 2003/01/28
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Glad you got it fixed.

    Any time with any of the NT systems (NT4/2K/XP) that you get an error asking for a password to make an IPC$ connection, you are dealing with a network that isn't sure who is who.

    Thanks for the note on the simple file sharing. Never messed with it since it removes some security and will cause problems on larger, domain based networks. Not an issue on most home networks evidently. I set my home systems up without it but that was force of habit probably.

    I think I need to play with that at home some since most of the network issues with XP posted here are from folks with peer networks either in a small office or a home setup so my education is sadly lacking.
     
    Newt,
    #4
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.