Articles

Only one of my 2003 servers can't access NAS

February 7, 2013 at 09:04:15
Specs: Windows Server 2003SP2, 2.99 ghz, 4GB Ram

Going insane here. Installed two NAS servers on the network. All computers can access the NAS shares no problem. Except for one Win2003 server.

This server has a lot of our network shares on it. No issues with users accessing the server. No issues with other servers accessing it. No issues with using this server to browse to other computers or servers. Everything is fine, except when I try to open either of the NAS servers.

They show up when I browse the network, when I try to click them it says "The Specified Network Name Is No Longer Available"


When I try to Start -> Run -> \\nasname, or Start -> Run -> \\nasipaddress I get the same message.

WHen I go to other 2003 servers and try any of these methods, I get to the shares no problem. Same if I try from any of the workstations.

Again, All servers and computers can access this server and it's shares no problem, so I do not believe it is a connectivitiy or networking issue.

Everything works on the network except this error message when this particular server tries to talk to these two NAS devices.

It HAS to be a setting somewhere, right?

I don't have Symantec or Kapersky on here, which GOogle loves to blame.

I also see it happens often when copying a large file, but in my case I cannot access it or browse to it at all from only this server.

(I can, however, browse to the NAS's internal web site, so again, not a connectivity issue)

Please help, been eating at me for a week now

(Additional info: On this server I can ping the NAS by name, it resolves and pings back with good replies. If I NET VIEW by name, I get ERROR 64, Name no longer available. If I NET VIEW from any other server, the command completes successfully)


See More: Only one of my 2003 servers cant access NAS

Report •


#1
February 10, 2013 at 16:38:27

I like to blame Symantec too. What about the basic windows firewall settings? Also, try net use before net view.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
February 11, 2013 at 05:38:33

Thank you for replying,

Net use gives the same error as Net View: Error 64: Specified Network Name is No Longer Available.

And this company uses Trend for it's antivirus, the only Symantec on this system is the Backup Exec, not sure if I can disable anything on that... the whole purpose of the NAS is to backup to so we can eliminate tapes.

Firewall settings look fine, like I said this server can communicate just fine with every other computer and server on the network. In fact, it's our primary file server that everyone's login scripts maps drives to.


Report •

#3
February 11, 2013 at 06:36:36

Add the nas_name & it's IP address to the hosts file, on the server in question. That might work.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
February 11, 2013 at 09:49:39

"On this server I can ping the NAS by name"

No reason to mess with the servers Hosts file. That would be improper anyway. You would make a static entry in the MS DNS server on your lan.

Lets see a ipconfig /all from this problem server for review.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
February 11, 2013 at 10:38:35

Already tried that, didn't work. Here's where I am now:

I can ping NAS no problem, either by IP or by name, so it IS resolving properly.
I can browse to it's internal web server to configure it.
I can FTP to it through command line (using FTP XXXNAS, not just IP address)

(With this I am able to run a backup to a local hard drive, and use a scheduled batch file to FTP it to the share on the NAS, then delete it from the local hard drive. Not a great workaround, but a workaround nonetheless.)

When I browse the network on the server, it shows up. I get the error message when I double click it.

It has to be something in the communication that is only windows based, don't you think? Since I can access it easily through FTP and HTTP? Maybe something is preventing the two devices from handshaking properly?


Report •

#6
February 11, 2013 at 10:48:56

Still waiting for that ipconfig /all

What firewall software is on this server?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#7
February 11, 2013 at 11:40:07

U:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DC-EXCHANGE
Primary Dns Suffix . . . . . . . : heritageXXXX.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : heritageXXXX.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-14-22-78-55-35
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.215.176.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.215.176.250
DNS Servers . . . . . . . . . . . : 10.215.176.100
10.215.176.94


DNS Servers are accurate, gateway, all normal, ect.

Only firewall is default Windows firewall, which is disabled. No need to firewall individual servers, we have firewalls protecting the network as a whole.


Report •

#8
February 11, 2013 at 12:07:57

for comparison, this is the IPCONFIG /ALL for a different 2003 server that connects no problem:

U:\>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0D-60-17-AD-E7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.215.176.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.215.176.250
DNS Servers . . . . . . . . . . . : 10.215.176.100
10.215.176.94


Report •

#9
February 11, 2013 at 12:20:59

Little surprised not to see nebios over tcp/ip enabled = yes.

I would enable netbios over tcp/ip and see if it makes a difference.

You have no issues accessing the nas units from the other dns server at 10.215.176.94?

Does the account you are logging into the server with, does it exist on the nas units?

Might check these registry settings

disable smb2 which is not supported on 2003


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Edit menu, point to New , and then click DWORD Value, Type SMB2 , set value to "0" (zero).

and

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\size

Your choices for this registry key are 1,2 and 3.
1 = Minimize Memory Used
2 = Balance
3 = Maximize Throughput for File Sharing and Maximize Throughput for Network Applications

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#10
February 11, 2013 at 12:41:25

it is kind of odd about the Netbios enabled over TCP IP, when I go to the properties of the network connection, IP properties, Advanced, WINS tab, the "Enable NETBIOS over TCP/IP IS checked.

Think that could be the problem? It's checked but not registering as checked?

There is one account on the NAS server that I set up to enable FTP (as my workaround)

All other computers access it fine, regardless of username/password. But i have been using the same username/password on all the servers.

I will work with the registry after hours tonight when it is safe to reboot and post back.


Report •

#11
February 11, 2013 at 12:52:16

and of course, a big thank you for your time/efforts!

Report •

#12
February 14, 2013 at 12:47:41

Just FYI, been out sick the past few days, will post again when I have an opportunity to reboot the server in question with Wanderer's suggestions.

Report •


Ask Question