[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::excursion

Title:note 3 has pointer to current kit
Notice:note 3 has pointer to current kit
Moderator:PEACHS::GHEFF
Created:Wed May 29 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3301
Total number of notes:14905

3271.0. "wxserver dies when using access control?" by CSC32::A_SHERLOCK () Fri Apr 18 1997 19:46

    I installed excursion v3.0 from the ssb kit (xcursionssb.zip) on jamin. 
    I'm using windows 95.  It seems to work fine, until I try to enable
    access control.  If I add a host to either the 'valid nodes' section or
    the 'controlling hosts' section, as soon as I click 'Apply' wxserver
    dies with an "invalid page fault" error.
    
    If I put in an unresolvable hostname, or an ip address, I get the
    (expected) error that it can't be resolved.  Once I put in a valid
    hostname, that's when wxserver dies.
    
    In order to get it going, I have to clear the entry from the 'existing
    nodes' box.
    
    Are there any known problems like this? 
    
    Thanks for any info!
    Al
T.RTitleUserPersonal
Name		DateLines
3271.1PEACHS::GHEFFDo you feel like swimming?Fri Apr 18 1997 20:5815
    Haven't seen this one.  I just did the same thing on Win95 and got the
    correct behavior.
    
    You're saying that you have the control panel and the xserver running
    at the same time, and you add a resolveable host name to the valid
    nodes list and hit apply, the server immediate crashes?  Odd that
    cpanel stays up and wxserver bites it.
    
    I wonder if we're getting bogus data being fed to wserver.  I recently
    saw a case where even though the registry looked clean from regedit,
    wxserver was getting incorrect information out of it.  (Specifically, it
    was looking for its rgb.txt file in "" instead of
    "c:\win32app\xcursion\common\rgb.txt")
    
    #Gary
3271.2CSC32::A_SHERLOCKSat Apr 19 1997 00:1522
    Yes, wxserver dies and cpanel stays up.  Here is the complete error:
    
    WXSERVER caused an invalid page fault in
    module WSOCK32.DLL at 0137:7e2e7bdf.
    Registers:
    EAX=0401a8c0 CS=0137 EIP=7e2e7bdf EFLGS=00010202
    EBX=00531cb0 SS=013f ESP=0075ea4c EBP=00531cf8
    ECX=00000000 DS=013f ESI=00531134 FS=0de7
    EDX=00531598 ES=013f EDI=00531d08 GS=0e36
    Bytes at CS:EIP:
    8b 00 89 45 04 74 10 c7 43 10 01 00 00 00 c7 43 
    Stack dump:
    0075eb60 006305a0 00531134 0063079c 00000002 bffb8b40 00000001 7e2e7506
    00531134 887c0000 00000001 00531c98 0075eb00 0075edbc 0075eafc 0075ea98 
    
    I deleted everything according to the instructions in the 3.0 release
    notes, and reinstalled.  I still have the same problem.  The server
    will only run if the 'existing nodes' box is clear.
    
    Very strange...
    
    Al
3271.3more info...CSC32::A_SHERLOCKSat Apr 19 1997 20:498
    It only happens if the node is listed in the local hosts file
    (c:\windows\hosts).  
    
    If it has to use dns to resolve the hostname, it works fine.  But if
    you try to enter a node that's listed in the hosts file, the server
    crashes!
    
    Al
3271.4PEACHS::GHEFFDo you feel like swimming?Mon Apr 21 1997 14:2810
    I'm afraid I've just got a subtle difference in my config.  I removed
    dns from my Win95 PC, and rebooted.  Then I added a few of my systems
    to the hosts file.  Then I brought up wxserver and control panel.  In
    cpanel I added the hosts to valid nodes and nothing untoward happened. 
    I added a controlling host and nothing bad happened.  Just for fun, I
    stopped and restarted the server, and again nothing bad happened.  
    
    I just don't know what's different about my system.
    
    #Gary
3271.5CSC32::A_SHERLOCKTue Apr 22 1997 13:549
    Hmmmm...
    
    I installed the same kit on another win95 system, and had the same
    problem.  So, I installed it on a third win95 system, and it doesn't
    have the problem!
    
    Now I'm trying to figure out what the difference is...
    
    Al
3271.6gotcha!CSC32::A_SHERLOCKFri Apr 25 1997 21:0028
    Finally!  Figured this one out...
    
    This problem probably won't affect too many people, since the following
    conditions must be met to reproduce it:
    
    1.  The system has to be configured for both ethernet and dialup
    networking.  The dialup networking interface doesn't have to be active,
    but it does have to be configured.
    
    2.  Both the ethernet and dialup interfaces must have the "specify an
    ip address" box checked.
    
    3.  The system has to have c:\windows\hosts, and one of the hostnames
    in that file must be entered into access control in excursion.
    
    If all three of the above conditions are met, wxserver will die
    immediately at startup. 
    
    I found a reference to this problem at:
    
    http://www.melee.com/morsel/fix/nn-vs-w95/avoid_npe.html
    
    In that case, they had the same problem with wsock32.dll, but the
    application that triggered the fault was netscape.  They also list
    workarounds, which are basically to eliminate any one of the above
    three conditions.
    
    Al
3271.7PEACHS::GHEFFDo you feel like swimming?Mon Apr 28 1997 12:459
    Wow!  Never seen that one before.  Thanks for following up with us.
    I bet I'll see this one again.  (I regularly get calls from folks who
    have both ethernet and dialup networking.)
    
    I didn't have dialup networking configured on my PC.  Guess that's why
    I didn't see it.  (And I doubt I have a hosts file specified.  A
    surprising number of customers do run that way, however.)
    
    #Gary