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

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

525.0. "win95 client problems" by NCMAIL::LEFFLERM () Tue Mar 25 1997 10:59

    I am having problems with a win95 client.
    
    Whenever I start up the user or administrator application from the
    client, I get a message saying "connecting to server", then I get 3
    pop-ups in a row, all saying something like "winworker - This program
    has caused an illegal operation and will be shut down". The details
    button reveals that "WINWORKR caused an invalid page fault in module
    WSOCK32.DLL ...etc"
    
    This client can ping the server (A UNIX machine) and vice versa. I have
    NT clients being backed up on the same server with no problems.
    
    Any suggestions?
    
    Thanks,
    Mark 
T.RTitleUserPersonal
Name
DateLines
525.1DECWET::KOWALSKITime's not for savingTue Mar 25 1997 11:133
Do you have tcp/ip setup on this 'W95 system?
Please provide version info for NetWorker on
the client.
525.2tcp is setupNQOS01::bfo7.bfo.dec.com::lefflerTue Mar 25 1997 11:319
Yes, TCP is setup. I can ping the server, the server can ping the 
client, the w95 machine has full internet access, etc. 

The w95 kit was copied off of slugbt.zso.dec.com this AM, came over 
as win95.zip. Although I can not start the admin or user program to 
verify the version, the Scheduled Backup Program reports that it is 
version 4.2.

-Mark
525.3Goto DOSDECWET::KOWALSKITime's not for savingTue Mar 25 1997 12:2310
So, apparently some of the client is running (scheduled
backup), right?

What happens if you start a window in the Dark Place,
cd \"Program Files"\legato\nsr\bin
and perform this command:

winadmin -s <server name>

?
525.4no luckNQOS01::bfo7.bfo.dec.com::lefflerTue Mar 25 1997 12:5110
The same ugly error message(s). When I don't specify a server, it 
searches for about 60 seconds then I get the errors.

The client has been added at the server using the server admin tool.

I've de-installed (manually removing the registry entries) and 
re-installed, no luck. I think I'll find another w95 box & try 
installing there.

-Mark
525.5fixedNQOS01::bfo7.bfo.dec.com::lefflerTue Mar 25 1997 13:547
The problem was that this was a laptop with the AltaVista Pseudo 
Tunnel adapter installed. Networker was getting a bogus address from 
the tunnel adapter instead of the correct address from the ethernet 
card. I released the Tunnel adapter address & everything works fine 
now. 

-Mark
525.6GCUVAX::PALMERLife: Eternity&#039;s Field TestWed Apr 09 1997 11:0922
    I'm seeing the same set of errors on two Windows 95 machines which have
    the Tunnel software installed.  Both report this error message
    regardless of whether I have the tunnel active or not:
    
    WINWORKR caused an invalid page fault in
    module WSOCK32.DLL at 0137:7e2e7bdf.
    Registers:
    EAX=7a108810 CS=0137 EIP=7e2e7bdf EFLGS=00010202
    EBX=00820094 SS=013f ESP=00a3e9fc EBP=008200f4
    ECX=00000000 DS=013f ESI=00910034 FS=3187
    EDX=00910498 ES=013f EDI=00820104 GS=31b6
    Bytes at CS:EIP:
    8b 00 89 45 04 74 10 c7 43 10 01 00 00 00 c7 43 
    Stack dump:
    00a3eb10 00910f40 00910034 00910cb4 00000003 bffb8b30 00000002 7e2e7506
    00910034 88700000 00000001 0082007c 00a3eab0 00a3ed6c 00a3eaac 00a3ea48 
    
    Any ideas?  I can't deinstall the tunnel, because that's how I connect
    back in to Digital, yet it's painful to run Windows Backup to a
    NT-served drive and then NSR-backup that.
    
    --Ed