P
Pat Garard
FIRST POSTED AUG 16, 2003 - Windows XP TCP/IP - ISP Issues with an
attachment.
1 reply to Group, 4 responses by e-mail (all experiencing similar problems)
and a Deafening Silence from Microsoft!
The attachment is now included in full (below).
Pat Garard
Australia
=============== Begin Original Attachment =====================
Telstra (Australia) ISP Connectivity - TCP/IP Issues
I am comparing the behaviour of Telstra (Australia) LaunchPad under Windows
XP, with that under Windows 2000. In both cases the IP address is obtained
using Telstra DHCP and DNS.
For the purposes of comparison during testing, I have used the generic ISP
software called BPALogin.
There appear to be some issues with Windows XP TCP/IP.
Windows 2000
Telstra LaunchPad (Proprietary connectivity tool) could be set up to start
in "Startup" and auto-connect to Telstra consistently and without problems.
This was entirely transparent to the User.
Windows XP Professional - After upgrade
Telstra LaunchPad could be set up to start in "Startup" but auto-connect to
Telstra consistently failed.
It was necessary to remove LaunchPad from "Startup", and always to manually
start LaunchPad after User Startup was complete (little or no disk activity
after services had started). This usually worked ok, but the connection
would "drop out" 2 to 3 times per session of about 7 hours. LaunchPad would
show "Connected", and a Network Connection "Repair" would normally restore
service.
Windows XP Professional - After IIS and ActiveSync
There are two (2) Network connections: ISP via Cable Modem and 10Mbs-1
Ethernet Card, and ActiveSync via COM1 and Direct Cable (VPN).
Immediately after User Startup but before connection:
It could be seen (in a command window) that ping and ftp have access to DNS,
on the Telstra Network, and that ftp is capable of remote access on the
Telstra WAN - the lower layers of the OSI Model are working as expected.
Two ISP Connectivity Tools are available:
Telstra LaunchPad
BPALogin
(BUT NEITHER IS YET RUNNING).
Windows Messenger will not Sign In.
Using Telstra LaunchPad
It connects to Telstra, but with a time lag of 10-15 seconds, however:
Windows Messenger is unable to Sign In (error message)...
There is no Internet Access via Internet Explorer (Page not Found in IE 6)..
And no e-mail Send/Receive in Outlook (Pop Server Error Window)..
For the purpose of discussion, I have arbitrarily named this state the
Stagnation State. The Upper layers of the OSI Model appear to be denied
access to the Middle Layers, even though it appears that the Session Layer
is ok. This ALWAYS occurs after User Login & User Startup.
It can also occur spontaneously - up to 4 or 5 times per day, usually
signalled by the Outlook Error Message, since Outlook is usually left
running Minimised.
Try a repair:
MsgBox:
"The following steps of the repair operation failed:
Flushing the ARP cache."
..however, in terms of the OSI Model, all Layers seem to be working ok, so
the repair has worked.
To avoid the repair error issue, I have created a batch file REPAIR.BAT,
with a shortcut on the Desktop. This file essentially executes the commands:
arp -d
ipconfig /release
ipconfig /renew.
REPAIR is executed manually:
a.. immediately after User Startup, before using ISP connectivity
software.
(After REPAIR, LaunchPad connects in less than 2 seconds).
a.. each time Stagnation occurs spontaneously.
Using BPALogin
There is no substantial performance difference or advantage over LaunchPad.
Stagnation
Stagnation can therefore be defined as a Windows TCP/IP State in which:
TCP/IP tools, such as ping and ftp, can reach out over the Telstra WAN,
indicating that the Lower OSI Layers are operating as expected.
Both ISP connectivity programmes will connect and disconnect BUT with a 10
to 15 second lag.
Neither program seems "aware" of Stagnation, nor are Session Errors
generated.
No Application Level program, requiring transport services via the Session
Layer, will operate correctly - Outlook, Internet Explorer, Windows
Messenger nor any other.
Normal OSI Middle Layer Services can usually be restored by executing
REPAIR.BAT (without disconnecting).
This Windows State is ALWAYS attained after User Login/Startup. REPAIR is
always necessary, after which either ISP Connectivity programme will connect
in less than 2 seconds and the Network performs correctly.
This Windows State occurs spontaneously 4 to 5 times during a 7-8 hour
login, at intervals varying from a few minutes to over two hours
This Windows State is signalled by Application Errors.
Discussion
The IP address appears to be acquired early in the System Startup process,
and, by the time
User Startup is complete, some portion(s) of the TCP/IP Stack enter(s) a
so-called Stagnation State and require(s) "Repair".
This Windows Stagnation State also arises spontaneously 4 to 5 times each
day, regardless of the ISP connectivity software used.
The Operating Procedure is to execute REPAIR.BAT after User Startup is
complete, and then Run LaunchPad.
The Operating Procedure is to also execute REPAIR.BAT whenever Stagnation
occurs.
Recommended Microsoft Action
Identify and fix so-called Windows Stagnation State.
Fix Network Connection Repair error(s).
Recommended Telstra Action
Better detection of the so-called Stagnation State and, possibly, initiate
"repair" of Network Connection.
=============== End Original Attachment ===========================
attachment.
1 reply to Group, 4 responses by e-mail (all experiencing similar problems)
and a Deafening Silence from Microsoft!
The attachment is now included in full (below).
Pat Garard
Australia
=============== Begin Original Attachment =====================
Telstra (Australia) ISP Connectivity - TCP/IP Issues
I am comparing the behaviour of Telstra (Australia) LaunchPad under Windows
XP, with that under Windows 2000. In both cases the IP address is obtained
using Telstra DHCP and DNS.
For the purposes of comparison during testing, I have used the generic ISP
software called BPALogin.
There appear to be some issues with Windows XP TCP/IP.
Windows 2000
Telstra LaunchPad (Proprietary connectivity tool) could be set up to start
in "Startup" and auto-connect to Telstra consistently and without problems.
This was entirely transparent to the User.
Windows XP Professional - After upgrade
Telstra LaunchPad could be set up to start in "Startup" but auto-connect to
Telstra consistently failed.
It was necessary to remove LaunchPad from "Startup", and always to manually
start LaunchPad after User Startup was complete (little or no disk activity
after services had started). This usually worked ok, but the connection
would "drop out" 2 to 3 times per session of about 7 hours. LaunchPad would
show "Connected", and a Network Connection "Repair" would normally restore
service.
Windows XP Professional - After IIS and ActiveSync
There are two (2) Network connections: ISP via Cable Modem and 10Mbs-1
Ethernet Card, and ActiveSync via COM1 and Direct Cable (VPN).
Immediately after User Startup but before connection:
It could be seen (in a command window) that ping and ftp have access to DNS,
on the Telstra Network, and that ftp is capable of remote access on the
Telstra WAN - the lower layers of the OSI Model are working as expected.
Two ISP Connectivity Tools are available:
Telstra LaunchPad
BPALogin
(BUT NEITHER IS YET RUNNING).
Windows Messenger will not Sign In.
Using Telstra LaunchPad
It connects to Telstra, but with a time lag of 10-15 seconds, however:
Windows Messenger is unable to Sign In (error message)...
There is no Internet Access via Internet Explorer (Page not Found in IE 6)..
And no e-mail Send/Receive in Outlook (Pop Server Error Window)..
For the purpose of discussion, I have arbitrarily named this state the
Stagnation State. The Upper layers of the OSI Model appear to be denied
access to the Middle Layers, even though it appears that the Session Layer
is ok. This ALWAYS occurs after User Login & User Startup.
It can also occur spontaneously - up to 4 or 5 times per day, usually
signalled by the Outlook Error Message, since Outlook is usually left
running Minimised.
Try a repair:
MsgBox:
"The following steps of the repair operation failed:
Flushing the ARP cache."
..however, in terms of the OSI Model, all Layers seem to be working ok, so
the repair has worked.
To avoid the repair error issue, I have created a batch file REPAIR.BAT,
with a shortcut on the Desktop. This file essentially executes the commands:
arp -d
ipconfig /release
ipconfig /renew.
REPAIR is executed manually:
a.. immediately after User Startup, before using ISP connectivity
software.
(After REPAIR, LaunchPad connects in less than 2 seconds).
a.. each time Stagnation occurs spontaneously.
Using BPALogin
There is no substantial performance difference or advantage over LaunchPad.
Stagnation
Stagnation can therefore be defined as a Windows TCP/IP State in which:
TCP/IP tools, such as ping and ftp, can reach out over the Telstra WAN,
indicating that the Lower OSI Layers are operating as expected.
Both ISP connectivity programmes will connect and disconnect BUT with a 10
to 15 second lag.
Neither program seems "aware" of Stagnation, nor are Session Errors
generated.
No Application Level program, requiring transport services via the Session
Layer, will operate correctly - Outlook, Internet Explorer, Windows
Messenger nor any other.
Normal OSI Middle Layer Services can usually be restored by executing
REPAIR.BAT (without disconnecting).
This Windows State is ALWAYS attained after User Login/Startup. REPAIR is
always necessary, after which either ISP Connectivity programme will connect
in less than 2 seconds and the Network performs correctly.
This Windows State occurs spontaneously 4 to 5 times during a 7-8 hour
login, at intervals varying from a few minutes to over two hours
This Windows State is signalled by Application Errors.
Discussion
The IP address appears to be acquired early in the System Startup process,
and, by the time
User Startup is complete, some portion(s) of the TCP/IP Stack enter(s) a
so-called Stagnation State and require(s) "Repair".
This Windows Stagnation State also arises spontaneously 4 to 5 times each
day, regardless of the ISP connectivity software used.
The Operating Procedure is to execute REPAIR.BAT after User Startup is
complete, and then Run LaunchPad.
The Operating Procedure is to also execute REPAIR.BAT whenever Stagnation
occurs.
Recommended Microsoft Action
Identify and fix so-called Windows Stagnation State.
Fix Network Connection Repair error(s).
Recommended Telstra Action
Better detection of the so-called Stagnation State and, possibly, initiate
"repair" of Network Connection.
=============== End Original Attachment ===========================