Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.
How to acess a iomega NAS that a modem does not recognize it
I have a iomega NAS 1 tb, i used to plug it in the router until my isp moved to fiber optic and now the alcatel lucent i240wr modem cant see the NAS. (standard modem provided by telmex company in mexico)
several weeks ago, i still could see the drive with the iomega home storage manager, now, i (plugged to the modem). Now, the modem can no longer see / recognize / detect the NAS.
So, i use a twisted ethernet cable to plug the nas to my laptop, but connection is very unstable, i have to "reset to factory setting" very often in the day because i lost the connection and some times that even does not help.
Sometimes is "0x80070035 network path is not found"
sometimes is a i/o device error
i have made the test of pluging it directly to the ethernet, with standard cable
and goes fine, for less than 5 minutes.
i have windows 7 professional
i bought a new router netgear n750 because net gear told me their router could
acces the nas, but..the modem cant be set to bridge mode so i cant use the router
So..anyone would like to try?
several weeks ago, i still could see the drive with the iomega home storage manager, now, i (plugged to the modem). Now, the modem can no longer see / recognize / detect the NAS.
So, i use a twisted ethernet cable to plug the nas to my laptop, but connection is very unstable, i have to "reset to factory setting" very often in the day because i lost the connection and some times that even does not help.
Sometimes is "0x80070035 network path is not found"
sometimes is a i/o device error
i have made the test of pluging it directly to the ethernet, with standard cable
and goes fine, for less than 5 minutes.
i have windows 7 professional
i bought a new router netgear n750 because net gear told me their router could
acces the nas, but..the modem cant be set to bridge mode so i cant use the router
So..anyone would like to try?
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Hello, good morning. Although i have not changed routers, i tried..but because the new one did not worked, i am still using alcatel lucent i-240-wr
- How does your NAS get an IP address? Is it static? Or via DHCP?
I put it fixed
- What is your NAS's IP address?
The last time i could access the home storage manager it was fixed to 192.168.1.177
- What is your computer's IP address?
192.168.1.171
- What is your router's IP address?
i guess is 192.168.1.254,
- How does your NAS get an IP address? Is it static? Or via DHCP?
I put it fixed
- What is your NAS's IP address?
The last time i could access the home storage manager it was fixed to 192.168.1.177
- What is your computer's IP address?
192.168.1.171
- What is your router's IP address?
i guess is 192.168.1.254,
Although i have not changed routers, i tried..but because the new one did not worked, i am still using alcatel lucent i-240-wrMy intention is to try and get it working on the Alcatel Lucent. Since you said it cannot be put in Bridge mode and it is provided by your ISP we're stuck with it. The Alcatel Lucent i-240-wr is a combination modem and router, right?
Please confirm your router's IP Address. This IP is the "default gateway" IP when you do an "ipconfig /all" on your computer.
Can you ping the IP address of the NAS when it is connected to the network?
Finally, when you attempt to access the NAS from Windows, are you accessing it by it's IP address, e.g. \\192.168.1.177, or by a hostname?
The Alcatel Lucent i-240-wr is a combination modem and router, right?
Yes
Please confirm your router's IP Address.
192.168.1.254
Can you ping the IP address of the NAS when it is connected to the network?
When i ping 192.168.1.177 the answers are
171, 70, 70, 70 "host unreachable" each of them.
Acording to the modem, 171 is the wireless for my laptop
and 70 is the ethernet lan of the laptop.
Finally, when you attempt to access the NAS from Windows, are you accessing it by it's IP address, e.g. \\192.168.1.177, or by a hostname?
i write 192.168.1.177 in google chrome. According to the manual
if there is no DHCP in the network, the NAS will take the addres http://169.254.55.82/
although that one neither take to the admin page of the NAS t
Yes
Please confirm your router's IP Address.
192.168.1.254
Can you ping the IP address of the NAS when it is connected to the network?
When i ping 192.168.1.177 the answers are
171, 70, 70, 70 "host unreachable" each of them.
Acording to the modem, 171 is the wireless for my laptop
and 70 is the ethernet lan of the laptop.
Finally, when you attempt to access the NAS from Windows, are you accessing it by it's IP address, e.g. \\192.168.1.177, or by a hostname?
i write 192.168.1.177 in google chrome. According to the manual
if there is no DHCP in the network, the NAS will take the addres http://169.254.55.82/
although that one neither take to the admin page of the NAS t
well...something happened, i guess the ISP provider did their job, because now i can use my new router which can detect the NAS drive...fine...for 15 minutes or less, it keeps disconnecting.
In the router i plugged the laptop & NAS through ethernet.
default gateway is 10.0.0.1
my laptop address 10.0.0.2 in an ethernet port 1
NAS address 10.0.0.3 is an ethernet port 2
laptop addres in wireless is 10.0.0.4
if i ping the NAS the reply is: packet sent 4, packet received 4
When i startup all the equipment it behaves well.
My NAS crashes it is when i am listening music in itunes, (the whole library is in the NAS,) and in the event i try to change something in the itunes library as add a photo, add new song (previously copied to the NAS) it works fine for...lets say 15 minutes,
i keep playing music, and navigating through the library, and suddenly...it crashes, it no longer can detect the song and i cannot longer access any of the 6 partions of the nas, the message is "network path is not found"
When the NAS disconnects, i can navigate through it contents tru the web version of the admin software , i can download, upload and delet contents, but i can not acces the mapped version in the windows explorer, and neither the itunes could play anything.
In the router i plugged the laptop & NAS through ethernet.
default gateway is 10.0.0.1
my laptop address 10.0.0.2 in an ethernet port 1
NAS address 10.0.0.3 is an ethernet port 2
laptop addres in wireless is 10.0.0.4
if i ping the NAS the reply is: packet sent 4, packet received 4
When i startup all the equipment it behaves well.
My NAS crashes it is when i am listening music in itunes, (the whole library is in the NAS,) and in the event i try to change something in the itunes library as add a photo, add new song (previously copied to the NAS) it works fine for...lets say 15 minutes,
i keep playing music, and navigating through the library, and suddenly...it crashes, it no longer can detect the song and i cannot longer access any of the 6 partions of the nas, the message is "network path is not found"
When the NAS disconnects, i can navigate through it contents tru the web version of the admin software , i can download, upload and delet contents, but i can not acces the mapped version in the windows explorer, and neither the itunes could play anything.
Saaxilk - in your first comment it looks like the NAS was unreachable. When you pinged it you didn't get a response back. This means for whatever reason the NAS was down or at least it wasn't on the IP you expected. At that point nothing will work.
What you read in the manual is the NAS's behavior for when it is configured to get an IP automatically (E.g. via DHCP), but no DHCP server was found on the network. When that happens the NAS will revert to using the static IP 169.254.55.82. This is *strictly* so that you have a way to go in and configure it. As soon as you have a DHCP server on the network your NAS will use that to get an automatic IP.
This is all totally unrelated to you - you said you configured it to get a static IP. If you configure the NAS for a static IP it will use that IP always, regardless of what your router is doing. It is up to you at this point to ensure your NAS has an IP that is on the same subnet as the rest of your network.
-----
In your second comment, you have changed subnet of your network to 10.0.0.xxx. Did you do this? Did you then also reconfigure your NAS to have 10.0.0.3 as it's static IP address? I'm trusting that you did and your NAS isn't just using a dynamic IP.
Assuming all of that, your last paragraph there makes it sound like there is a problem with the NAS itself - you are able to access the web interface over the network (proving that the network is still working fine), and I presume it was pingable, but the folder share was inaccessible from Windows (so the SMB service was down). That's not something that should happen on a working NAS. That would lean me in the direction of the NAS being flaky.
What you read in the manual is the NAS's behavior for when it is configured to get an IP automatically (E.g. via DHCP), but no DHCP server was found on the network. When that happens the NAS will revert to using the static IP 169.254.55.82. This is *strictly* so that you have a way to go in and configure it. As soon as you have a DHCP server on the network your NAS will use that to get an automatic IP.
This is all totally unrelated to you - you said you configured it to get a static IP. If you configure the NAS for a static IP it will use that IP always, regardless of what your router is doing. It is up to you at this point to ensure your NAS has an IP that is on the same subnet as the rest of your network.
-----
In your second comment, you have changed subnet of your network to 10.0.0.xxx. Did you do this? Did you then also reconfigure your NAS to have 10.0.0.3 as it's static IP address? I'm trusting that you did and your NAS isn't just using a dynamic IP.
Assuming all of that, your last paragraph there makes it sound like there is a problem with the NAS itself - you are able to access the web interface over the network (proving that the network is still working fine), and I presume it was pingable, but the folder share was inaccessible from Windows (so the SMB service was down). That's not something that should happen on a working NAS. That would lean me in the direction of the NAS being flaky.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
The NAS IP #.#.#.177 is the one that i used a long time a go, when iomega support told me to assign a fix IP. After several reboots and "return to factory settings", it remains the same #.#.#.177.
The new ip (10.0.0.# ) was assigned by the new router, just after i plug it suddenly it was recognized (that is why i bought to router, to recognize the NAS).
So, assuming the NAS is wrong, how do i recover everthing from it?
In 2 days, the connection has been working only 20 mins max, and again, reset factoy settings, restart laptop & router, for just another 20 minutes of bakcup.
And the assigned IP has been varible from 10.0.0.3, to 4 and last time 2.
Somewhere in the www i read about a unix server station to acces the NAS from "root"
The new ip (10.0.0.# ) was assigned by the new router, just after i plug it suddenly it was recognized (that is why i bought to router, to recognize the NAS).
So, assuming the NAS is wrong, how do i recover everthing from it?
In 2 days, the connection has been working only 20 mins max, and again, reset factoy settings, restart laptop & router, for just another 20 minutes of bakcup.
And the assigned IP has been varible from 10.0.0.3, to 4 and last time 2.
Somewhere in the www i read about a unix server station to acces the NAS from "root"
It seems my problem is..not as easy to develop through ask - answer, it is slow for all the tests i have to go through, although Frosty555 he does knows about the topic.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
Lets focus on that issue first.
How is your NAS configured to connect to the network? Does it have a static IP address?
I am thinking that maybe your NAS was configured with a static IP, and when you changed routers, the new router was configured for a different subnet than your nas (e.g. your NAS was 192.168.1.xxx and your router was 192.168.0.xxx), that would explain the behavior you were seeing.
So please tell me:
- How does your NAS get an IP address? Is it static? Or via DHCP?
- What is your NAS's IP address?
- What is your computer's IP address?
- What is your router's IP address?