June 1997 Notes:
Note 06/25/97: I recommend using the IBM dialer with IBM.net instead of the Win 95 TCP/IP dialer alone, which the IBM dialer works with, because on my system the Network seems to freeze after a period of time which it does not do if one uses the IBM dialer. Of course the IBM dialer uses more system resources.
Note 06/25/97: I recommend using the IBM dialer with IBM.net instead of the Win 95 TCP/IP dialer alone, which the IBM dialer works with, because on my system the Network seems to freeze after a period of time which it does not do if one uses the IBM dialer. Of course the IBM dialer uses more systems resources.
Note 6/25/97: NYNEX made a service call yesterday and said my telephone lines in my apartment were fine. They did redirect my service to a different connection box, which seems to have improved service. No problems so far this morning. They said they would discontinue the early morning line tests.
Note 6/21/97: On following message, NYNEX advises me they perform a line test in the early AM every day. When I am online I will be disconnected. When I reconnect and they reperform the line test again until succesfully completed, I will be disconnected again, thus setting up a redundant anoyance until the line test successfully completes. That is NYNEX's explanation for the problem listed below.
6/20/97 Internet Access in Greenwich, Connecticut from Byram, Connecticut Via NYNEX telephone exchange in Greenwich to Stamford, Connecticut SNET exchange or NYNEX telephone exchange in White Plains, New York or Armonk, New York has system problems possibly due to heavy usage, or internal industrial espionage. I have experienced continual cut offs in the morning hours from after midnight to 7 AM for the last six months. They are caused by irregular line noise possibly caused by internal telephone system failures or industrial espionage. Since I am not a telephone technician it is all theory. However, repeated disconnects during the morning hours when the system is not heavily used lead me to believe it is more than telephone system failure. Nothing in Scott's directory is classified or secret, so I advise anyone transmitting sensitive information over the Greenwich, Connecticut telephone system to possibly consult with their internal security to see if it is system malfunctions or industrial espionage, or possibly teenage hackers who are too smart for their own good. Believe it or not the the busiest category at Scott's site has become "Hacks and Cracks" up to 300 hits a day, so possibly some young hackers have figured out how to hack into our systems and disrupt normal use of the internet. It is all theory, but I have no proof other than irregular audible telephone line noise that the IBM.NET technician also heard and NYNEX claims does not exist. Thus either somone has the capability of tapping into my system telephone "bugging" at various intervals or there is a gopher gnawing at the telephone line. Who Knows ? However, if it happens to a simple home user like myself, I suspect that more serious corporate users might have certain security considerations that they might want to consider.
Note 06/06/97: I have had internet access connection access problems since Christmas Time. The sympthoms were that the connection would freeze up or disconnect. I was able to fix the problem by selecting "Control Panel", "Networking". Under "Networking" I removed "Client for Microsoft Networks", "Dialer", and "TCP/IP". I then rebooted and selected "Control Panel" , "Networking"; and reinstalled "Client for Microsoft Networks", "Dialer", and "TCP/IP". When prompted to insert Win95 disks, I installed the files again, however I "did not keep the newer files", but overwrote the newer files with the original files from the Win95 disks. The newer files that I overwrote with the original files were:
mapi32.dll
rpcltcl.dll
secur32.dll
winsock.dll
ndis.vxd
vredir.vxd
vdhcp.386
vip.386
vnbt.386
vtcp.386
vtdi.386
Those eleven files were replaced with the original files from the Win95 installation disks, by selecting "NO" when prompted to keep newer files. The networking problem that this fixed for me might have possibly been caused in December when I happen to log onto the "Chaos Computer Club" in Germany. However, I also had installed the MS "winsock.dll" update, MS "TCP/IP Dialer" update, plus numerous other betas and updates. The system is back running fine, so if you are having internet access speed slowdowns or disconnects, you might think that it might be possibly the networking system that is corrupted by one of the various previous mentioned files.
Note 06/05/97: If You Have Problems Connecting To Your ISP, Particulary IBM.NET; IBM Suggests Deleting Your Network Components From Windows 95 Network Window and Reinstalling Them, It Seems To Work for Me.
Note 06/01/97: My internet access worked poorly recently because I had the TCP setting in Networking set to "Windows Logon" instead of "Network Logon". I suggest looking at the link below if you use IBM.NET.