Question

Symptoms and Cause

Have you checked the type of your connection in the connection details? Some sites, even though the modem host is an NT4 server, have only a TCP/IP connection configured in the RAS control panel. If that is the case, that could be your problem right there. Even if the NetBIOS is enabled to go over TCP/IP, it won't work. You need to have the NetBEUI protocol enabled in the RAS settings for RCTP to be able to return the content back to your display.

For example, here is s a real life example of what you may expect to see in such case. Having only a TCP-IP connection, you connect, map a drive using the TCP/IP address (and you can do this because NetBIOS is enabled over TCP/IP). You then try RCTP as follows:

	C:>rctp \\xx.xx.xx.xx -comm z
	comm done
	

	C:>rctp \\xx.xx.xx.xx -status
	
	 Current state of the server "Remote CTP Service":
	 Comm: 3
	 Baud: 9600
	 Logfile: none
	 MaxLogSize: 102400
	 MaxBackupLogs: 3
	 status done.
	

All right! This is cool too. And how about doing some real work, like this:

	C:>rctp \\xx.xx.xx.xx
	>>_
	

And that's all you get at this point. It never returns any content and if you ask the client to check the device using HyperTerminal everything works like a charm so you know the Diag port and cable are OK. This is when you realize how badly you NEED a NetBEUI connection in order to use RCTP.

Solution

To correct this, have the customer open up the control panel and double-click the Network control panel icon. When it opens, click on the services tab, scroll down to Remote Access Service, highlight it and click on the properties button. When the RAS configuration applet comes up click on the Network button on the right and see if NetBEUI is selected. If it is not, select it, and then click on Configure button to the right (making sure that Entire Network is selected). OK out of all of that and reboot the server.

If, after all of this is done, you still cannot get a NetBEUI protocol to work over RAS (it happens sometimes in NT4, especially on Alpha machines for some weird binding reasons) feel free to give up and try dialing into another machine. The alternative is essentially reloading WinNT.

Technical Contact(s)

Sinisa Nojkovic

Submitted by

Daniel Ortegon

Date Submitted

18 Mar 2002