Dear Carsten,

on Thursday, January 06, 2000, 20:50, you wrote:

CD>>> If you do use it, sounds to me like the routing wants to go over DUN
CD>>> first, _then_ the network.

MH>> That is quite close, I think.  The question still is: why?

CD> Ahh, now that's always the deep one, ain't it!? ;]

CD>>> In that case I guess I can't help you except with the eternal
CD>>> "reinstall Windows" advice - which I try and avoid like the plague!
CD>>> ;] No, seriously though, maybe uninstalling DUN, rebooting and
CD>>> reinstalling could fix this.

MH>> I doubt that. If you read my original posting again you will see that
MH>> the DUN windows comes up only when sending mail. It does *not* come up
MH>> when retrieving mail.  On top of that, it does only come up the first
MH>> time when sending after launching TB.

MH>> Thus it looks like a TB problem to me, not like a Win98 problem. If it
MH>> would be a Win98 problem, it would happen always and not only when
MH>> sending mail.

CD> Hmm... Gotta admit, this one's got me stumped. Could you maybe send me
CD> how you configured your network (all params in the TCP/IP section)

OK, here are the properties of "TCP/IP -> Intel EtherExpress(TM) PRO/10+
(PnP enabled)" - sorry for some German terms:

Tab IP-Adresse:         "IP-Adresse festlegen" enabled
                        IP-Adresse : 192.168.1.1
                        Subnet Mask: 255.255.255.0

Tab WINS-Konfiguration: "WINS-Aufl�sung deaktivieren" enabled

Tab Gateway:            <no entry>

DNS-Konfiguration:      "DNS aktivieren" enabled
                        Host  : PC01
                        Dom�ne: AirTraffic
                        Suchreihenfolge f�r DNS-Server:    <no entry>
                        Suchreihenfolge f�r Dom�nensuffix: <no entry>

                        Remark (1): corresponding entries have been made
                                    in the HOSTS file in the Windows
                                    directory as well as in the NWHOST
                                    file in the Novell client directory

                        Remark (2): although DNS is enabled, I'm not
                                    using it.  In TB I have entered
                                    the IP address 192.168.1.1 for POP
                                    and SMTP server.

Tab NetBIOS:            "NetBIOS �ber TCP/IP aktivieren" enabled

Tab Erweitert:          "Bindung an ATM zulassen" = Nein
                        "Als Standardprotokoll definieren" disabled

                        Remark: enabling TCP/IP as the default protocol
                                does not change TB's behaviour

Tab Bindungen:          <no entry>


CD> and the DUN config as well (all params for everything)

Tab Allgemein:          Rufnummer: 0191011
                        "Ortsvorwahl und W�hlparameter verwenden" disabled
                        Verbinden �ber: MicroLink 56k pro

Tab Servertypen:        Typ des DF�-Servers: PPP: Internet, Windows NT
                                                  Server, Windows 98
                        Erweiterte Optionen: <all disabled>
                        Zul�ssige Netzwerkprotokolle: TCP/IP enabled,
                                                      all others disabled

Button TCP/IP-Einstellungen: "Vom Server zugewiesene IP-Adresse" enabled
                             "Vom Server zugewiesene
                             Namensserveradressen" enabled
                             "IP-Header-Komprimierung" enabled
                             "Standard-Gateway im Remote-Netzwerk
                             verwenden verwenden" enabled

                             (What does the latter mean BTW?)

Tab Skript:             <no script>
                        "Terminalfenster minimiert starten" enabled

Tab Multilink:          "Keine zus�tzlichen Ger�te verwenden" enabled


CD> and then get the output of the following commands (done in a DOS
CD> window):

CD> route print

Aktive Routen:

  Netzwerkadresse      Subnet Mask  Gateway-Adresse    Schnittstelle  Anzahl
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1       1
      192.168.1.0    255.255.255.0      192.168.1.1      192.168.1.1       1
      192.168.1.1  255.255.255.255        127.0.0.1        127.0.0.1       1
    192.168.1.255  255.255.255.255      192.168.1.1      192.168.1.1       1
        224.0.0.0        224.0.0.0      192.168.1.1      192.168.1.1       1
  255.255.255.255  255.255.255.255      192.168.1.1          0.0.0.0       1

CD> netstat -a


Aktive Verbindungen

  Proto  Lokale Adresse         Remote-Adresse            Status
  TCP    PC01:smtp              0.0.0.0:0              LISTENING
  TCP    PC01:pop3              0.0.0.0:0              LISTENING


This output is related to the local mail server that is running on my
machine, I believe. But what is interesting: the output above is the one
I get *after* I established an SMTP connection to our local mail server
at least once (and remember, the DUN windows comes up only the first
time when sending mail after launching TB). *Before* I established such
an SMTP connection the first time after launching TB, I get the
following output:


Aktive Verbindungen

  Proto  Lokale Adresse         Remote-Adresse            Status
  TCP    PC01:smtp              0.0.0.0:0              LISTENING
  TCP    PC01:pop3              0.0.0.0:0              LISTENING
  TCP    PC01:1135              pc01.airtraffic:pop3   TIME_WAIT
  TCP    PC01:1136              pc01.airtraffic:pop3   TIME_WAIT
  TCP    PC01:1137              pc01.airtraffic:pop3   TIME_WAIT
  TCP    PC01:1138              pc01.airtraffic:pop3   TIME_WAIT
  TCP    PC01:1139              pc01.airtraffic:pop3   TIME_WAIT


This irritates me.  Why is the status "TIME_WAIT"?  I have set up TB to
fetch mail for all 5 accounts at startup, so this looks to me as if TB
would not clear the connection with the local mail server properly. Or
might there be a problem with the mail server even?

When I now send a test message from one of the 5 accounts, the DUN
window comes up, I cancel it and the message is being sent. After that,
the output of "netstat -a" is :


Aktive Verbindungen

  Proto  Lokale Adresse         Remote-Adresse            Status
  TCP    PC01:smtp              0.0.0.0:0              LISTENING
  TCP    PC01:pop3              0.0.0.0:0              LISTENING
  TCP    PC01:1140              pc01.airtraffic:smtp   TIME_WAIT


Hmm, even different to the first output above.  Now I'm sending another
test message (DUN windows does not come up anymore) and get the
following output of "netstat -a":


Aktive Verbindungen

  Proto  Lokale Adresse         Remote-Adresse            Status
  TCP    PC01:smtp              0.0.0.0:0              LISTENING
  TCP    PC01:pop3              0.0.0.0:0              LISTENING
  TCP    PC01:1141              pc01.airtraffic:smtp   TIME_WAIT


Hmm, again different and now I wonder how I managed to get the first
2-line output above. Damn, I'm not familiar with that stuff, maybe you
can draw the right conclusions.

CD> With  that info maybe (and that's a big maybe! ;] ) I could figure out
CD> what's happening... I still kinda think it's a Win98 problem.

A big thank you for your efforts, Carsten!  Hope it'll help (me). ;-)


Best regards,

-- 
Michael Heydekamp
AIR TRAFFIC Euro Charter GmbH
eMail: [EMAIL PROTECTED]
http://www.airtraffic.de

*----------------------------------------------------------*
  Using The Bat! 1.38e under Windows 98 4.10 Build 2222  A 
  on a PIII/450, 128MB RAM, 10GB Harddisk
  in a NetWare 3.12 network environment
*----------------------------------------------------------*



-- 
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
   <mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
   <mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------

Reply via email to