´`´´Official Files Tutorial - How setup yourself as administrator

Page 2 of 2 FirstFirst 12
Results 16 to 17 of 17
  1. #16
    Apprentice Mistwalker is offline
    MemberRank
    Aug 2022 Join Date
    8Posts
    Quote Originally Posted by The Sourcerer View Post
    Client side IP and mac address.
    You are a scholar and a gentleman. Thank you kindly!!

    Finished restoring the databases to take another shot at it. :)

    EDIT: Still get a "Manager is not Registered" error when I try to log in, and the client shuts down. Hrm.

    EDIT AGAIN: OK, so if you're using VMWare to run the server in a VM, then you need to be very specific about which network adapter's addresses to register in the SQL database. In my case, the host's physical ethernet adapter and the IP address listed in the VM Network Map did NOT work. Probably obvious to anyone used to VMs.

    If, like me, you have a handful of adapters show up in /ipconfig and don't know which to use, ping your host machine's name from inside the VM and see which IP address bounces back. Use that adapter's IPv4 and MAC address. That's the one that finally let me log in as normal.

    This is all probably braindead simple to the veterans here, but maybe this will help another newcomer like myself.
    Last edited by Mistwalker; 11-08-22 at 07:04 PM.

  2. #17
    Valued Member The Sourcerer is offline
    MemberRank
    May 2022 Join Date
    CanadaLocation
    115Posts
    I am using Hyper-X for my VM mostly because it is not limited to 128GB memory like VMWare and the hypervisor is an actual 64-bit one. I found that if the server and client work through the same MAC address this happens. BDO really hates sharing server's IP/MAC addresses adapters with the client! In Hyper-X I had to assign one of my ethernet adapter's mac addresses exclusively to the server's adapter (I have 3 physical adapters) while the server is running.

    That leaves 2 (wired and wireless) addresses for my client to use. Since I usually turn my wireless off and I can register the remaining wired adapter's address and MAC for gm registration. That client adapter is still perfectly usable for all my other TCP work. I just can't use the server's adapter while a Hyper-V VM is running.

    Not sure if that helps, but that is how I got around that error.



Page 2 of 2 FirstFirst 12

Advertisement