Update: RDO/Win95 Performance Problem
| Author |
Message |
|
Bradley Pee
#1 / 10
|
 Update: RDO/Win95 Performance Problem For those of you who may be experiencing a similar problem (VB4/RDO on
Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 &
NT - using latest MSSQL ODBC drivers in all cases):
Over the last weekend, our LAN administrator rearranged the ethernet
cabling between our file servers and the RDO/Win95 problem has disappeared.
It appears there was a problem with packets being routed properly to the
SQL Server box. I'm still not quite sure why Windows NT Workstation ran
VB4/RDO without a hitch when Windows 95 had problems.
The important thing to realize is that the problem is almost definitely
external to your Win95/RDO client machine and external to your SQL Server
box. It may be best described as a networking glitch or anomaly. I'd
suggest isolating your SQL Server. Put it on the same network segment as
your Win95 client and see what happens.
Good luck.
--------------------------------------------------------
http://www.*-*-*.com/
MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
http://www.*-*-*.com/ * (708)954-2900
--------------------------------------------------------
|
| Sat, 06 Feb 1999 03:00:00 GMT |
|
 |
|
Bradley Pee
#2 / 10
|
Update: RDO/Win95 Performance Problem For those of you who may be experiencing a similar problem (VB4/RDO on
Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 &
NT - using latest MSSQL ODBC drivers in all cases):
Over the last weekend, our LAN administrator rearranged the ethernet
cabling between our file servers and the RDO/Win95 problem has disappeared.
It appears there was a problem with packets being routed properly to the
SQL Server box. I'm still not quite sure why Windows NT Workstation ran
VB4/RDO without a hitch when Windows 95 had problems.
The important thing to realize is that the problem is almost definitely
external to your Win95/RDO client machine and external to your SQL Server
box. It may be best described as a networking glitch or anomaly. I'd
suggest isolating your SQL Server. Put it on the same network segment as
your Win95 client and see what happens.
Good luck.
--------------------------------------------------------
http://www.cl.ais.net/bpeet
MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
http://www.healthnetwk.com * (708)954-2900
--------------------------------------------------------
|
| Sat, 06 Feb 1999 03:00:00 GMT |
|
|
|
Bradley Pee
#3 / 10
|
Update: RDO/Win95 Performance Problem For those of you who may be experiencing a similar problem (VB4/RDO on
Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 &
NT - using latest MSSQL ODBC drivers in all cases):
Over the last weekend, our LAN administrator rearranged the ethernet
cabling between our file servers and the RDO/Win95 problem has disappeared.
It appears there was a problem with packets being routed properly to the
SQL Server box. I'm still not quite sure why Windows NT Workstation ran
VB4/RDO without a hitch when Windows 95 had problems.
The important thing to realize is that the problem is almost definitely
external to your Win95/RDO client machine and external to your SQL Server
box. It may be best described as a networking glitch or anomaly. I'd
suggest isolating your SQL Server. Put it on the same network segment as
your Win95 client and see what happens.
Good luck.
--------------------------------------------------------
http://www.cl.ais.net/bpeet
MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
http://www.healthnetwk.com * (708)954-2900
--------------------------------------------------------
|
| Sat, 06 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#4 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#5 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#6 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#7 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#8 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#9 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
|
|
Marc C. Brook
#10 / 10
|
Update: RDO/Win95 Performance Problem This is caused by routing problems of the NetBEUI protocol when the Named
Pipes network library. If you can't fix the problems be eliminating
routers (as I could not), then you should switch to NWLink as the network
library as selected in the SQL Client Configuration Utility.
Marc
Quote: > For those of you who may be experiencing a similar problem (VB4/RDO on > Win95 is *slow*, VB4/RDO on NT Workstation is fast, VB4/DAO is fast on 95 & > NT - using latest MSSQL ODBC drivers in all cases): > Over the last weekend, our LAN administrator rearranged the ethernet
> cabling between our file servers and the RDO/Win95 problem has
disappeared.
> It appears there was a problem with packets being routed properly to the
> SQL Server box. I'm still not quite sure why Windows NT Workstation ran
> VB4/RDO without a hitch when Windows 95 had problems.
> The important thing to realize is that the problem is almost definitely
> external to your Win95/RDO client machine and external to your SQL Server
> box. It may be best described as a networking glitch or anomaly. I'd
> suggest isolating your SQL Server. Put it on the same network segment as
> your Win95 client and see what happens.
> Good luck.
> --------------------------------------------------------
> http://www.cl.ais.net/bpeet
> MIS Project Leader * HealthNetwork, Inc., Oak Brook, IL
> http://www.healthnetwk.com * (708)954-2900
> --------------------------------------------------------
|
| Sun, 07 Feb 1999 03:00:00 GMT |
|
| |
|
