Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 693
  • Last Modified:

NAS device - CAN ping with IP; CANNOT ping with device name???

Experts:

Having issues with a new seagate 2TB NAS device....

Facts:
Running windows 2003 server, AND Windows 2000 server.
Running DHCP
NAS device on IP: 192.168.1.80
NAS device name:  BA-381494
NAS device connected to switch.
I can ping NAS via IP address; however, CANNOT ping by device name
Because necessary to start using the NAS, I have set up shares to the NAS with IP adress....  Yes, I know not optimal.
CAN ONLY see the NAS from the 2003 server through shares set up wtih IP.
From 2000 server, I can see the shares, as well as the ENTIRE NAS device under a folder "WORKGROUP" in the network neighborhood

I need to be able to reference shares on the NAS device by device name...  Will solve serveral problems for me....

Any assistance is greatly appreciated.
0
Rick Norris
Asked:
Rick Norris
2 Solutions
 
Carol ChisholmCommented:
You could create an A record in your DNS server with the NAS name and IP address.
0
 
atrevidoCommented:
DNS record as carolchi says.  Here is a way to make sure they get created automatically.  See attached jpeg.  If you don't have a DNS server on the network then use LMHOSTS file.  see this link
http://support.microsoft.com/kb/105997
DNS-settings-check-box.jpg
0
 
Rick NorrisAuthor Commented:
More Info....

Just discovered that I CAN ping both IP, AND device name from a workstation.  Also, I can set up a LOCAL share by device name, FROM the local desktop.... but cannot from the 2003 server itself???

On the 2003 server, I CANNOT ping by device name, or set up a share by device name...?????

I need to be able to put the path in my "mappings.bat" file so everyone gets the same drive mappings; however, will not work from the server....?????????

If I attempt to set up a share on the 2003 server, I get an error message - "Drive could not be mapped because no network was found."    

NOW, I'm totally confused...

Thanks
0
Cyber Threats to Small Businesses (Part 1)

This past May, Webroot surveyed more than 600 IT decision-makers at medium-sized companies to see how these small businesses perceived new threats facing their organizations.  Read what Webroot CISO, Gary Hayslip, has to say about the survey in part 1 of this 2-part blog series.

 
Carol ChisholmCommented:
Have you done the DNS record?
0
 
Carol ChisholmCommented:
Can you ping other devices by name from your server?
0
 
AkinsdNetwork AdministratorCommented:
Do an ipconfig /all on the NAS and check the domain
Looks like you can't access flat name addresses meaning you either configure flat name spaces, or configure wins or just use the fqdn.

Try pinging the fqdn
Results of ipconfig /all
Host. Test
DNS suffix. host.comcast.net

Your fqdn will be
Test.host.comcast.net
0
 
avcontrolCommented:
1. Mapping drives, base on WinsName/NetBios, which could enable/disable on PC's.
If it is enable LAN  will see each other(this often use for some other programs)
2. For DNS to work, you need DNS server(in congestion with DHCP server),  and local machine with IP configuration pointed to this DNS, or any other DNS who would have records of particular name-to-IP  mapping.

Unless you understand well windows server, it might not be easy to configure this properly.
On avarage LAN DHCP ussially issued by gateway router, who would also provide DNS, but either to the router itself, or DNS address of ISP other on WAN. But they would have no record of your "local" DNS win2008.
In other words you need to find way include NAS name and IP allocated for NAS to be present in DNS server to which other LAN members referencing to it.
0
 
Rick NorrisAuthor Commented:
Everyone:

I am sorry for the delay....  Went to doctor yesterday afternoon.... and in office now...  will try some of the suggestions and get back with everyone today.

Thanks again for all the help!!
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now