Authentication problems of member server on DC Win 2003

I have a member terminal server Win 2008R2 with authentication problems  on DC Win 2003.

The server is joined to the network properly but when I try to access any resources (from the member server) on the DC server it does not work.

For example when I run \\DCserver I get Windows cannot access \\DCserver error
Mapping network drives does not work either

Any ideas for me?
LVL 1
GerhardpetAsked:
Who is Participating?
 
Reinert WentzelConnect With a Mentor Managing MemberCommented:
just check something for me on the tserver. go to network connections, advanced, advanced settings. under adapters and bindings, under connections, see that the local nic is first in the binding order. also run nslookup server2 from the tserver and give me the feedback
0
 
Shabarinath RamadasanInfrastructure ArchitectCommented:
Is this issue only with DCs?
Ping works?
Windows firewall status?

Good luck
Shaba
0
 
jerrypdCommented:
who are you logging in as on the TS box? you need to log into the domain (domainname\username) or else you are logging in "locally" on the TS box
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
GerhardpetAuthor Commented:
Yes ping works and firewall is ok

All the other workstation communicate will with the DC
0
 
EichhornHCommented:
can you ping full qualified domain name ?
dns entry on memberserver ok ?
dns server running ?
0
 
antonyleirasCommented:
Man,

Basically this can be a problem of synchronization time that gives  us strange messages when trying to access any kind of server via UNC name. So the first situation would be you verify the time into both servers and see if they are equal.

If yes, please tell me.

If not I need to know

1. How many DCs do  you have in your network?

Thanks,

Antony
0
 
Darius GhassemCommented:
Make sure your TS server is putting to the DC for DNS in it's TCP\IP properties. Make sure the DC is pointing to itself for DNS in it's TCP\IP settings
0
 
GerhardpetAuthor Commented:
can you ping full qualified domain name ? YES
dns entry on memberserver ok ? YES
dns server running ? YES

Time is equal on both servers
One DC in the network
0
 
Darius GhassemCommented:
When you go to Run then type \\IPaddress what error do you get?
0
 
GerhardpetAuthor Commented:
DNS in TCP\IP properties is properly setup on both servers

I can access
- a workstation from the TS Server
- from a workstation to the TS server
- from DC server to TS Server
- BUT NOT from the TS Server to the DC Server
0
 
GerhardpetAuthor Commented:
dariusg,
Wola....When I use the DC IP address from the TS Server then it works

Why is that?
0
 
Darius GhassemCommented:
Has to be a DNS issue or host file issue. Or WINS issue some where.

Post ipconfig /all from DC and TS server
0
 
GerhardpetAuthor Commented:
Here it is.
Terminal Server IP Configuration (Windows 2008 R2)

   Host Name . . . . . . . . . . . . : TSERVER
   Primary Dns Suffix  . . . . . . . : intercosmetics.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : intercosmetics.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
 VBD Client)
   Physical Address. . . . . . . . . : 00-26-B9-3A-42-E5
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::9c45:4f00:e230:ae53%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.40.202(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.40.254
   DHCPv6 IAID . . . . . . . . . . . : 234890937
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-75-D1-6B-00-26-B9-3A-42-E5

   DNS Servers . . . . . . . . . . . : 192.168.40.201
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{91BB6D77-2F99-443B-99F6-BF99CF430727}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

DC Server IP Configuration (Windows 2003)

   Host Name . . . . . . . . . . . . : server2
   Primary Dns Suffix  . . . . . . . : intercosmetics.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : intercosmetics.local

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
   Physical Address. . . . . . . . . : 00-0E-0C-7F-6C-8B
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.40.201
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.40.254
   DNS Servers . . . . . . . . . . . : 192.168.40.201

















IPconfig.txt
0
 
Reinert WentzelManaging MemberCommented:
how many nics do you have in the TSERVER?
0
 
Reinert WentzelManaging MemberCommented:
when you ping the dc from the tserver by its dns name what ip does it show you when replying?
0
 
GerhardpetAuthor Commented:
I have two adaptors but one is disabled

When I ping the DC full DNS name from the TS server I get 192.168.40.201 (the IP of the DC)
0
 
Darius GhassemCommented:
0
 
GerhardpetAuthor Commented:
The binding order was set to the disabled adaptor first which is changed now to the enabled adaptor first
Here are the nslookup results:
C:\Users\administrator>nslookup server2
Server:  server2.intercosmetics.local
Address:  192.168.40.201

Name:    server2.intercosmetics.local
Address:  192.168.40.201
0
 
Darius GhassemCommented:
Does it work now?
0
 
Reinert WentzelManaging MemberCommented:
after changing the binding order, does it work now? try also restart server after changing binding order
0
 
GerhardpetAuthor Commented:
Yes after restarting the server it is working now. The funny thing is that at one point I did not have this problem but the ts server is not in production yet

Thank you for your help ReinerWentzel!
0
 
Reinert WentzelManaging MemberCommented:
Great, glad I could be of help. Well I have had similar intermittent issues when the binding order is not correct. With a lot of isa server installs I had  similar issues until correcting the binding order. One moment the isa server would allow me to add users from the ad to the rules and the next second it does not allow me.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.