Network connectivity on Iomega NAS running W2K server
From: N (walchuk_at_yahoo.com)
Date: 07/31/04
- Next message: Jerold Schulman: "Re: Problem with Share folder"
- Messages sorted by: [ date ] [ thread ]
Date: 31 Jul 2004 00:07:25 -0700
I am having a major issue here that I need to solve this weekend:
Iomega 410m NAS running W2K server, with a 4-disk RAID5 array. My
company uses this primarily as a file server, with a Linksys router as
a DHCP server on a Windows network (~30-40 machines mostly XP Pro,
with a couple XP Home and a few W2K Pro) . Recently we have had some
network slowdowns, so I connected to the NAS to take a look at the NIC
cards on the unit. There are two NICs, with one having the static IP
of 192.168.0.200, and the second, which is DHCP-assigned. I noticed
that way more protocols than we use were bound to the adapters, so I
disabled Appletalk protocol and NWLink for Novell networks on both to
try and eliminate unneccesary resource usage. (we have no Macs or
Novell network usage at all, that I am aware of). I left TCP/IP bound
on both NICs, and they are not "teamed" (learned that hard way that
that kills connectivity to the NAS as well, but solved that issue
earlier in the day).
After doing that, I lost connectivity to the NAS unit. I have
restarted it, and the NIC configured for DHCP picks up an IP address
from the router (192.168.0.12). However, with the exception of one
successful response this evening (1 success, 3 lost), there is no
response when I ping that address, even though it shows up as \\SERVER
(the server name) when I use the net view command. the static IP
doesn't work either. I don't have a network monitor program/sniffer,
so I don't know if the NIC with the static address is up or not. All
I know is that I can't ping or otherwise connect to that one either.
Last but not least, this is apparently one of Iomega's units that
don't allow for connecting a keyboard/mouse/monitor to manipulate
directly - I've tried (i.e. I can't reboot and press F8 to get to safe
mode - it just sticks at the windows server logo startup screen). I
have to go through the network via Terminal Services/Remote Desktop
Connection, or through the Web interface. Iomega so far has told me
that if I can't get the connection to work, their answer is to ship me
a new disk, which will erase everything on the NAS unit. While I have
a recent backup of the files, I REALLY would like to avoid the hassle.
Does anyone have a suggestion on a) a reason why the unit picks up an
IP, but I can't ping or otherwise connect? or b) a workaround to get
in?
If I can't figure this out by Monday morning Pacific Coast time, I
will have to bite the bullet and have Iomega ship a new disk, which
means lots of lost data...help?!
- Next message: Jerold Schulman: "Re: Problem with Share folder"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
