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.

Win2k to Win2k File Sharing

Discussion in 'Networking (Hardware & Software)' started by Yumei, 2002/08/27.

Thread Status:
Not open for further replies.
  1. 2002/08/27
    Yumei

    Yumei Inactive Thread Starter

    Joined:
    2002/08/27
    Messages:
    5
    Likes Received:
    0
    Ok... I hope that I'm posting in the right forum...

    Well... onto the problem. Both my brother and I have our computers right next to each other and we're both using Windows 2000 as our OS. We connected our computers with a Firewire cable and we're using Unibrain's Firenet thingie to attempt to share files. We got both of them connected to each other but I don't know how to access files on the other computer. I have set folders to share and set permissions to Everyone but...

    When I go to My Network Places and then Computers Near Me, I see both our computers listed there. Double clicking my computer is no problem, but when I double click on the other computer name, a message pops up asking for the network password and provides 2 slots for login and then the password. I have absolutely no idea what to input here. When I try to input a user on my computer, it doesn't work. And when I input a user from the other computer, it tells me "Logon failure: the user has not been granted the requested logon type at this computer. "

    So... I am at a complete loss as to what I am supposed to do. If someone would help, it would be greatly appreciated.
     
  2. 2002/08/27
    Profgab101

    Profgab101 Inactive

    Joined:
    2002/05/10
    Messages:
    239
    Likes Received:
    0
    Everyone?

    I'd be VERY carefull with those permissions...

    Easy way would be to create user accounts on each machine. Like george & jim. - the pass for jim is the same on both systems, and the same for george. (meaning the pass for george would be the EXACTLY same on each system, but different from jim.)

    Yes you will have to use the logon window and type your user name (last person to use the machine will be shown as default) and the password. - You can both use the same password, but not recommended, also as admin, you may want to set the passwords to never expire. (OK for home use, but bad practice otherwise.)

    This method also makes printer sharing a breeze.

    BTW - all you need to do is boot the remote computer, it can sit at a login screen and you can remote access & printshare without an local logon. - No need to even turn on the monitor.
     

  3. to hide this advert.

  4. 2002/08/31
    Yumei

    Yumei Inactive Thread Starter

    Joined:
    2002/08/27
    Messages:
    5
    Likes Received:
    0
    Umm... ok... I did what you said... I think. Made users of the same name/password for both computers. But it still gives me the same error...

    Also, it may have something to do with it (but I'm not sure), but on the sharing permissions, I have to have Everybody there. First off, if I try to go to the Look In drop down menu, it only has my computer and the workgroup. It does not show the other computer anywhere in there except in the workgroup's listing. If I try to add that, it does not work. If I do not add Everybody into my file sharing permissions, the other computer cannot even see my computer in the Computers Near Me from the My Network Places.

    I'm probably doing something wrong since I really have no clear idea of what I'm doing... can you suggest any other ideas to try out? Thanks in advance
     
  5. 2002/08/31
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Ignore the "network neighborhood" or whatever name it is going under.

    On computers Alpha & Bravo, add identical user accounts for each of you (which you have already done I think but make sure the account name and passwords exactly match what you use to log on - and case must match).

    On computers A & B, place each account in the "administrators" group.

    On computer Alpha, open windows explorer and select tools~map network drive. Then map to \\Bravo\c$ which is a hidden administative share that will always be there. Same for any other drives on Bravo. So if you have D & E for instance, you would map another drive to \\Bravo\d$ and another to \\Bravo\e$. And so on. This will work for hard drives, CD drives, etc.

    These new drives will show up and behave exactly like they were physically on Alpha.

    And were it me, I'd remove all except the administrators group from the permissions list. Remove rather than deny because if you deny access to the everyone group, that is exactly what happens. No one can connect regardless of what other groups or permissions they might have.

    Do the same mappings on Bravo to \\alpha\c$ , etc. and you should be good to go.
     
    Last edited: 2002/08/31
    Newt,
    #4
  6. 2002/09/01
    Yumei

    Yumei Inactive Thread Starter

    Joined:
    2002/08/27
    Messages:
    5
    Likes Received:
    0
    Aaack... Ok, I was doing what you said... the mapping network drive. I'm quite sure that both accounts on both computers are exactly the same case wise for name and password. But when mapping, after I input the \\(computer name)\c$ it gives me the same error as before.

    The mapped network drive could not be created because the following error has occurred:
    Logon failure: the user has not been granted the requested logon type at this computer.


    I checked the user names and passwords and they should be the same. For the permissions on shared folders I put the Administrator Group and both the user accounts in there...
    Well... any idea of what I'm doing wrong?
     
  7. 2002/09/01
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    I did some searching to find information on "Logon failure: the user has not been granted the requested logon type at this computer. " which is an error I've never seen before.

    Most were problems with domain-based accounts and most references cited NT4 rather than 2000. But the common thread was problems with accounts or account-rights.

    All I can figure is there is a problem with the accounts somewhere. My suggestion is to log on to each computer with a different account having local admin rights and delete the user accounts you are actually using to log on. Then recreate them. The will have a different security identifier and as far as 2K is concerned, will be completely new accounts.

    Then back thru the same drill as previously posted which is 1) use different logons for the two systems 2) list both accounts on each computer 3) add both accounts to administrators on both computers 4) try mapping to the admin shares (C$, whatever) again.
     
    Newt,
    #6
  8. 2002/09/03
    AndyO

    AndyO Inactive

    Joined:
    2002/04/04
    Messages:
    188
    Likes Received:
    0
    Could be totally off beam but as this FireWire networking (something which I profess to know nothing about) could it be that some different rights are required than normal ?

    I'm thinking that "this type of logon" means it needs logon locally or as aservice or something similar (which as Newt mentioned earlier are more domain type problems)

    I'm probably completely wrong but will do some digging as I'm intrigued now - have itch, will scratch !
     
  9. 2002/09/03
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Oops - totally missed the firewire from the original post. Good catch AndyO and you could be right. Odd though if the type of connection messed with the entire permissions structure. Odd but very possible. Could be the Unibrain as well. I know as much about those as a chicken does about astronomy.
     
    Newt,
    #8
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.