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

Conference gyro::internet_toolss

Title:Internet Tools
Notice:Report ALL NETSCAPE Problems directly to [email protected].rnet? Read note 448.L for beginner information.
Moderator:teco.mro.dec.com::tecotoo.mro.dec.com::mayer
Created:Fri Jun 25 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4714
Total number of notes:40609

4643.0. "Altavista Tunnel Client and Win NT Server v4" by NNTPD::"[email protected]" (John Scott) Wed Apr 30 1997 21:18

I use Windows NT Server v4 on my home system.  I have installed Altavista 
Tunnel v1.1 Client on this system (release kit, same one I installed on my
laptop running Windows NT Workstation v4).  Works fine on the laptop.  On my
server when I connect I get TONS of messages in the event log.  Generally 6
messages about 1 sec apart, with about 2 minutes between groups.  The messages

are all:

        The description for Event ID ( 1 ) in Source ( Deccore ) 
        could not be found. It contains the following insertion 
        string(s): , PSUDO, [DECPSUDO] Adapter 16.66.160.2 filter fixed p.

I have reported it to CCS several times with no repsonse.  The tunnel seems
to work okay, just fills up the event log.

Any ideas what I need to do to the server to get this to stop?
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
4643.1Know Problemsmoken.imc.das.dec.com::BRUNELLEThu May 01 1997 00:0412
    John,
    
    Not sure who in CCS you have reported this to.  But this is a known
    problem with the NT client.  As far as I know, there is no resolution
    for the current version.  Maybe the new release called Tunnel 97 will
    correct it.
    
    I would also suggest you contact the Altavista Engineering Group.  A
    good person to start with is Jeff Needle at dtn 226-2160.
    
    John
                                         
4643.2a-61.tunnel.crl.dec.com::needleMoney talks. Mine says "Good-Bye!"Thu May 01 1997 15:2514
Try the new client.  This is a Microsoft bug that we're reporting - our adapter
is receiving packets from addresses that are incorrect, so we report it because
we figure it's an attempt to subvert the client.  Unfortunately, due to a
brain-dead bug in SMB, packets with incorrect source addresses are sent out
all the time (see MS Knowledge Base article q155986 for a hint at a tiny
piece of the problem).

And please, folks, don't call me before trying your normal channels.  I'm
already on the phone 20 hours a day with customers as it is.  If your normal
channels can't help, we have a support organization who can be reached at
1-800-336-7890.

j.