RRAS Problem

[rclendenon]

I have recently switched from a Novell server to a Windows 2000 Small Business Server. Everything seems to be working okay until I start the Router and Remote Access Service. When I start the service three computers (all running Windows 98) can no longer log on to the server. The get the following error message:

"No domain server was available to validate your password. You may not be able to gain access to some network resources. "

However, they can see the network through Network Neighboorhood and I can map the network drives using Net Use at the Command Prompt. The other computers on the network (a mixture of WinXP,Win98 and Win95) all seem to work just fine. When I shutdown Router and Remote Access Service and restart the three computers affected the log on just fine. Does anybody have any suggestions?

Thanks in advance for your help,

 

[GlenJohnson]

Are the problem PC's using dhcp? Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"I grow old learning something new everyday".
Solon (640-558 BC); Greek legislator.

 

[rclendenon]

Yes they are using DHCP. I have tried using static IP addresses for these computers and have gotten the same problems.

 

[Takis]

If you use DHCP in clients, try to see if all of options in your scope are available that is (the most common are 003,006,015,044,046) for the clients and same for the server ...
If you have win98-95 clients be sure that DS client for windows 98 or 95 is installed from the server CD!
Do not make any special changes in properties netneighbourhood for clients except that they use DHCP!

And here is some other tip for the server & Internet Connection Sharing with RRAS!

Right click on RRAS in MMC (or look for Routing & Remote Access in Programs -> Administrative Tools), and choose 'enable Routing & Remote Access'
Select 'manual configuration' and click next until the setup has completed
After completion, right click on 'general' under the IP routing section, and choose 'New Routing Protocol'
Choose NAT from the list

Right click on 'Network Address Translation' under the IP routing section, and choose 'new interface'
All the interfaces, both logical & physical are listed here
First, select your public interface (=interface that has an public internet IP)

Set this interface to 'public interface connected to the internet' and check 'translate TCP/UDP headers'
Do the same for the internal interface, and set it's properties to 'private interface connected to private network'

Right click 'Network address translation (NAT)' and choose properties
Go to the address translation tab, and make sure the checkbox 'automatically assign IP addresses by using DHCP' is DISABLED
In the tab 'Name resolution', make sure everything is disabled as well.

Assuming that your server is running DNS :
Now go to the DNS snap-in in mmc, right-click on the local server name, and choose properties
Go to the forwarders tab, and enable forwarders
Fill in the address of the DNS server of your ISP, and click OK

Reboot your server

Client configuration : if your clients have a fixed IP, make sure the default GW is pointing to your RRAS server, and that the DNS server is pointing to the RRAS server as well (by using the forwarder, your RRAS server will be able to resolve all names, including internet addresses...)
If your clients are using DHCP, make sure the DHCP scope options are assigning the IP address of your RRAS server as default gateway, and that the IP address of the DNS server is pointing to your RRAS server as well...

Try to ping to 209.73.180.2
Try to do a tracert to 209.73.180.2
Try to ping to

http://www.altavista.com

If these 3 tests work, then you will be able to surf the internet.
(make sure your IE is not using a proxy server when it's not needed)

Good luck,