Answer:

You could be having problems connecting to your Internet Service Provider (ISP) or connecting to servers on the Internet. Both of these topics a cover below.

These tips may help you connect to your Internet Service Provider.

Back To Menu

If you can connect to your ISP, but have trouble connecting to servers on the Internet using a web browser, ftp, or telnet, the following suggestions may help.

Back To Menu

Problems with TCP/IP Configuration

Verify that the IP address assigned to you by your ISP for this connection is not the same as the IP address for your network card or loopback driver (if installed). Also, the IP address of your network card or loopback driver should not be on the same network as the IP address assigned to you by your ISP for this connection.

For additional information, please see the following article in the Microsoft Knowledge Base:

NTBackup.exe from WinNT 3.51 SP5 Causes Verify Errors

The information in this article applies to:

SYMPTOMS

After installing Service Pack 5 on Windows NT 3.51, you may start to see verify errors in NTBackup. The errors you see, in either your NTbackup screen or Backup.log, will have the following format:

*File information found on tape:
*%FileName% %Size% %Date% %Time%
*File information found on disk:
*%FileName% %Size% %Date% %Time%
*Difference encountered in alternate file data.
*The file %FileName% is different.

The problem seems to occur more frequently on Macintosh or large NTFS volumes.

CAUSE

This is caused by NTBackup checking the stream size of the data which may change every time you run backup.

RESOLUTION

This problem seems to be more of a nuisance than actual file problems, but can cause NTBackup to degrade in performance, especially on large volumes. So far, we have not seen any cases which actually showed file corruption. You can simply choose not to verify after backup or apply the Hotfix available as mentioned below.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

NTBackup.exe from WinNT 3.51 SP5 Causes Verify Errors

Back To Menu

RAS error 629.

Error 629 is usually the result of a mismatch in what the ISP requires and how the Dial-Up Networking (DUN) entry is configured. Try the following steps one at a time. Most of these steps steps are performed in the phone book properties.

1.Change the authentication to Clear Text under Security.
2.Lower the connection speed under Modem Configuration.
3.Disable hardware flow control under Modem Configuration.
4.Disable modem error control under Modem Configuration.
5.Disable modem compression under Modem Configuration.
6.Disable software compression under Server.
7.Disable PPP LCP extensions.
8.Disable IP header compression.
9.Check DNS configuration.
10.Check the user name and password syntax (mixed case, "ppp" extension needed, and so on.) You may need to contact your ISP for assistance.
11.Connect using a Terminal window�if you get connected then there is a possible problem with CHAP or PAP. (This determines the user name and password. Set at the remote host site.)
You may need to call your ISP for additional support.
12.Check to see if your modem is supported. (Please see the HCL.)
13.Contact the modem's manufacturer for updated modem files.
14.Try another supported modem.
15.Have the phone company check the phone lines.
16.If you are not prompted for a user name or password and you get the error message, then choose UnSave Password on the Security tab in the phone book. Try to reconnect.
You should be prompted for a user name and password.
17.If running a script, disable it and try to connect with a Terminal window. If you are able to connect then there is a problem with the script file.

Back To Menu

Troubleshooting RAS Client Issues in Windows NT 4.0

The information in this article applies to:
�Microsoft Windows NT Server version 4.0 �Microsoft Windows NT Workstation version 4.0

SUMMARY

This article contains steps to help you troubleshoot issues with the Remote Access Service (RAS) in Windows NT 4.0. This article focuses on issues that can occur when you use RAS to dial into another computer or an Internet service provider (ISP).

The issues discussed in this article include:

MORE INFORMATION

Cannot Dial with RAS

When you attempt to dial with Dial-Up Networking, the following error message may appear:

Error 692: Hardware failure in port or attached device.

If you have upgraded from Windows NT 3.51 and you are running a program that monitors the phone line (for example, a fax program), you may receive an error message that indicates the port is busy when you try to dial out with Dial-Up Networking.

Error 633: The port is already in use or is not configured for RemoteAccess dial out.

If you installed RAS in Windows NT 3.51 before upgrading to Windows NT 4.0, the kernel-mode telephony driver that is used in Windows NT 3.51 is retained and RAS uses non-Unimodem drivers. If another program uses the Unimodem driver and is set answer the line automatically, that program causes TAPI 2.0 to control the communications port. When this occurs, the communications port is not available to the non-Unimodem version of RAS.

To resolve this problem, remove the non-Unimodem driver and replace it with one supplied with Windows NT 4.0. To do so, follow theses steps:
1.In Control Panel, double-click Network. 2.Click the Services tab. 3.Click Remote Access Service, and then click Properties. 4.If the type of modem listed indicates that the kernel-mode TAPI driver is still being used [that is, it lists the type as "Modem (modem.inf)"], click the port, and then click Remove. 5.Click Add to add the Unimodem driver (the driver supplied with Windows NT 4.0) for this COM port. 6.Click Continue and restart your computer when prompted to do so.

Back To Menu

Cannot Connect After Dialing with RAS

If the telephone line is unusually noisy, you may receive an error message such as:

Error 640: A Netbios error has occurred.
This message indicates that the modem may not be able to negotiate a connection at a higher speed. Try setting the modem speed on the client computer down to a lower speed such as 9600 bps. To do so, follow these steps:
1.In Dial-Up Networking, click the appropriate phone book entry.
2.Click More, and then click Edit Entry And Modem Properties
. 3.Click the appropriate modem, and then click Configure.
4.In the Initial Speed box, click 9600.

As an additional troubleshooting step, you can clear the Enable Modem Compression check box. 5.Click OK, and then click OK.

You may also need to disable software compression for this connection. To do so, use the following steps:>BR> 1.In Dial-Up Networking, click the appropriate phone book entry.
2.Click More, and then click Edit Entry And Modem Properties.
3.Click the Server tab.
4.Click the Enable Software Compression check box to clear it.
5.Click OK.

If the remote network does not answer or cannot connect, it is a good idea to test the connection from another computer. The problem may lie with the RAS server and not with the client.

Back To Menu

Enabling AutoDial with Internet Explorer in Windows NT 4.0

The information in this article applies to:
�Microsoft Windows NT Server version 4.0 �Microsoft Windows NT Workstation version 4.0

SUMMARY

You can use the AutoDial feature in Windows NT 4.0 to automatically prompt you to dial a phonebook entry when you try to connect to a network or Internet path that is not available or cannot be found. For example, when you double-click the Internet Explorer icon, Microsoft Internet Explorer attempts to load your start page. If you are not connected to your Internet service provider (ISP), you receive the following error message:

cannot open the Internet site http://.
The site was not found. Make sure the address is correct, and try again.

With AutoDial correctly configured, you are prompted to dial your ISP.

Back To Menu

MORE INFORMATION

To configure AutoDial, follow all of the steps in each of the following sections.

Enable AutoDial By Location
1.Double-click My Computer and then double-click Dial-Up Networking.
2.In the Phonebook Entry To Dial box, click the entry for your ISP.
3.Click More, click User Preferences, and then verify that the location from which you are dialing is selected. Click OK.

Remote Access Services Must Be Started

1.In Control Panel, double-click Services.
2.Locate the following two services and verify that they are started: - Remote Access AutoDial Manager
- Remote Access Connection Manager

Manually Set Your Start Page

1.Using Dial-Up Networking, connect to your ISP.

2.Start Internet Explorer and then connect to the Web page you want to use as your start page.

3.On the View menu, click Options.
4.Click the Navigation tab.
5.In the Page box, click Start Page, and then click Use Current.
6.Click OK.

The next time you start Internet Explorer without being connected to your ISP, you will be prompted to dial the connection.

Back To Menu

Troubleshooting Autodial

The information in this article applies to:
�Microsoft Windows NT Workstation version 4.0 �Microsoft Windows NT Server version 4.0

SUMMARY

The Autodial component of Windows NT 4.0 contains a tracing utility and a character mode program that can be used to diagnose problems with autodial and related network components.

MORE INFORMATION

Viewing and Deleting information in Autodial

To view the list of addresses and names that Autodial has a record of, run a command window and type:

RASAUTOU -S

To delete an address or name entry from the list, start the Registry Editor (REGEDT32.EXE) and go to the following subkey:

HKEY_CURRENT_USER/Software/Microsoft/RAS Autodial/Addresses

You can delete any TCP/IP addresses that you see under this key. Note that Autodial can use IP addresses, DNS fully qualified domain names (FQDN), and NetBIOS names.

Troubleshooting Autodial

Another helpful troubleshooting tool is the Rasauto tracing log. When activated, this feature will write to a log all events that occur within Autodial. This logfile will aid Microsoft support engineers in debugging the problem.

The following steps will enable Rasauto tracing:
1.Copy the file rtutils.dll to the %systemroot%/system32 directory on your hard disk.

After copying rtutils.dll to the system32 directory, you have to start and stop rasphone to create the Tracing registry keys.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. 2.Start the registry editor (Regedt32) and locate the following Registry subkey:

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services /Tracing/RASAUTO/EnableFileTracing

3.Double-click this value and change the string from 0 to 1. The default value is 0. 4.Exit REGEDT32. 5.Stop all Remote Access Service processes. if you are unclear as to what RAS services are running, check Control Panel, Services. 6.Wait a moment, and restart any necessary services. be sure that you enable Rasauto.

Unless you change the FileDirectory value in the same area in the registry, the log will be in the %windir%/tracing directory with a file name of Rasauto.log.

Back To Menu

Drivers, Patches, & Sample Files

http://www.microsoft.com/ntserversupport/default-sl.htm

For a listing of all service packs, go to this address:
http://www.microsoft.com/isapi/support/ps_sl.idc?purl=/ntserver/&pfx=nts&base=ntserversupport&kbd=winnt&sl=q_servpk

Service Packs
Contains single-file downloads for the DEC Alpha, Intel, MIPS, and PowerPC builds of the latest service packs for Windows NT 3.51 and 4.0. Contains disk images for the Intel build of the latest service packs for Windows NT 3.1 and 3.5. For DEC Alpha, MIPS, and PowerPC builds for Windows NT 3.1 and 3.5, or for single-file download versions, look on our FTP server at

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/

Back To Menu

DIFFICULTY GETTING MAIL ON PROXY SERVER

From our tech friend, Janet Prejan, the following information was made available:

"If the customer is on a Network and they are trying to get mail, the first thing to ask is if they are on a proxy server. If they are, they will never, ever, ever get mail unless they disconnect from there server, and turn the computer off, and then back on and dial up. But this isn't recommended, because we do not support it!

The reason: Proxy servers make a cached copy of a web page and bring it to the person. They never really ever get out into the internet. The mail server must have customers login. They cannot get a cached copy of mail. The news server will work on a proxy server, but mail will not. Almost all of the areas of GTE, other than us, will have proxy servers. So, if you get a GTE person, and they are at work, 99% says it is a proxy.

Back To Menu

WINDOWS NT 4.0 SERVICE PACK 2

AND from easymoney:

Windows NT 4.0 Service Pack 2 breaks PPP in ascend modems.

Symptoms are:
Userid/password will negotiate okay
System registers you on the network o.k.
Connection extablished
You are then unable to ping anything using DNS
All requests timeout
After about 20 seconds you will be disconnected.

Fixes Are:
Delete Service Pack 2
Call Microsoft and have them Edit "New Value #1 in the registry to read "DisableMultiLink" Don't try this at home!! Meaning, dont go there! Let MS do it!!!!!!

More On Service Pack 2

Problem--------- NT 4.0 Service Pack 2.

For those who are not aware: If a customer is having problems connecting, or with NO DNS or Bad IP in NT 4.0, ask them if they have installed SP 2. If they have, there is a good chance this is the problem. This is a known issue acknowledged by Microsoft. They have released a fix available on their website. There is a known bug in Service Pack 2 that causes problems in the authentication phase of a PPP connection. It can also cause "NO DNS" and "bad"connections if you do actually make a connection. Microsoft has released an active fix for this. It is available at microsoft.com. Also, below I have included the registry fix for this issue. We do not recommend editing your system registry unless you feel comfortable in doing so.

After installing Service Pack 2 for Windows NT 4.0, you may receive the following error message when you attempt to connect to Internet addresses using MSN, The Microsoft Network, or other Internet service providers:
Bad IP Address:...... CAUSE
By default, the components of Service Pack 2 automatically attempt to negotiate LCP extensions. The Enable PPP LCP Extensions option in Dial-Up Networking no longer has any effect.

RESOLUTION......
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

To resolve this issue, use Registry Editor (Regedt32.exe) to add the following values :
Value name: DisableMultilink
Data type: REG_DWORD
Value: 1
to the following registry key:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RasMan/PPP
NOTE: Adding this registry entry may affect other Windows NT communications functionality.
STATUS
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
For additional information, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q154917
TITLE : Cannot Access Internet with Dial-Up Networking and MSN Account
ARTICLE-ID: Q135530
TITLE : Using Windows NT to Access The Microsoft Network

Back To Menu

Solution:         When the screen comes up with the username, password, domain, they may have something in domain. This particular customer, today, had gte.net. I had her take it out and she got connected.

Thanks to Floyd Bunch

Back To Menu