We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

2008 R2 accessing 2003 network share

PaulDub
PaulDub asked
on
Medium Priority
441 Views
Last Modified: 2013-11-05
Hey all,
I have a Windows Server 2008 R2 standard that is having problems accessing one network server share. The server the share is on is a 2003 server. This is the kicker, I can access all other servers (2008 and 2003) on the network but this one and its our file server that everyone hits. I can hit the server using it fully qualified domain name. The problem is that the 2008 server has a program installed that is looking for the 2003 server to save files and can't see it.

Things I've tried:
editing the reg of the program with the fully qualified domain name to save files (didn't work)
edit the hosts file on the 2008 server (didn't work)

Thanks for any help

Paul

Comment
Watch Question

CERTIFIED EXPERT

Commented:
1) Can you access the share with typing in run:  \\192.168.1.1 , \\server2003 and \\server2003.mydomain.local (192.168.1.1 is IP of the Server2003) ?
2) Check DNS IP addres on 2008 R2 IP settings.

Author

Commented:
Sorry got it working. Not sure what was up. I was able to see that no one was hitting the server and I rebooted. That seemed to have done the trick. Sorry I could not have rebooted before as users where on it. I got lucky.

Paul

Author

Commented:
Problem is back today. I would like to reopen it

Author

Commented:
To answer your questions Ravakl:
I'm able to hit the server all the way you asked but I can not access it by \\servername or \\servername.domain.local

IP works \\servername.domain.com works
Dns is setup correctly on the nic and seems to be working because I can access all the other servers on my network.

Thanks
Paul
CERTIFIED EXPERT

Commented:
1) The first time the problem was solved after reboot Server 2003?
2) Is the name of your local AD domain mydomain.local or mydomain.com?
3) You write:  I'm able to hit the server all the way you asked but I can not access it by \\servername or \\servername.domain.local
 It looks like that 2008 server can't resolve name of 2003 Server.
When you can access to the share with IP (for example  \\192.168.1.1 ) and can't access with FQDN         ( \\servername.mydomain.local ) try to >ping servername and >ping servername.mydomain.local. Try the same from another servers or PC's.
After this step  you can say: is this the problem of your 2003 Server and nobody can access to the share (as you say " I was able to see that no one was hitting the server ") OR only 2008 server has an access problem to the share on 2003 machine...
4)Please check on both servers Event Log.
Let me know about results

Author

Commented:
1) It was temporary fixed after a reboot of the 2008 server. (I had to go ahead and reboot last night to get it working again)
2) The local domain is mydomain.com
3) I can access the server with \\servername.domain.com (FQDN). I just wasn't sure if \\servername.domain.local was supposed to work. We need to forget the whole .local thing. Sorry for my confusion.
I'm able to ping the server by name. (ping servername).
I have always been able to access the 2003 server from any machine but this one.

The 2003 server is our file server and everyone can access it or my phone would be off the hook. : )

Thanks
Paul

Author

Commented:
Going to move this server to a VM. I can not figure this one out.
How do I close this question?
This looks to me like an issue with the DNS heirarchical structure.    Are you sure everything is pointing to the correct provider of DNS?

Author

Commented:
I'm not sure what to say. This server can access all 10 other 2008 and 2003 servers on the domain by name. I'm really confused. Is there a way to trump DNS servers for one server?

The temporary reboot fix just adds to my confusion.


Paul  
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Commented:
What do you get if you ping
servername.domain.local
or
servername?

Author

Commented:
Okay started to go down the list:
Networking (GOOD)
nslookup (GOOD)
Oh wait now it's working! Check my cmd copy and paste from the 2008 server:



Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.domain.com>ping DNS1

Pinging DNS1.domain.com [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128

Ping statistics for x.x.x.x:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\administrator.domain.com>nslookup
Default Server:  DNS1.domain.com
Address:  x.x.x.x

> 2003-Server
Server:  DNS1.domain.com
Address:  x.x.x.x

Name:    2003-Server.domain.com
Address:  x.x.x.x

> exit

C:\Users\administrator.domain.com>nslookup DNS2
Server:  DNS1.domain.com
Address:  x.x.x.x

Name:    DNS2.domain.com
Address:  x.x.x.x


C:\Users\administrator.domain.com>ping DNS3

Pinging DNS3.domain.com [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128

Ping statistics for x.x.x.x:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\administrator.domain.com>nslookup
Default Server:  DNS3.domain.com
Address:  x.x.x.x

> 2003-Server
Server:  DNS3.domain.com
Address:  x.x.x.x

Name:    2003-Server.domain.com
Address:  x.x.x.x

> exit

C:\Users\administrator.domain.com>ping 2003-Server

Pinging 2003-Server.domain.com [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128

Ping statistics for x.x.x.x:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\administrator.domain.com>

Now I can access the network shares. My mind just went boom. lol
What do you all make of this?

Thanks
Paul

Author

Commented:
The server can still the shares. Can anyone tell me why running a nslookup query made this server work?

Paul
My guess would be something to do with triggering some kind of reset or initialisation process.  If there is any cacheing going on somewhere then it may clear out tables containing stale records.  It sounds like a "participant observer" situation because when you tried to observe the problem, the process of observation cleared the problem.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.