Pat Garard
December 5th 03, 12:32 PM
I am comparing the behaviour of Telstra (Australia) LaunchPad (ISP
connectivity software) 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 also used the generic
ISP software called BPALogin.
There appear to be some issues with Windows XP TCP/IP.
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 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.
Full details are discussed in the attachment (3 Pages), and any information
would be gratefully received.
Pat Garard
Australia
connectivity software) 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 also used the generic
ISP software called BPALogin.
There appear to be some issues with Windows XP TCP/IP.
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 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.
Full details are discussed in the attachment (3 Pages), and any information
would be gratefully received.
Pat Garard
Australia