“Cannot access system profile”

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #282
    AvatarGuenther
    Member
    • Total Post: 44
    • Frequent Flyer
    • ★★★

    Hi,

    I have a problem with a new server. We ran Rapport 4.4.1 on a Xp machine for a lot of months but now the pc crashed.
    So we hab to install a new PC and we also installed WDM 4.5.1 . After installing the licences and subnets we could discover all our clients.
    After a few days my users they note sth was wrong. The logon took very long and they do not use the resolution they are used to.

    So I controlled the settings on my server and compared them with the settings on the old machine, but there are obviously no differences.

    The Event Log always shows “Cannot access system profile” which mean they do’nt have access to the FTP, right?

    Where can I find further information?

    greets,
    Michael

    #9056
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    You are spot on, there is an issue and the terminals have “remembered” the old settings and can not find the new server. Does the new server have the same IP? Have you got the DHCP tags correct?

    Maybe to a Ethereal capture on the device and see where it is trying to go to?

    Hopefully WDM is on a server or in VMware now – mot on XP Pro 🙂

    #9058
    AvatarGuenther
    Member
    • Total Post: 44
    • Frequent Flyer
    • ★★★

    mhh…of course on Windows XP Pro 😥

    I’m using static IPs and the Event-Log shows me that he is in the correct “WDM”-group. The terminal appears in the correct group in WDM with status online.
    Also the correct image is assigned to the right group. The only thing that is not work is that the wnos.in from that image is not processing.

    The new server has the same IP, so I was hoping this will work properly.
    In the wnos.ini I used the parameter EnableLocal=yes so that could be the problem. How can i get rid of that?

    #9069
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    OK, check the event log of the WDM PC and see if there are any errors on ftp access or exceeding the 10 user limit. Open WDM and right click on the Master Repository and select test – did that all work?

    On the WTOS device have a look at the system log and see where the device was trying to get to:

    myserverip/office or whatever

    I am assuming here you have the enterprise version of WDM?

    Also jokes aside, you really should run enterprise on a Windows Server OS. I would recomend download ing VMware server (its free) at a minimum and running it there if you want to save on hardware. At least you can back it up and and dont have to worry about the PC crashing again. Secondly XP pro only supports 10 connections and this oftern causes problems when clients try to get the config.

    Finally as a matter of interest, if you G-Key a client to remove all prior settings does it work correctly with the new WDM server.

    Cheers,
    -TT

    #9078
    AvatarGuenther
    Member
    • Total Post: 44
    • Frequent Flyer
    • ★★★

    Hi TT,

    you are right. In the softwrae repository was the wrong IP of the WDM server. After I changed that we can connect to the FTP and use the system profiles. Thank you so much. I missed that point in my documentation but now I will add it.
    Thanks again.

    cheers,
    Michael

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.