Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
NT 4.0 to Win2k Pro RAS problem
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Graeme Byrne  
View profile  
 More options Jul 11 2001, 2:30 am
Newsgroups: microsoft.public.win2000.ras_routing
From: "Graeme Byrne" <g.by...@bendigo.latrobe.edu.au>
Date: Tue, 10 Jul 2001 23:28:38 -0700
Local: Wed, Jul 11 2001 2:28 am
Subject: NT 4.0 to Win2k Pro RAS problem
I have set up an incoming connection item on my Win2k box
at work. Its TCP/IP properties are

Allow callers to access my local area network - Yes
Specify TCP/IP Addresses (range specified)
Allow calling computer to specify its own IP address - Yes

My home machine is running NT 4.0 (SP 6a) is set up to
dial in specifying its own IP.

I get connected can ping some machines on the work
intranet (unix boxes) but cannot ping any windows machines
on the intranet or extrenal addresses. Also browsing the
internet is a problem.

When the work machine was NT4 everything worked fine.

The only clue as to the problem is the following Event
message.

Event Type:     Warning
Event Source:   RemoteAccess
Event Category: None
Event ID:       20187
Date:           7/11/2001
Time:           10:19:18 AM
User:           N/A
Computer:       BYRNE
Description:
The user  \g.byrne failed an authentication attempt due to
the following reason: The current configuration only
supports local user accounts.  

Any help appreciated.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John Spradlin  
View profile  
 More options Jul 11 2001, 7:44 am
Newsgroups: microsoft.public.win2000.ras_routing
From: "John Spradlin" <johnsprad...@hotmail.com>
Date: Wed, 11 Jul 2001 07:42:18 -0400
Local: Wed, Jul 11 2001 7:42 am
Subject: Re: NT 4.0 to Win2k Pro RAS problem
IS the RAS server a domain controller, member server or a standalone?
"Graeme Byrne" <g.by...@bendigo.latrobe.edu.au> wrote in message

news:48a601c109d2$b8a09b80$19ef2ecf@tkmsftngxa01...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Graeme Byrne  
View profile  
 More options Jul 11 2001, 8:10 pm
Newsgroups: microsoft.public.win2000.ras_routing
From: "Graeme Byrne" <g.by...@bendigo.latrobe.edu.au>
Date: Wed, 11 Jul 2001 17:06:50 -0700
Local: Wed, Jul 11 2001 8:06 pm
Subject: Re: NT 4.0 to Win2k Pro RAS problem
The RAS server is a standalone.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Discussion subject changed to "(Now Solved) NT 4.0 to Win2k Pro RAS problem" by Graeme Byrne
Graeme Byrne  
View profile  
 More options Jul 12 2001, 7:03 am
Newsgroups: microsoft.public.win2000.ras_routing
From: "Graeme Byrne" <g.by...@bendigo.latrobe.edu.au>
Date: Thu, 12 Jul 2001 03:59:30 -0700
Local: Thurs, Jul 12 2001 6:59 am
Subject: Re: (Now Solved) NT 4.0 to Win2k Pro RAS problem
The problem is now solved. My home machine used to be my
work machine and the NIC was still physically present and
setup. Uninsatlling the NIC on the NT 4.0 home machine
solved the problem. I had changed the NIC IP on the home
machine to one that the RAS server allocates. This must
have been sending conflicting info to the network causing
the problems.

Thanks


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »