Re: RDP can not logon error
- From: Caryn Condon <CarynCondon@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 24 Apr 2009 12:30:06 -0700
Hi,
Yes, ping and tracert to the dc in that remote site (where this system
resides) work just fine. I also did tracert and pings to DC's at the home
site and they worked just fine too.
****
Tracert & Ping to dc on the same subnet as the server that is having trouble.
C:\>tracert adbcp
Tracing route to adbcp.mynet.net [192.168.77.70]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.77.70
Trace complete.
C:\>ping adbcp
Pinging adbcp.mynet.net [192.168.77.70] with 32 bytes of data:
Reply from 192.168.77.70: bytes=32 time<1ms TTL=128
Reply from 192.168.77.70: bytes=32 time<1ms TTL=128
Reply from 192.168.77.70: bytes=32 time<1ms TTL=128
Reply from 192.168.77.70: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.77.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
****
Tracert & Ping to DC at home site (home site & remote site connected via vpn)
C:\>tracert ad2
Tracing route to ad2.mynet.net [192.168.1.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.77.1
2 432 ms 41 ms 58 ms mynet.net [X.X.X.X]
3 50 ms 46 ms 47 ms AD2 [192.168.1.8]
Trace complete.
C:\>ping ad2
Pinging ad2.mynet.net [192.168.1.8] with 32 bytes of data:
Reply from 192.168.1.8: bytes=32 time=41ms TTL=126
Reply from 192.168.1.8: bytes=32 time=43ms TTL=126
Reply from 192.168.1.8: bytes=32 time=45ms TTL=126
Reply from 192.168.1.8: bytes=32 time=43ms TTL=126
Ping statistics for 192.168.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 45ms, Average = 43ms
****
"C C" wrote:
Okay, on your original post, you mentioned the if you log in as the local.
administrator, you are successfully logged in. Now, when logged in as the
local administrator, try to do a ping or tracert to the DC's. Does it
ping/trace successfully?
"Caryn Condon" <CarynCondon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3C73440E-08FA-4A06-8715-B3407024AAF7@xxxxxxxxxxxxxxxx
Hello,
I confirmed that the domain admins is in the local administrator group. I
also tried adding that group the the RDP-TCP properties and that didn't
work
either. We want to use RDP and not TS.
Additional notes: We are using AD Integrated DNS on 192.168.1.8,
192.168.1.7
(AD2 & AD1 are in our home site) and 192.168.77.70 (ADBCP - in our remote
site). DNS replication appears to be running fine. Any manual entries we
add
have been replicated to all the DNS servers without error)
Here is the ipconfig from ADBCP and AD1:
***
Windows IP Configuration
Host Name . . . . . . . . . . . . : adbcp
Primary Dns Suffix . . . . . . . : mynet.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mynet.net
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : mynet.net
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
#2
Physical Address. . . . . . . . . : 00-0D-56-FD-BA-29
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.77.70
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.77.1
DNS Servers . . . . . . . . . . . : 192.168.77.70
192.168.1.8
192.168.1.7
Primary WINS Server . . . . . . . : 192.168.1.84
NetBIOS over Tcpip. . . . . . . . : Disabled
***
Windows IP Configuration
Host Name . . . . . . . . . . . . : ad1
Primary Dns Suffix . . . . . . . : mynet.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mynet.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mynet.net
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS VBD Client)
Physical Address. . . . . . . . . : 00-1D-09-6D-A1-46
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.8
Primary WINS Server . . . . . . . : 192.168.1.84
"C C" wrote:
Make sure that the domain admins group is added to the Permissions tab in
the RDP-TCP properties of the Terminal Services Configuration. In the
W2K3
server, go to Terminal Services Configuration in the Administrative
Tools,
Click on Connections, then right click on RDP-Tcp and click on
Properties.
Go to the Permissions tab. Do the rest.
OR you can add the Domain Admins group to the Administrators group of
your
W2K3, that is assuming that the local Administrators group is in the
Permissions tab of the TS Configuration.
Good luck.
"Caryn Condon" <CarynCondon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3A738CD1-E512-4AB0-993E-210AA9DF76CB@xxxxxxxxxxxxxxxx
Hi folks, trying this post in this dicussion per suggestion from
another
.....
I'm trying to connect to a remote server (Win2k3) using RDP and receive
the
following error:
"The system cannot log you on due to the following error: The network
address in invalid. Please try again or consult your system
administrator."
This error occurs when I attempt to login as a domain admin, a domain
user
(who does have login rights) but not when I login as the local
administrator.
I also have used VNC to login as the domain admin and that worked just
fine.
So I suspect there is something amiss with RDP permissions?
Here is some additional information, I verified that the DC for that
site
has no errors in the dcdiag and dcdiag /dnsbasic or fmso query.
Replication
from the home office site to this site appears to be running ok. We are
connected via a static vpn connection.
We just upgraded our NT4 domain to Win2k3 last Saturday (4/18) and so
far
all else appears to be ok.
This error occurs on several Win2k3 servers but there are others that
this
does not occur on.
One strange piece of information is posted below. I ran the dcdiag for
that
sites dc (adbcp) from the system having the problem and it noted errors
(see
below):
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Chicago\ADBCP
Starting test: Connectivity
......................... ADBCP passed test Connectivity
Doing primary tests
Testing server: Chicago\ADBCP
Starting test: Replications
......................... ADBCP passed test Replications
Starting test: NCSecDesc
......................... ADBCP passed test NCSecDesc
Starting test: NetLogons
[ADBCP] An net use or LsaPolicy operation failed with error 1203,
No network provider accepted the given network path..
......................... ADBCP failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (ADBCP) call failed, error 1722
The Locator could not find the server.
......................... ADBCP failed test Advertising
Starting test: KnowsOfRoleHolders
......................... ADBCP passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ADBCP passed test RidManager
Starting test: MachineAccount
Could not open pipe with [ADBCP]:failed with 1203: No network
provider accepted the given network path.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... ADBCP failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [ADBCP]:failed with 1203: No network
provider accepted the given network path.
......................... ADBCP failed test Services
Starting test: ObjectsReplicated
......................... ADBCP passed test ObjectsReplicated
Starting test: frssysvol
[ADBCP] An net use or LsaPolicy operation failed with error 1203,
No network provider accepted the given network path..
......................... ADBCP failed test frssysvol
Starting test: frsevent
......................... ADBCP failed test frsevent
Starting test: kccevent
Failed to enumerate event log records, error No network provider
accepted the given network path.
......................... ADBCP failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error No network provider
accepted the given network path.
......................... ADBCP failed test systemlog
Starting test: VerifyReferences
......................... ADBCP passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : mynet
Starting test: CrossRefValidation
......................... mynet passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... mynet passed test
CheckSDRefDom
Running enterprise tests on : mynet.net
Starting test: Intersite
......................... mynet.net passed test
Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1722
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1722
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1722
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1722
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1722
A KDC could not be located - All the KDCs are down.
......................... mynet.net failed test
FsmoCheck
More details:
I ran another dcdiag between the system with the problem (messengerbcp)
and
- Follow-Ups:
- Re: RDP can not logon error
- From: C C
- Re: RDP can not logon error
- References:
- RDP can not logon error
- From: Caryn Condon
- Re: RDP can not logon error
- From: C C
- Re: RDP can not logon error
- From: Caryn Condon
- Re: RDP can not logon error
- From: C C
- RDP can not logon error
- Prev by Date: SPAM
- Next by Date: File Transfer Manager will not download Server 2008 VHD image
- Previous by thread: Re: RDP can not logon error
- Next by thread: Re: RDP can not logon error
- Index(es):
Relevant Pages
|
