PDA

View Full Version : Problems with a WD 1TB Network drive



Iced Tea
11-09-08, 04:07 AM
I have a Linksys WRT54GL Wireless Router on my network and a Western Digital
My Book World Edition 1TB Network Drive. For some reason after several
hours (haven't timed it so I don't actually know how long)on the network the
WD Network drive becomes inaccessible. I sent back the first drive and got
another one brand new right out of the box and I have the same issues.

Contacted WD Supprt and so far no success on the problem as to why this
happens. the only way that I can get then network to see the drive again is
to unplug the power from the back of the WD Network drive. I have an HP
Officejet that is on the network and I don't have any problems with it.

Anyone familiar with the router and network drive I have? Will taking any
help at this point.

Bob M
11-09-08, 02:52 PM
Iced Tea wrote:

> I have a Linksys WRT54GL Wireless Router on my network and a Western
> Digital
> My Book World Edition 1TB Network Drive. For some reason after several
> hours (haven't timed it so I don't actually know how long)on the network
> the WD Network drive becomes inaccessible. I sent back the first drive and
> got another one brand new right out of the box and I have the same issues.
>
> Contacted WD Supprt and so far no success on the problem as to why this
> happens. the only way that I can get then network to see the drive again
> is to unplug the power from the back of the WD Network drive. I have an HP
> Officejet that is on the network and I don't have any problems with it.
>
> Anyone familiar with the router and network drive I have? Will taking any
> help at this point.

While this may not resolve your problem it wouldn't hurt to try and
configure the drive for "static" IP and assign it an address on your
network. The reason is that if your DHCP "lease" is expiring the drive
controller may not be reacquiring a new address.

Just a hunch... Good luck.

Iced Tea
11-10-08, 07:14 AM
I know how to manually configure the WD Network Drive for a static IP but
not sure on the router though???

"Bob M" <r.mariotti@fdcx.net> wrote in message
news:gf7ikc$jh$1@registered.motzarella.org...
> Iced Tea wrote:
>
>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>> Digital
>> My Book World Edition 1TB Network Drive. For some reason after several
>> hours (haven't timed it so I don't actually know how long)on the network
>> the WD Network drive becomes inaccessible. I sent back the first drive
>> and
>> got another one brand new right out of the box and I have the same
>> issues.
>>
>> Contacted WD Supprt and so far no success on the problem as to why this
>> happens. the only way that I can get then network to see the drive again
>> is to unplug the power from the back of the WD Network drive. I have an
>> HP
>> Officejet that is on the network and I don't have any problems with it.
>>
>> Anyone familiar with the router and network drive I have? Will taking any
>> help at this point.
>
> While this may not resolve your problem it wouldn't hurt to try and
> configure the drive for "static" IP and assign it an address on your
> network. The reason is that if your DHCP "lease" is expiring the drive
> controller may not be reacquiring a new address.
>
> Just a hunch... Good luck.

GlowingBlueMist
11-10-08, 04:07 PM
"Iced Tea" <icedteas@cox.net> wrote in message
news:VsWRk.2614$e5.1518@newsfe01.iad...
>I know how to manually configure the WD Network Drive for a static IP but
>not sure on the router though???
>
> "Bob M" <r.mariotti@fdcx.net> wrote in message
> news:gf7ikc$jh$1@registered.motzarella.org...
>> Iced Tea wrote:
>>
>>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>>> Digital
>>> My Book World Edition 1TB Network Drive. For some reason after several
>>> hours (haven't timed it so I don't actually know how long)on the network
>>> the WD Network drive becomes inaccessible. I sent back the first drive
>>> and
>>> got another one brand new right out of the box and I have the same
>>> issues.
>>>
>>> Contacted WD Supprt and so far no success on the problem as to why this
>>> happens. the only way that I can get then network to see the drive again
>>> is to unplug the power from the back of the WD Network drive. I have an
>>> HP
>>> Officejet that is on the network and I don't have any problems with it.
>>>
>>> Anyone familiar with the router and network drive I have? Will taking
>>> any
>>> help at this point.
>>
>> While this may not resolve your problem it wouldn't hurt to try and
>> configure the drive for "static" IP and assign it an address on your
>> network. The reason is that if your DHCP "lease" is expiring the drive
>> controller may not be reacquiring a new address.
>>
>> Just a hunch... Good luck.
>
>
Nothing is usually needed to be done at the router except to possibly put a
limit on the maximum number of DHCP address values it can assign. Just make
sure that the fixed IP is not one that the router has permission to assign
using DHCP. In my case I have my router limited to the first 50 address
entries for DHCP starting with 192.168.1.1. Any fixed IP's I assign to
devices like servers or test machines all in the 192.168.1.200 - 254 range.
That way there is never an overlap caused by the router giving out an IP
already in use by a fixed IP device and I still have room to expand the DHCP
range if needed..

Iced Tea
11-11-08, 07:14 PM
I am not sure what to fill in where when setting the static IP on this
network drive. I am so new to networking, I am learning and looking at
getting a book or two to expand my knowledge.

Anyway when I go into the manual configuration on the network drive it asks
the following:

Step #1 - Network Address and Subnet Settings
Network Address: xxx.xxx.xxx.xxx

Subnet Mask: 255.255.255.0

Step #2 - Gateway
Gateway: xxx.xxx.xxx.xxx

DNS Servers: xxx.xxx.xxx.xxx
xxx.xxx.xxx.xxx
xxx.xxx.xxx.xxx
xxx.xxx.xxx.xxx

NTP Server:


Not sure what goes, but this is my guess bases on what little I have
learned:

Network Address: static IP I would assign to the network
Subnet Mask: I dont know
Gateway: IP address of my router
DNS Servers: I don't know
NTP Server: I don't know

Any help would be greatly appreciated.

Carl

"GlowingBlueMist" <nobody@nowhere.com> wrote in message
news:4918f27c$0$33683$892e0abb@auth.newsreader.octanews.com...
> "Iced Tea" <icedteas@cox.net> wrote in message
> news:VsWRk.2614$e5.1518@newsfe01.iad...
>>I know how to manually configure the WD Network Drive for a static IP but
>>not sure on the router though???
>>
>> "Bob M" <r.mariotti@fdcx.net> wrote in message
>> news:gf7ikc$jh$1@registered.motzarella.org...
>>> Iced Tea wrote:
>>>
>>>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>>>> Digital
>>>> My Book World Edition 1TB Network Drive. For some reason after several
>>>> hours (haven't timed it so I don't actually know how long)on the
>>>> network
>>>> the WD Network drive becomes inaccessible. I sent back the first drive
>>>> and
>>>> got another one brand new right out of the box and I have the same
>>>> issues.
>>>>
>>>> Contacted WD Supprt and so far no success on the problem as to why this
>>>> happens. the only way that I can get then network to see the drive
>>>> again
>>>> is to unplug the power from the back of the WD Network drive. I have an
>>>> HP
>>>> Officejet that is on the network and I don't have any problems with it.
>>>>
>>>> Anyone familiar with the router and network drive I have? Will taking
>>>> any
>>>> help at this point.
>>>
>>> While this may not resolve your problem it wouldn't hurt to try and
>>> configure the drive for "static" IP and assign it an address on your
>>> network. The reason is that if your DHCP "lease" is expiring the drive
>>> controller may not be reacquiring a new address.
>>>
>>> Just a hunch... Good luck.
>>
>>
> Nothing is usually needed to be done at the router except to possibly put
> a limit on the maximum number of DHCP address values it can assign. Just
> make sure that the fixed IP is not one that the router has permission to
> assign using DHCP. In my case I have my router limited to the first 50
> address entries for DHCP starting with 192.168.1.1. Any fixed IP's I
> assign to devices like servers or test machines all in the 192.168.1.200 -
> 254 range. That way there is never an overlap caused by the router giving
> out an IP already in use by a fixed IP device and I still have room to
> expand the DHCP range if needed..
>

1PW
11-11-08, 08:04 PM
On 11/11/2008 05:14 PM, Iced Tea sent:
> I am not sure what to fill in where when setting the static IP on this
> network drive. I am so new to networking, I am learning and looking at
> getting a book or two to expand my knowledge.
>
> Anyway when I go into the manual configuration on the network drive it asks
> the following:
>
> Step #1 - Network Address and Subnet Settings
> Network Address: xxx.xxx.xxx.xxx
>
> Subnet Mask: 255.255.255.0
>
> Step #2 - Gateway
> Gateway: xxx.xxx.xxx.xxx
>
> DNS Servers: xxx.xxx.xxx.xxx
> xxx.xxx.xxx.xxx
> xxx.xxx.xxx.xxx
> xxx.xxx.xxx.xxx
>
> NTP Server:
>
>
> Not sure what goes, but this is my guess bases on what little I have
> learned:
>
> Network Address: static IP I would assign to the network

Make this the same as the former DHCP address for now. In the future,
you may wish to make this /above/ the range of your router's usual DHCP
allotments. Example: 192.168.1.101

> Subnet Mask: I dont know

255.255.255.0 if you were to use the above example.

> Gateway: IP address of my router

192.168.1.1 typically

> DNS Servers: I don't know

On your Windows PC, and from a "CMD" prompt: >ipconfig/all

Pick out the DNS server addresses, in the order given, by your ISP.

> NTP Server: I don't know

Pick a geographical nearby "Stratum 2" Network Time Protocol server.

>
> Any help would be greatly appreciated.
>
> Carl

Best wishes to you Carl.

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-13-08, 08:13 PM
So the NTP Server is just a name I need to assign?

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gfddjn$rft$1@registered.motzarella.org...
> On 11/11/2008 05:14 PM, Iced Tea sent:
>> I am not sure what to fill in where when setting the static IP on this
>> network drive. I am so new to networking, I am learning and looking at
>> getting a book or two to expand my knowledge.
>>
>> Anyway when I go into the manual configuration on the network drive it
>> asks
>> the following:
>>
>> Step #1 - Network Address and Subnet Settings
>> Network Address: xxx.xxx.xxx.xxx
>>
>> Subnet Mask: 255.255.255.0
>>
>> Step #2 - Gateway
>> Gateway: xxx.xxx.xxx.xxx
>>
>> DNS Servers: xxx.xxx.xxx.xxx
>> xxx.xxx.xxx.xxx
>> xxx.xxx.xxx.xxx
>> xxx.xxx.xxx.xxx
>>
>> NTP Server:
>>
>>
>> Not sure what goes, but this is my guess bases on what little I have
>> learned:
>>
>> Network Address: static IP I would assign to the network
>
> Make this the same as the former DHCP address for now. In the future,
> you may wish to make this /above/ the range of your router's usual DHCP
> allotments. Example: 192.168.1.101
>
>> Subnet Mask: I dont know
>
> 255.255.255.0 if you were to use the above example.
>
>> Gateway: IP address of my router
>
> 192.168.1.1 typically
>
>> DNS Servers: I don't know
>
> On your Windows PC, and from a "CMD" prompt: >ipconfig/all
>
> Pick out the DNS server addresses, in the order given, by your ISP.
>
>> NTP Server: I don't know
>
> Pick a geographical nearby "Stratum 2" Network Time Protocol server.
>
>>
>> Any help would be greatly appreciated.
>>
>> Carl
>
> Best wishes to you Carl.
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-13-08, 10:35 PM
On 11/13/2008 06:13 PM, Iced Tea sent:
> So the NTP Server is just a name I need to assign?
>
> Carl
>
> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
> news:gfddjn$rft$1@registered.motzarella.org...
>> On 11/11/2008 05:14 PM, Iced Tea sent:
>>> I am not sure what to fill in where when setting the static IP on this
>>> network drive. I am so new to networking, I am learning and looking at
>>> getting a book or two to expand my knowledge.
>>>
>>> Anyway when I go into the manual configuration on the network drive it
>>> asks
>>> the following:
>>>
>>> Step #1 - Network Address and Subnet Settings
>>> Network Address: xxx.xxx.xxx.xxx
>>>
>>> Subnet Mask: 255.255.255.0
>>>
>>> Step #2 - Gateway
>>> Gateway: xxx.xxx.xxx.xxx
>>>
>>> DNS Servers: xxx.xxx.xxx.xxx
>>> xxx.xxx.xxx.xxx
>>> xxx.xxx.xxx.xxx
>>> xxx.xxx.xxx.xxx
>>>
>>> NTP Server:
>>>
>>>
>>> Not sure what goes, but this is my guess bases on what little I have
>>> learned:
>>>
>>> Network Address: static IP I would assign to the network
>> Make this the same as the former DHCP address for now. In the future,
>> you may wish to make this /above/ the range of your router's usual DHCP
>> allotments. Example: 192.168.1.101
>>
>>> Subnet Mask: I dont know
>> 255.255.255.0 if you were to use the above example.
>>
>>> Gateway: IP address of my router
>> 192.168.1.1 typically
>>
>>> DNS Servers: I don't know
>> On your Windows PC, and from a "CMD" prompt: >ipconfig/all
>>
>> Pick out the DNS server addresses, in the order given, by your ISP.
>>
>>> NTP Server: I don't know
>> Pick a geographical nearby "Stratum 2" Network Time Protocol server.
>>
>>> Any help would be greatly appreciated.
>>>
>>> Carl
>> Best wishes to you Carl.
>>
>> --
>> 1PW
>>
>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>
>

Yes. That's correct. I stated that you should select a stratum 2 NTP
server. Sometimes a nearby large college will have one.

Google for NTP servers for your area. Sometimes the folks that care for
the server would like a note from you telling them that you'd be using
their NTP service from your system. As long as your equipment
doesn't place a high demand on their system, they'll be OK with your
request.

Another good place to start your search is: <http://www.ntp.org/>.

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-15-08, 02:46 AM
I haven't yet changed the Network Drive to s static IP yet. I don have
another question though. As I was looking through what few menus exist on
the drive for settings, I did come across where you can change the device
name and the workgroup name. How important is this? I found nothing on the
WD site about it, but I know when I set up my desktop and laptop I thought I
remember something to the fact about having the workgroup names the same. At
this time the Network Drive does have a different workgroup name. Just
something else I thought I would ask about.

I also thought about buying a book or 2 to learn about networking, does
anyone have any suggestions? Are there some that are better than others?

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gfiv5s$hm1$1@feeder.motzarella.org...
> On 11/13/2008 06:13 PM, Iced Tea sent:
>> So the NTP Server is just a name I need to assign?
>>
>> Carl
>>
>> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
>> news:gfddjn$rft$1@registered.motzarella.org...
>>> On 11/11/2008 05:14 PM, Iced Tea sent:
>>>> I am not sure what to fill in where when setting the static IP on this
>>>> network drive. I am so new to networking, I am learning and looking at
>>>> getting a book or two to expand my knowledge.
>>>>
>>>> Anyway when I go into the manual configuration on the network drive it
>>>> asks
>>>> the following:
>>>>
>>>> Step #1 - Network Address and Subnet Settings
>>>> Network Address: xxx.xxx.xxx.xxx
>>>>
>>>> Subnet Mask: 255.255.255.0
>>>>
>>>> Step #2 - Gateway
>>>> Gateway: xxx.xxx.xxx.xxx
>>>>
>>>> DNS Servers: xxx.xxx.xxx.xxx
>>>> xxx.xxx.xxx.xxx
>>>> xxx.xxx.xxx.xxx
>>>> xxx.xxx.xxx.xxx
>>>>
>>>> NTP Server:
>>>>
>>>>
>>>> Not sure what goes, but this is my guess bases on what little I have
>>>> learned:
>>>>
>>>> Network Address: static IP I would assign to the network
>>> Make this the same as the former DHCP address for now. In the future,
>>> you may wish to make this /above/ the range of your router's usual DHCP
>>> allotments. Example: 192.168.1.101
>>>
>>>> Subnet Mask: I dont know
>>> 255.255.255.0 if you were to use the above example.
>>>
>>>> Gateway: IP address of my router
>>> 192.168.1.1 typically
>>>
>>>> DNS Servers: I don't know
>>> On your Windows PC, and from a "CMD" prompt: >ipconfig/all
>>>
>>> Pick out the DNS server addresses, in the order given, by your ISP.
>>>
>>>> NTP Server: I don't know
>>> Pick a geographical nearby "Stratum 2" Network Time Protocol server.
>>>
>>>> Any help would be greatly appreciated.
>>>>
>>>> Carl
>>> Best wishes to you Carl.
>>>
>>> --
>>> 1PW
>>>
>>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>>
>>
>
> Yes. That's correct. I stated that you should select a stratum 2 NTP
> server. Sometimes a nearby large college will have one.
>
> Google for NTP servers for your area. Sometimes the folks that care for
> the server would like a note from you telling them that you'd be using
> their NTP service from your system. As long as your equipment
> doesn't place a high demand on their system, they'll be OK with your
> request.
>
> Another good place to start your search is: <http://www.ntp.org/>.
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Bob M
11-15-08, 08:25 AM
Iced Tea wrote:

> I haven't yet changed the Network Drive to s static IP yet. I don have
> another question though. As I was looking through what few menus exist on
> the drive for settings, I did come across where you can change the device
> name and the workgroup name. How important is this? I found nothing on the
> WD site about it, but I know when I set up my desktop and laptop I thought
> I remember something to the fact about having the workgroup names the
> same. At this time the Network Drive does have a different workgroup name.
> Just something else I thought I would ask about.
>
> I also thought about buying a book or 2 to learn about networking, does
> anyone have any suggestions? Are there some that are better than others?
>
> Carl
>
> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
> news:gfiv5s$hm1$1@feeder.motzarella.org...
>> On 11/13/2008 06:13 PM, Iced Tea sent:
>>> So the NTP Server is just a name I need to assign?
>>>
>>> Carl
>>>
>>> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
>>> news:gfddjn$rft$1@registered.motzarella.org...
>>>> On 11/11/2008 05:14 PM, Iced Tea sent:
>>>>> I am not sure what to fill in where when setting the static IP on this
>>>>> network drive. I am so new to networking, I am learning and looking at
>>>>> getting a book or two to expand my knowledge.
>>>>>
>>>>> Anyway when I go into the manual configuration on the network drive it
>>>>> asks
>>>>> the following:
>>>>>
>>>>> Step #1 - Network Address and Subnet Settings
>>>>> Network Address: xxx.xxx.xxx.xxx
>>>>>
>>>>> Subnet Mask: 255.255.255.0
>>>>>
>>>>> Step #2 - Gateway
>>>>> Gateway: xxx.xxx.xxx.xxx
>>>>>
>>>>> DNS Servers: xxx.xxx.xxx.xxx
>>>>> xxx.xxx.xxx.xxx
>>>>> xxx.xxx.xxx.xxx
>>>>> xxx.xxx.xxx.xxx
>>>>>
>>>>> NTP Server:
>>>>>
>>>>>
>>>>> Not sure what goes, but this is my guess bases on what little I have
>>>>> learned:
>>>>>
>>>>> Network Address: static IP I would assign to the network
>>>> Make this the same as the former DHCP address for now. In the future,
>>>> you may wish to make this /above/ the range of your router's usual DHCP
>>>> allotments. Example: 192.168.1.101
>>>>
>>>>> Subnet Mask: I dont know
>>>> 255.255.255.0 if you were to use the above example.
>>>>
>>>>> Gateway: IP address of my router
>>>> 192.168.1.1 typically
>>>>
>>>>> DNS Servers: I don't know
>>>> On your Windows PC, and from a "CMD" prompt: >ipconfig/all
>>>>
>>>> Pick out the DNS server addresses, in the order given, by your ISP.
>>>>
>>>>> NTP Server: I don't know
>>>> Pick a geographical nearby "Stratum 2" Network Time Protocol server.
>>>>
>>>>> Any help would be greatly appreciated.
>>>>>
>>>>> Carl
>>>> Best wishes to you Carl.
>>>>
>>>> --
>>>> 1PW
>>>>
>>>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>>>
>>>
>>
>> Yes. That's correct. I stated that you should select a stratum 2 NTP
>> server. Sometimes a nearby large college will have one.
>>
>> Google for NTP servers for your area. Sometimes the folks that care for
>> the server would like a note from you telling them that you'd be using
>> their NTP service from your system. As long as your equipment
>> doesn't place a high demand on their system, they'll be OK with your
>> request.
>>
>> Another good place to start your search is: <http://www.ntp.org/>.
>>
>> --
>> 1PW
>>
>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]


IMHO - the workgroup on ALL your networked devices need to be the same to
allow then to "see" each other. That includes your PC's and NAS's.

One book that might help is the standard yellow and black "Networking for
Dummies" which you should be able to find used on Amazon.com books for a
buck or two.

Hope this helps.

Iced Tea
11-22-08, 02:56 AM
Drive now has a static IP and the workgroup name matches and still the same
result. The only support I can get from WD is that it is the router or
something in the configuration. So at this point it sounds like they are
going to be much help. They offered yet another exchange but I can't see
getting 2 of them that are defective. I have even connected the network
drive to different ports on the router and I get the same result. Even used
the ethernet cable that was supplied with the drive. At this point I am out
of answers and it looks like I will be out some more money to send this
thing back. Anyway have any more suggetions?

Carl
"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gfddjn$rft$1@registered.motzarella.org...
> On 11/11/2008 05:14 PM, Iced Tea sent:
>> I am not sure what to fill in where when setting the static IP on this
>> network drive. I am so new to networking, I am learning and looking at
>> getting a book or two to expand my knowledge.
>>
>> Anyway when I go into the manual configuration on the network drive it
>> asks
>> the following:
>>
>> Step #1 - Network Address and Subnet Settings
>> Network Address: xxx.xxx.xxx.xxx
>>
>> Subnet Mask: 255.255.255.0
>>
>> Step #2 - Gateway
>> Gateway: xxx.xxx.xxx.xxx
>>
>> DNS Servers: xxx.xxx.xxx.xxx
>> xxx.xxx.xxx.xxx
>> xxx.xxx.xxx.xxx
>> xxx.xxx.xxx.xxx
>>
>> NTP Server:
>>
>>
>> Not sure what goes, but this is my guess bases on what little I have
>> learned:
>>
>> Network Address: static IP I would assign to the network
>
> Make this the same as the former DHCP address for now. In the future,
> you may wish to make this /above/ the range of your router's usual DHCP
> allotments. Example: 192.168.1.101
>
>> Subnet Mask: I dont know
>
> 255.255.255.0 if you were to use the above example.
>
>> Gateway: IP address of my router
>
> 192.168.1.1 typically
>
>> DNS Servers: I don't know
>
> On your Windows PC, and from a "CMD" prompt: >ipconfig/all
>
> Pick out the DNS server addresses, in the order given, by your ISP.
>
>> NTP Server: I don't know
>
> Pick a geographical nearby "Stratum 2" Network Time Protocol server.
>
>>
>> Any help would be greatly appreciated.
>>
>> Carl
>
> Best wishes to you Carl.
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-22-08, 06:26 AM
On 11/22/2008 12:56 AM, Iced Tea sent:
> Drive now has a static IP and the workgroup name matches and still the same
> result. The only support I can get from WD is that it is the router or
> something in the configuration. So at this point it sounds like they are
> going to be much help. They offered yet another exchange but I can't see
> getting 2 of them that are defective. I have even connected the network
> drive to different ports on the router and I get the same result. Even used
> the Ethernet cable that was supplied with the drive. At this point I am out
> of answers and it looks like I will be out some more money to send this
> thing back. Anyway have any more suggestions?
>
> Carl

Hello Carl:

Now, won't you need to go into your router's setup and make a
sympathetic entry to match static IP you've just created?

Does it seem to have been a DHCP lease expiration issue?

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-22-08, 07:42 AM
Not sure if I need to or not, I have a Linksys WRT54GL Wireless Router.

On the expiration issue that is what I thought at first, I could reset the
drive back to a DHCP and then look at the expiration and keep an eye on it
to see if that is when the drive disappears from the network.

I appreciate your help in trying to resolve my issues with this thing.

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gg8tqi$duv$1@news.motzarella.org...
> On 11/22/2008 12:56 AM, Iced Tea sent:
>> Drive now has a static IP and the workgroup name matches and still the
>> same
>> result. The only support I can get from WD is that it is the router or
>> something in the configuration. So at this point it sounds like they are
>> going to be much help. They offered yet another exchange but I can't see
>> getting 2 of them that are defective. I have even connected the network
>> drive to different ports on the router and I get the same result. Even
>> used
>> the Ethernet cable that was supplied with the drive. At this point I am
>> out
>> of answers and it looks like I will be out some more money to send this
>> thing back. Anyway have any more suggestions?
>>
>> Carl
>
> Hello Carl:
>
> Now, won't you need to go into your router's setup and make a
> sympathetic entry to match static IP you've just created?
>
> Does it seem to have been a DHCP lease expiration issue?
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Bob Fry
11-22-08, 11:02 AM
>>>>> "IT" == Iced Tea <icedteas@cox.net> writes:

IT> I appreciate your help in trying to resolve my issues with
IT> this thing.

Can you post links to the online manuals for the drive and router.
--
You can't say civilizations don't advance, because they kill you in a
new way in each war.
~ Will Rogers

1PW
11-22-08, 11:15 AM
On 11/22/2008 05:42 AM, Iced Tea sent:
> Not sure if I need to or not, I have a Linksys WRT54GL Wireless Router.
>
> On the expiration issue that is what I thought at first, I could reset the
> drive back to a DHCP and then look at the expiration and keep an eye on it
> to see if that is when the drive disappears from the network.
>
> I appreciate your help in trying to resolve my issues with this thing.
>
> Carl

Hello Carl:

I tried looking at the illustrations in the Linksys WRT54GL User Guide,
but their on-line pdf does not work well with enlargement of its
embedded images. I tried to see if the DHCP lease time could be set to
some extremely large time value and I was also trying to see if the
router /itself/ could declare some addresses as static.

Ultimately, maybe you might need to contact Linksys/Cisco technical
support. Your router may have had a firmware update issued earlier this
year, and tech support may possibly ask you to verify that your firmware
is the latest.

It's a pleasure to help you. I've actually dreamed up an idea of trying
to cascade my Linksys Gateway and my Linksys Router in my own SOHO
installation. That came about during this thread. Thank YOU!

Pete
--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-22-08, 12:08 PM
Here are the links to the manuals:

Linksys WRT54GL

http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02

WD My Book World Edition (I am using the drive under the 'Shared Storage
Manager'

http://www.wdc.com/en/library/usb/2779-701026.pdf?wdc_lang=en

Thanks for taking the time to try and help me solve my problem.

Carl
"Bob Fry" <bobfry@mailinator.com> wrote in message
news:od078zia.fsf@mailinator.com...
>>>>>> "IT" == Iced Tea <icedteas@cox.net> writes:
>
> IT> I appreciate your help in trying to resolve my issues with
> IT> this thing.
>
> Can you post links to the online manuals for the drive and router.
> --
> You can't say civilizations don't advance, because they kill you in a
> new way in each war.
> ~ Will Rogers

Iced Tea
11-22-08, 12:11 PM
I will try the support tomorrow when I have plenty of time. If you think of
anything that I could try please let me know. Glad my problem created an
idea for you!!!

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gg9ems$nvc$1@news.motzarella.org...
> On 11/22/2008 05:42 AM, Iced Tea sent:
>> Not sure if I need to or not, I have a Linksys WRT54GL Wireless Router.
>>
>> On the expiration issue that is what I thought at first, I could reset
>> the
>> drive back to a DHCP and then look at the expiration and keep an eye on
>> it
>> to see if that is when the drive disappears from the network.
>>
>> I appreciate your help in trying to resolve my issues with this thing.
>>
>> Carl
>
> Hello Carl:
>
> I tried looking at the illustrations in the Linksys WRT54GL User Guide,
> but their on-line pdf does not work well with enlargement of its
> embedded images. I tried to see if the DHCP lease time could be set to
> some extremely large time value and I was also trying to see if the
> router /itself/ could declare some addresses as static.
>
> Ultimately, maybe you might need to contact Linksys/Cisco technical
> support. Your router may have had a firmware update issued earlier this
> year, and tech support may possibly ask you to verify that your firmware
> is the latest.
>
> It's a pleasure to help you. I've actually dreamed up an idea of trying
> to cascade my Linksys Gateway and my Linksys Router in my own SOHO
> installation. That came about during this thread. Thank YOU!
>
> Pete
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-23-08, 01:11 PM
Contact Linksys this morning and they had me change the IP address of the
NAS, to see if that would resolve the problem. The only other thing they
asked me to do is if the problem continued was to contact the NAS mfg and
see if certain ports need to be open or opened. Is there anything on my NIC
that would be causing the problem?

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gg9ems$nvc$1@news.motzarella.org...
> On 11/22/2008 05:42 AM, Iced Tea sent:
>> Not sure if I need to or not, I have a Linksys WRT54GL Wireless Router.
>>
>> On the expiration issue that is what I thought at first, I could reset
>> the
>> drive back to a DHCP and then look at the expiration and keep an eye on
>> it
>> to see if that is when the drive disappears from the network.
>>
>> I appreciate your help in trying to resolve my issues with this thing.
>>
>> Carl
>
> Hello Carl:
>
> I tried looking at the illustrations in the Linksys WRT54GL User Guide,
> but their on-line pdf does not work well with enlargement of its
> embedded images. I tried to see if the DHCP lease time could be set to
> some extremely large time value and I was also trying to see if the
> router /itself/ could declare some addresses as static.
>
> Ultimately, maybe you might need to contact Linksys/Cisco technical
> support. Your router may have had a firmware update issued earlier this
> year, and tech support may possibly ask you to verify that your firmware
> is the latest.
>
> It's a pleasure to help you. I've actually dreamed up an idea of trying
> to cascade my Linksys Gateway and my Linksys Router in my own SOHO
> installation. That came about during this thread. Thank YOU!
>
> Pete
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-25-08, 01:39 PM
On 11/23/2008 11:11 AM, Iced Tea sent:
> Contact Linksys this morning and they had me change the IP address of the
> NAS, to see if that would resolve the problem. The only other thing they
> asked me to do is if the problem continued was to contact the NAS mfg and
> see if certain ports need to be open or opened. Is there anything on my NIC
> that would be causing the problem?
>
> Carl
>
> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
> news:gg9ems$nvc$1@news.motzarella.org...
>> On 11/22/2008 05:42 AM, Iced Tea sent:
>>> Not sure if I need to or not, I have a Linksys WRT54GL Wireless Router.
>>>
>>> On the expiration issue that is what I thought at first, I could reset
>>> the
>>> drive back to a DHCP and then look at the expiration and keep an eye on
>>> it
>>> to see if that is when the drive disappears from the network.
>>>
>>> I appreciate your help in trying to resolve my issues with this thing.
>>>
>>> Carl
>> Hello Carl:
>>
>> I tried looking at the illustrations in the Linksys WRT54GL User Guide,
>> but their on-line pdf does not work well with enlargement of its
>> embedded images. I tried to see if the DHCP lease time could be set to
>> some extremely large time value and I was also trying to see if the
>> router /itself/ could declare some addresses as static.
>>
>> Ultimately, maybe you might need to contact Linksys/Cisco technical
>> support. Your router may have had a firmware update issued earlier this
>> year, and tech support may possibly ask you to verify that your firmware
>> is the latest.
>>
>> It's a pleasure to help you. I've actually dreamed up an idea of trying
>> to cascade my Linksys Gateway and my Linksys Router in my own SOHO
>> installation. That came about during this thread. Thank YOU!
>>
>> Pete
>> --
>> 1PW
>>
>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>
>

Hello Carl:

Through the top posting, snipping and days between replies, I have lost
sight of where you are now. If your network drive is still becoming
unavailable after nn hours, it may have been a dhcp lease expiration
issue. I believed you should set a static IP address in the network
drive and make an appropriate entry in the router.

This might probably involve disabling the dhcp server feature within the
router so that all devices served by your router would need static IP
addresses.

Where do you believe you are now? What do you believe is happening?

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Bob Fry
11-26-08, 09:19 AM
>>>>> "bar" == barcrnahgjuvfgyr <1PW> writes:
bar> I believed you should
bar> set a static IP address in the network drive and make an
bar> appropriate entry in the router.

bar> This might probably involve disabling the dhcp server feature
bar> within the router so that all devices served by your router
bar> would need static IP addresses.

Exactly. The OP has been given some odd and misleading advice in this
thread, but this post concisely states the problem and solution.
--
God favors no group. Only religions do that.
~ Bumper Sticker

Iced Tea
11-27-08, 10:08 AM
Good Morning, hope you are having or have a GREAT Thanksgiving!!!

While I am no further today in getting a stable connection on the NAS. I
have tried various things in the past couple of days and to no avail nothing
has worked.
For the most part,

1. I have finally got some better answers from Western Digital on the NAS.
Try another network/router (which I think was suggested here), also try
hooking the NAS directly to the NIC, plus some standard stuff which I had
already done, but with no change.

2. I tried the NAS at my brothers network (all dhcp, including when we
hooked the NAS up), The only difference was his router (D-Link DI-524) which
after 24 hours on the network, the NAS was still there!!! Yeah!!! Which
leads me to believe now that it is my router or my NIC (which is has onboard
LAN built into the motherboard, Intel DP35DP, Gigabit (10/100/1000
Mbits/sec) LAN subsystem using the IntelŪ 82566DC Gigabit Ethernet
Controller)

3. I connected the NAS directly to the NIC last night when I got home from
work and 10 hours later it is still visible and accessible on the network.
YEAH!!!

So this has now narrowed ot down to the router, BUT what? Linksys has asked
about specific ports needing to be opened to the drive. According to WD
(which they did include the ports) the ports only needed to be opened if you
used the Mionet software which enables you to access the NAS away from home.

At this point I am out of any ideas, as I am going to try and contact
Linksys support again and see what they can offer since I do have it
narrowed down to what seems to be the router. Everything on this computer
(with the exception of the tower and power supply are only a little over a 1
1/2 months old). I can't return anything to NewEgg where I bought everything
since they only have a 30 day return/refund exchange on most items. My
brother suggested just buying another router but unless I get the exact same
one he has, there is no gaurantee that I won't have the same issues with
another one (different brand or model).

Let me know if I have shed anything new on this issue since it now sounds as
though I have narrowed it down to the router. I will follow up here with
what I found out from Linksys.

Carl
"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gghk96$bqp$1@news.motzarella.org...
> On 11/23/2008 11:11 AM, Iced Tea sent:
>> Contact Linksys this morning and they had me change the IP address of the
>> NAS, to see if that would resolve the problem. The only other thing they
>> asked me to do is if the problem continued was to contact the NAS mfg and
>> see if certain ports need to be open or opened. Is there anything on my
>> NIC
>> that would be causing the problem?
>>
>> Carl
>>
>> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
>> news:gg9ems$nvc$1@news.motzarella.org...
>>> On 11/22/2008 05:42 AM, Iced Tea sent:
>>>> Not sure if I need to or not, I have a Linksys WRT54GL Wireless Router.
>>>>
>>>> On the expiration issue that is what I thought at first, I could reset
>>>> the
>>>> drive back to a DHCP and then look at the expiration and keep an eye on
>>>> it
>>>> to see if that is when the drive disappears from the network.
>>>>
>>>> I appreciate your help in trying to resolve my issues with this thing.
>>>>
>>>> Carl
>>> Hello Carl:
>>>
>>> I tried looking at the illustrations in the Linksys WRT54GL User Guide,
>>> but their on-line pdf does not work well with enlargement of its
>>> embedded images. I tried to see if the DHCP lease time could be set to
>>> some extremely large time value and I was also trying to see if the
>>> router /itself/ could declare some addresses as static.
>>>
>>> Ultimately, maybe you might need to contact Linksys/Cisco technical
>>> support. Your router may have had a firmware update issued earlier this
>>> year, and tech support may possibly ask you to verify that your firmware
>>> is the latest.
>>>
>>> It's a pleasure to help you. I've actually dreamed up an idea of trying
>>> to cascade my Linksys Gateway and my Linksys Router in my own SOHO
>>> installation. That came about during this thread. Thank YOU!
>>>
>>> Pete
>>> --
>>> 1PW
>>>
>>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>>
>>
>
> Hello Carl:
>
> Through the top posting, snipping and days between replies, I have lost
> sight of where you are now. If your network drive is still becoming
> unavailable after nn hours, it may have been a dhcp lease expiration
> issue. I believed you should set a static IP address in the network
> drive and make an appropriate entry in the router.
>
> This might probably involve disabling the dhcp server feature within the
> router so that all devices served by your router would need static IP
> addresses.
>
> Where do you believe you are now? What do you believe is happening?
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-27-08, 01:25 PM
On 11/27/2008 08:08 AM, Iced Tea sent:
> Good Morning, hope you are having or have a GREAT Thanksgiving!!!

....and to you Carl.

>
> While I am no further today in getting a stable connection on the NAS. I
> have tried various things in the past couple of days and to no avail nothing
> has worked.
> For the most part,
>
> 1. I have finally got some better answers from Western Digital on the NAS.
> Try another network/router (which I think was suggested here), also try
> hooking the NAS directly to the NIC, plus some standard stuff which I had
> already done, but with no change.
>
> 2. I tried the NAS at my brothers network (all dhcp, including when we
> hooked the NAS up), The only difference was his router (D-Link DI-524) which
> after 24 hours on the network, the NAS was still there!!! Yeah!!! Which
> leads me to believe now that it is my router or my NIC (which is has on board
> LAN built into the motherboard, Intel DP35DP, Gigabit (10/100/1000
> Mbits/sec) LAN subsystem using the IntelŪ 82566DC Gigabit Ethernet
> Controller)
>
> 3. I connected the NAS directly to the NIC last night when I got home from
> work and 10 hours later it is still visible and accessible on the network.
> YEAH!!!

Nice troubleshooting above. Good stuff!

>
> So this has now narrowed it down to the router, BUT what? Linksys has asked
> about specific ports needing to be opened to the drive. According to WD
> (which they did include the ports) the ports only needed to be opened if you
> used the Mionet software which enables you to access the NAS away from home.

This seems to have some significance. What port(s) would the NAS use
while receiving/sending files via backup and restore?

>
> At this point I am out of any ideas, as I am going to try and contact
> Linksys support again and see what they can offer since I do have it
> narrowed down to what seems to be the router. Everything on this computer
> (with the exception of the tower and power supply are only a little over a 1
> 1/2 months old). I can't return anything to NewEgg where I bought everything
> since they only have a 30 day return/refund exchange on most items. My
> brother suggested just buying another router but unless I get the exact same
> one he has, there is no guarantee that I won't have the same issues with
> another one (different brand or model).
>
> Let me know if I have shed anything new on this issue since it now sounds as
> though I have narrowed it down to the router. I will follow up here with
> what I found out from Linksys.
>
> Carl

Although I do note with interest that your NAS worked at your brother's,
even in a DHCP mode, I'd still like to see you set up a static IP
between your router and NAS. Even if this meant setting up static IPs
for everything you have.

You probably can't state how long the DHCP lease period was on your
brother's D-Link router. Might it have been set to more than 24 hours?

Did you ever make sure you had the latest firmware in your Linksys
router?

Have a nice Thanksgiving.

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-27-08, 08:48 PM
I did set a static IP on the NAS, I didn't have to set them for anything
else. Linksys walked me through the setup up. I had it set up like you had
setup before but the IP address of the NAS had to be changed from what you
had suggested, everything else was fine.

I know I don't have the latest firmware for my router. I did read through
what all the firmware fixes are and didn't see anything that pertained to my
problem but then again I am pretty dumb on the network issue.

You are correct on my brothers router, that I don't have an answer for the
DHCP lease period.



Carl


"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggms6t$s19$1@news.motzarella.org...
> On 11/27/2008 08:08 AM, Iced Tea sent:
>> Good Morning, hope you are having or have a GREAT Thanksgiving!!!
>
> ...and to you Carl.
>
>>
>> While I am no further today in getting a stable connection on the NAS. I
>> have tried various things in the past couple of days and to no avail
>> nothing
>> has worked.
>> For the most part,
>>
>> 1. I have finally got some better answers from Western Digital on the
>> NAS.
>> Try another network/router (which I think was suggested here), also try
>> hooking the NAS directly to the NIC, plus some standard stuff which I had
>> already done, but with no change.
>>
>> 2. I tried the NAS at my brothers network (all dhcp, including when we
>> hooked the NAS up), The only difference was his router (D-Link DI-524)
>> which
>> after 24 hours on the network, the NAS was still there!!! Yeah!!! Which
>> leads me to believe now that it is my router or my NIC (which is has on
>> board
>> LAN built into the motherboard, Intel DP35DP, Gigabit (10/100/1000
>> Mbits/sec) LAN subsystem using the IntelŪ 82566DC Gigabit Ethernet
>> Controller)
>>
>> 3. I connected the NAS directly to the NIC last night when I got home
>> from
>> work and 10 hours later it is still visible and accessible on the
>> network.
>> YEAH!!!
>
> Nice troubleshooting above. Good stuff!
>
>>
>> So this has now narrowed it down to the router, BUT what? Linksys has
>> asked
>> about specific ports needing to be opened to the drive. According to WD
>> (which they did include the ports) the ports only needed to be opened if
>> you
>> used the Mionet software which enables you to access the NAS away from
>> home.
>
> This seems to have some significance. What port(s) would the NAS use
> while receiving/sending files via backup and restore?
>
>>
>> At this point I am out of any ideas, as I am going to try and contact
>> Linksys support again and see what they can offer since I do have it
>> narrowed down to what seems to be the router. Everything on this computer
>> (with the exception of the tower and power supply are only a little over
>> a 1
>> 1/2 months old). I can't return anything to NewEgg where I bought
>> everything
>> since they only have a 30 day return/refund exchange on most items. My
>> brother suggested just buying another router but unless I get the exact
>> same
>> one he has, there is no guarantee that I won't have the same issues with
>> another one (different brand or model).
>>
>> Let me know if I have shed anything new on this issue since it now sounds
>> as
>> though I have narrowed it down to the router. I will follow up here with
>> what I found out from Linksys.
>>
>> Carl
>
> Although I do note with interest that your NAS worked at your brother's,
> even in a DHCP mode, I'd still like to see you set up a static IP
> between your router and NAS. Even if this meant setting up static IPs
> for everything you have.
>
> You probably can't state how long the DHCP lease period was on your
> brother's D-Link router. Might it have been set to more than 24 hours?
>
> Did you ever make sure you had the latest firmware in your Linksys
> router?
>
> Have a nice Thanksgiving.
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-27-08, 10:53 PM
On 11/27/2008 06:48 PM, Iced Tea sent:
> I did set a static IP on the NAS, I didn't have to set them for anything
> else. Linksys walked me through the setup up. I had it set up like you had
> setup before but the IP address of the NAS had to be changed from what you
> had suggested, everything else was fine.

I have a strong feeling that a static address in the NAS looking at a
similar static address in the router is the solution. However, read on.

>
> I know I don't have the latest firmware for my router. I did read through
> what all the firmware fixes are and didn't see anything that pertained to my
> problem but then again I am pretty dumb on the network issue.

It's just a fact of life that not everything is going to be revealed
when software is updated. Unless you have heard something to the
contrary, I would update the firmware, *soon*.

>
> You are correct on my brothers router, that I don't have an answer for the
> DHCP lease period.

This is a partial clue.

I wonder if Western Digital would enlighten us on as to what ports are
used with your NAS?

If you can find the place in your router where the DHCP lease time can
be adjusted, I would set it to some known larger value. If the NAS
failure coincides with the new setting, you know that a lease renewal
problem is at hand. Then, static addresses at both ends should solve
the trouble.

>
>
>
> Carl
>
>

I perceive some reluctance on your part to make static addresses at both
ends. Try the above first, then you probably have few choices left open
to you.

Good luck,

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-28-08, 08:03 AM
> I have a strong feeling that a static address in the NAS looking at a
> similar static address in the router is the solution. However, read on.

I had a static IP set up within the instructions that we had went over in
one of the above threads, I did chat with Linksys support and they only have
me change the static IP addess of the NAS. No changes made to the router
though. I was very clear in the chat about having the static IP on the NAS
and asked if anything needed to be changed on the router, which was an
answer of 'NO'

> It's just a fact of life that not everything is going to be revealed
> when software is updated. Unless you have heard something to the
> contrary, I would update the firmware, *soon*.

Going to do the firmware update today to see if that helps.

> I wonder if Western Digital would enlighten us on as to what ports are
> used with your NAS?

Western Digital did give me the ports that are used, but they said they are
only used by Mionet which is the software included with the NAS if you want
to access the NAS from a remote location. They say that the ports don't have
to be or need to be opened if the NAS is just used in a regular network
setup. I thought about trying them, opening ports is a whole new game for
me.

> If you can find the place in your router where the DHCP lease time can
> be adjusted.

I wish I would have checked my brothers but the clown can't remember is
ID/PW for the router and he didn't want to reset everything. I looked at all
the menus on mine and didn't see anything where you could change the lease
time.

> I perceive some reluctance on your part to make static addresses at both
> ends.

I will try anything just need set by set instructions, I did set the NAS to
a static IP but Linksys says nothing further needed to be done.

As always I am open to anything to try and get this resolved.

Thanks for all your help, I really do appreciate it.


"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggntg1$mm4$1@news.motzarella.org...
> On 11/27/2008 06:48 PM, Iced Tea sent:
>> I did set a static IP on the NAS, I didn't have to set them for anything
>> else. Linksys walked me through the setup up. I had it set up like you
>> had
>> setup before but the IP address of the NAS had to be changed from what
>> you
>> had suggested, everything else was fine.
>
> I have a strong feeling that a static address in the NAS looking at a
> similar static address in the router is the solution. However, read on.
>
>>
>> I know I don't have the latest firmware for my router. I did read through
>> what all the firmware fixes are and didn't see anything that pertained to
>> my
>> problem but then again I am pretty dumb on the network issue.
>
> It's just a fact of life that not everything is going to be revealed
> when software is updated. Unless you have heard something to the
> contrary, I would update the firmware, *soon*.
>
>>
>> You are correct on my brothers router, that I don't have an answer for
>> the
>> DHCP lease period.
>
> This is a partial clue.
>
> I wonder if Western Digital would enlighten us on as to what ports are
> used with your NAS?
>
> If you can find the place in your router where the DHCP lease time can
> be adjusted, I would set it to some known larger value. If the NAS
> failure coincides with the new setting, you know that a lease renewal
> problem is at hand. Then, static addresses at both ends should solve
> the trouble.
>
>>
>>
>>
>> Carl
>>
>>
>
> I perceive some reluctance on your part to make static addresses at both
> ends. Try the above first, then you probably have few choices left open
> to you.
>
> Good luck,
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-28-08, 11:04 AM
On 11/28/2008 06:03 AM, Iced Tea sent:
>> I have a strong feeling that a static address in the NAS looking at a
>> similar static address in the router is the solution. However, read on.
>
> I had a static IP set up within the instructions that we had went over in
> one of the above threads, I did chat with Linksys support and they only have
> me change the static IP addess of the NAS. No changes made to the router
> though. I was very clear in the chat about having the static IP on the NAS
> and asked if anything needed to be changed on the router, which was an
> answer of 'NO'
>
>> It's just a fact of life that not everything is going to be revealed
>> when software is updated. Unless you have heard something to the
>> contrary, I would update the firmware, *soon*.
>
> Going to do the firmware update today to see if that helps.
>
>> I wonder if Western Digital would enlighten us on as to what ports are
>> used with your NAS?
>
> Western Digital did give me the ports that are used, but they said they are
> only used by Mionet which is the software included with the NAS if you want
> to access the NAS from a remote location. They say that the ports don't have
> to be or need to be opened if the NAS is just used in a regular network
> setup. I thought about trying them, opening ports is a whole new game for
> me.

I'm fairly sure that your system(s) need to open (a) port(s) between
them and your NAS in order to make successful file transfers.

>
>> If you can find the place in your router where the DHCP lease time can
>> be adjusted.
>
> I wish I would have checked my brothers but the clown can't remember is
> ID/PW for the router and he didn't want to reset everything. I looked at all
> the menus on mine and didn't see anything where you could change the lease
> time.

*Client Lease Time.* Page 36 in your WRT54GL User Guide. However, this
is just a means to an end. If your failures coincide with DHCP lease
expiration time, then you know what action to take next.

>
>> I perceive some reluctance on your part to make static addresses at both
>> ends.
>
> I will try anything just need set by set instructions, I did set the NAS to
> a static IP but Linksys says nothing further needed to be done.

1.) One of my recent purchases was a Linksys WRT310N. This is a fairly
new product from Linksys. It's firmware did not have the latest version
as received. I updated with the latest firmware and I keep looking for
new releases.

2.) One of my systems runs Windows XP Pro (the devil made me do it) and
over the next several days, the Windows system would not have its lease
renewed. By the third day of this, I had enough. Static addresses took
care of that. My Linux system never had trouble with the lease renewal.

3.) Even the PC resident set-up software (LELA) was in need of update
right out of the box. I have updated it too.

Does any of this sound familiar Carl?

I've had another problem with my WRT310N. But this one's a design issue
and I have resolved that shortcoming for now.

>
> As always I am open to anything to try and get this resolved.
>
> Thanks for all your help, I really do appreciate it.
>

Another lease renewal solution might be better but I don't know what it
could be.

Think static Carl...

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Bob Fry
11-28-08, 01:52 PM
>>>>> "IT" == Iced Tea <icedteas@cox.net> writes:

>> I perceive some reluctance on your part to make static
>> addresses at both ends.

IT> I will try anything just need set by set instructions, I did
IT> set the NAS to a static IP but Linksys says nothing further
IT> needed to be done.

Linksys is wrong. At least they're wrong for your problem.

Dammit man, from the first reply to your post you've been told to use
static ports and turn off the DHCP, and it's been clear that has to be
done at both the NAS *and* router. But you haven't done it yet.
You've got several people trying to help you over several days--very
unusual in Usenet--but you follow a multitude of advice only part way.

Go to your router, RTFM, and use static ports. Geez.

--
If you are ever skydiving, and your parachute fails, and your
friends are all watching youu fall, I think a good gag would be
to pretend you're swimming.
- Jack Handey

GMAN
11-29-08, 12:57 AM
In article <dCzXk.4957$kn7.2824@newsfe08.iad>, "Iced Tea" <icedteas@cox.net> wrote:
>Good Morning, hope you are having or have a GREAT Thanksgiving!!!
>
>While I am no further today in getting a stable connection on the NAS. I
>have tried various things in the past couple of days and to no avail nothing
>has worked.
>For the most part,
>
>1. I have finally got some better answers from Western Digital on the NAS.
>Try another network/router (which I think was suggested here), also try
>hooking the NAS directly to the NIC, plus some standard stuff which I had
>already done, but with no change.
>
>2. I tried the NAS at my brothers network (all dhcp, including when we
>hooked the NAS up), The only difference was his router (D-Link DI-524) which
>after 24 hours on the network, the NAS was still there!!! Yeah!!! Which
>leads me to believe now that it is my router or my NIC (which is has onboard
>LAN built into the motherboard, Intel DP35DP, Gigabit (10/100/1000
>Mbits/sec) LAN subsystem using the IntelŪ 82566DC Gigabit Ethernet
>Controller)
>
>3. I connected the NAS directly to the NIC last night when I got home from
>work and 10 hours later it is still visible and accessible on the network.
>YEAH!!!
>
>So this has now narrowed ot down to the router, BUT what? Linksys has asked
>about specific ports needing to be opened to the drive. According to WD
>(which they did include the ports) the ports only needed to be opened if you
>used the Mionet software which enables you to access the NAS away from home.
>
>At this point I am out of any ideas, as I am going to try and contact
>Linksys support again and see what they can offer since I do have it
>narrowed down to what seems to be the router. Everything on this computer
>(with the exception of the tower and power supply are only a little over a 1
>1/2 months old). I can't return anything to NewEgg where I bought everything
>since they only have a 30 day return/refund exchange on most items. My
>brother suggested just buying another router but unless I get the exact same
>one he has, there is no gaurantee that I won't have the same issues with
>another one (different brand or model).
>
>Let me know if I have shed anything new on this issue since it now sounds as
>though I have narrowed it down to the router. I will follow up here with
>what I found out from Linksys.
>

Try downloading and flashing the latest firmware for your router.

Iced Tea
11-29-08, 03:47 AM
*Client Lease Time.* Page 36 in your WRT54GL User Guide.

Here is a link to the manual that I got from the site, and it only goes to
page 32:

http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02

Getting ready tu upgrade the firmware.

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggp8be$ms$1@news.motzarella.org...
> On 11/28/2008 06:03 AM, Iced Tea sent:
>>> I have a strong feeling that a static address in the NAS looking at a
>>> similar static address in the router is the solution. However, read on.
>>
>> I had a static IP set up within the instructions that we had went over in
>> one of the above threads, I did chat with Linksys support and they only
>> have
>> me change the static IP addess of the NAS. No changes made to the router
>> though. I was very clear in the chat about having the static IP on the
>> NAS
>> and asked if anything needed to be changed on the router, which was an
>> answer of 'NO'
>>
>>> It's just a fact of life that not everything is going to be revealed
>>> when software is updated. Unless you have heard something to the
>>> contrary, I would update the firmware, *soon*.
>>
>> Going to do the firmware update today to see if that helps.
>>
>>> I wonder if Western Digital would enlighten us on as to what ports are
>>> used with your NAS?
>>
>> Western Digital did give me the ports that are used, but they said they
>> are
>> only used by Mionet which is the software included with the NAS if you
>> want
>> to access the NAS from a remote location. They say that the ports don't
>> have
>> to be or need to be opened if the NAS is just used in a regular network
>> setup. I thought about trying them, opening ports is a whole new game for
>> me.
>
> I'm fairly sure that your system(s) need to open (a) port(s) between
> them and your NAS in order to make successful file transfers.
>
>>
>>> If you can find the place in your router where the DHCP lease time can
>>> be adjusted.
>>
>> I wish I would have checked my brothers but the clown can't remember is
>> ID/PW for the router and he didn't want to reset everything. I looked at
>> all
>> the menus on mine and didn't see anything where you could change the
>> lease
>> time.
>
> *Client Lease Time.* Page 36 in your WRT54GL User Guide. However, this
> is just a means to an end. If your failures coincide with DHCP lease
> expiration time, then you know what action to take next.
>
>>
>>> I perceive some reluctance on your part to make static addresses at both
>>> ends.
>>
>> I will try anything just need set by set instructions, I did set the NAS
>> to
>> a static IP but Linksys says nothing further needed to be done.
>
> 1.) One of my recent purchases was a Linksys WRT310N. This is a fairly
> new product from Linksys. It's firmware did not have the latest version
> as received. I updated with the latest firmware and I keep looking for
> new releases.
>
> 2.) One of my systems runs Windows XP Pro (the devil made me do it) and
> over the next several days, the Windows system would not have its lease
> renewed. By the third day of this, I had enough. Static addresses took
> care of that. My Linux system never had trouble with the lease renewal.
>
> 3.) Even the PC resident set-up software (LELA) was in need of update
> right out of the box. I have updated it too.
>
> Does any of this sound familiar Carl?
>
> I've had another problem with my WRT310N. But this one's a design issue
> and I have resolved that shortcoming for now.
>
>>
>> As always I am open to anything to try and get this resolved.
>>
>> Thanks for all your help, I really do appreciate it.
>>
>
> Another lease renewal solution might be better but I don't know what it
> could be.
>
> Think static Carl...
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-29-08, 04:11 AM
On 11/29/2008 01:47 AM, Iced Tea sent:
> *Client Lease Time.* Page 36 in your WRT54GL User Guide.
>
> Here is a link to the manual that I got from the site, and it only goes to
> page 32:
>
> http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02
>
> Getting ready to upgrade the firmware.

Hello Carl:

In the 32 page User Guide, it's on page 7. In the on-line 106 page User
Guide, it's on page 36.

<http://www-uk.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=UK%2FLayout&cid=1166859841350&packedargs=sku%3DWRT54GL&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4135041350B01&displaypage=download#versiondetail>

BTW - is your WRT54GL router hardware version 1.1?

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-29-08, 05:27 AM
Yes it is version 1.1 but when I go to the site and select all the proper
info it only shows version 1.0. If I follow your link I can get to the 1.1
stuff.

Carl
"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggr4gs$ab2$1@news.motzarella.org...
> On 11/29/2008 01:47 AM, Iced Tea sent:
>> *Client Lease Time.* Page 36 in your WRT54GL User Guide.
>>
>> Here is a link to the manual that I got from the site, and it only goes
>> to
>> page 32:
>>
>> http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02
>>
>> Getting ready to upgrade the firmware.
>
> Hello Carl:
>
> In the 32 page User Guide, it's on page 7. In the on-line 106 page User
> Guide, it's on page 36.
>
> <http://www-uk.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=UK%2FLayout&cid=1166859841350&packedargs=sku%3DWRT54GL&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4135041350B01&displaypage=download#versiondetail>
>
> BTW - is your WRT54GL router hardware version 1.1?
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-29-08, 05:29 AM
I see on the link you are on their UK site and I was in the US. I wonder why
Version 1.1 doesn't show up on the US site?

Carl
"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggr4gs$ab2$1@news.motzarella.org...
> On 11/29/2008 01:47 AM, Iced Tea sent:
>> *Client Lease Time.* Page 36 in your WRT54GL User Guide.
>>
>> Here is a link to the manual that I got from the site, and it only goes
>> to
>> page 32:
>>
>> http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02
>>
>> Getting ready to upgrade the firmware.
>
> Hello Carl:
>
> In the 32 page User Guide, it's on page 7. In the on-line 106 page User
> Guide, it's on page 36.
>
> <http://www-uk.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=UK%2FLayout&cid=1166859841350&packedargs=sku%3DWRT54GL&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4135041350B01&displaypage=download#versiondetail>
>
> BTW - is your WRT54GL router hardware version 1.1?
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-30-08, 11:57 AM
Upgraded the firmware and changed the DHCP Client Lease times and to no
avail no change. I an getting ready to make all IPs static and see where
that takes this issue. I have one question on my Laptop I have to TCP/IPs to
choose from. Version 4 and 6, do I need to set one of them or both?

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggr4gs$ab2$1@news.motzarella.org...
> On 11/29/2008 01:47 AM, Iced Tea sent:
>> *Client Lease Time.* Page 36 in your WRT54GL User Guide.
>>
>> Here is a link to the manual that I got from the site, and it only goes
>> to
>> page 32:
>>
>> http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02
>>
>> Getting ready to upgrade the firmware.
>
> Hello Carl:
>
> In the 32 page User Guide, it's on page 7. In the on-line 106 page User
> Guide, it's on page 36.
>
> <http://www-uk.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=UK%2FLayout&cid=1166859841350&packedargs=sku%3DWRT54GL&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4135041350B01&displaypage=download#versiondetail>
>
> BTW - is your WRT54GL router hardware version 1.1?
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-30-08, 02:03 PM
Will this affect when I use my laptop at wireless locations?

Carl

"Iced Tea" <icedteas@cox.net> wrote in message
news:auAYk.8379$1s7.4977@newsfe02.iad...
> Upgraded the firmware and changed the DHCP Client Lease times and to no
> avail no change. I an getting ready to make all IPs static and see where
> that takes this issue. I have one question on my Laptop I have to TCP/IPs
> to choose from. Version 4 and 6, do I need to set one of them or both?
>
> Carl
>
> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
> news:ggr4gs$ab2$1@news.motzarella.org...
>> On 11/29/2008 01:47 AM, Iced Tea sent:
>>> *Client Lease Time.* Page 36 in your WRT54GL User Guide.
>>>
>>> Here is a link to the manual that I got from the site, and it only goes
>>> to
>>> page 32:
>>>
>>> http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02
>>>
>>> Getting ready to upgrade the firmware.
>>
>> Hello Carl:
>>
>> In the 32 page User Guide, it's on page 7. In the on-line 106 page User
>> Guide, it's on page 36.
>>
>> <http://www-uk.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=UK%2FLayout&cid=1166859841350&packedargs=sku%3DWRT54GL&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4135041350B01&displaypage=download#versiondetail>
>>
>> BTW - is your WRT54GL router hardware version 1.1?
>>
>> Pete
>>
>> --
>> 1PW
>>
>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>
>

1PW
11-30-08, 02:38 PM
On 11/30/2008 09:57 AM, Iced Tea sent:
> Upgraded the firmware and changed the DHCP Client Lease times and to no
> avail no change. I am getting ready to make all IPs static and see where
> that takes this issue. I have one question on my Laptop I have to TCP/IPs to
> choose from. Version 4 and 6, do I need to set one of them or both?
>
> Carl

Hello Carl:

To answer your previous question - I don't know why the User Guide is on
their UK site. Perhaps the product was aimed at their European markets?

Did the DHCP Lease Time expirations coincide with the changed settings?

Your other issue probably has to do with IPv4 vs IPv6. When we say:
IPv4, we are using IP address notations like 192.168.1.101 and the same
address using an IPv6 notation is c0a8:165::. I would try only the IPv4
notation for now.

What firmware version does your WRT54GL have now?

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
11-30-08, 03:19 PM
DHCP Lease Time, it would only allow a numeric entry up 4 numbers. I even
set it to less time just to see what happened. Even at 5 minute intervals
there was no change, it didn't fail right away. It renewed with the same IP
and was still available. I left and came back about 9 hours later and the
NAS was inaccessible.

The router firmware upgrade went fine as far as I know, followed the
directions from the site. I now have version: 4.30.12.

Will be setting everything to static IPs tomorrow when I have a little more
time, so will let you know something tomorrow evening. Hopefully it will be
good news.

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:ggutji$sr0$1@news.motzarella.org...
> On 11/30/2008 09:57 AM, Iced Tea sent:
>> Upgraded the firmware and changed the DHCP Client Lease times and to no
>> avail no change. I am getting ready to make all IPs static and see where
>> that takes this issue. I have one question on my Laptop I have to TCP/IPs
>> to
>> choose from. Version 4 and 6, do I need to set one of them or both?
>>
>> Carl
>
> Hello Carl:
>
> To answer your previous question - I don't know why the User Guide is on
> their UK site. Perhaps the product was aimed at their European markets?
>
> Did the DHCP Lease Time expirations coincide with the changed settings?
>
> Your other issue probably has to do with IPv4 vs IPv6. When we say:
> IPv4, we are using IP address notations like 192.168.1.101 and the same
> address using an IPv6 notation is c0a8:165::. I would try only the IPv4
> notation for now.
>
> What firmware version does your WRT54GL have now?
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
11-30-08, 06:47 PM
On 11/30/2008 12:03 PM, Iced Tea sent:
> Will this affect when I use my laptop at wireless locations?
>
> Carl
>
> "Iced Tea" <icedteas@cox.net> wrote in message
> news:auAYk.8379$1s7.4977@newsfe02.iad...
>> Upgraded the firmware and changed the DHCP Client Lease times and to no
>> avail no change. I an getting ready to make all IPs static and see where
>> that takes this issue. I have one question on my Laptop I have to TCP/IPs
>> to choose from. Version 4 and 6, do I need to set one of them or both?
>>
>> Carl
>>
>> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
>> news:ggr4gs$ab2$1@news.motzarella.org...
>>> On 11/29/2008 01:47 AM, Iced Tea sent:
>>>> *Client Lease Time.* Page 36 in your WRT54GL User Guide.
>>>>
>>>> Here is a link to the manual that I got from the site, and it only goes
>>>> to
>>>> page 32:
>>>>
>>>> http://www.linksys.com/servlet/Satellite?blobcol=urldata&blobheadername1=Content-Type&blobheadername2=Content-Disposition&blobheadervalue1=application%2Fpdf&blobheadervalue2=inline%3B+filename%3DWRT54GL-V1.1_ug.pdf&blobkey=id&blobtable=MungoBlobs&blobwhere=1193787041094&ssbinary=true&lid=7719841350B02
>>>>
>>>> Getting ready to upgrade the firmware.
>>> Hello Carl:
>>>
>>> In the 32 page User Guide, it's on page 7. In the on-line 106 page User
>>> Guide, it's on page 36.
>>>
>>> <http://www-uk.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=UK%2FLayout&cid=1166859841350&packedargs=sku%3DWRT54GL&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4135041350B01&displaypage=download#versiondetail>
>>>
>>> BTW - is your WRT54GL router hardware version 1.1?
>>>
>>> Pete
>>>
>>> --
>>> 1PW
>>>
>>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>>
>
>

Hello Carl:

I apologize, but the top posting has confused me again.

Perhaps you could bottom post and re-ask your question more completely.

I'm sorry.

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
12-01-08, 07:16 AM
DHCP Lease Time, it would only allow a numeric entry up 4 numbers. I even
set it to less time just to see what happened. Even at 5 minute intervals
there was no change, it didn't fail right away. It renewed with the same IP
and was still available. I left and came back about 9 hours later and the
NAS was inaccessible.

The router firmware upgrade went fine as far as I know, followed the
directions from the site. I now have version: 4.30.12.

Will be setting everything to static IPs tomorrow when I have a little more
time, so will let you know something tomorrow evening. Hopefully it will be
good news.

Carl

"Iced Tea" <icedteas@cox.net> wrote in message
news:gEyRk.5952$ih7.1486@newsfe01.iad...
>I have a Linksys WRT54GL Wireless Router on my network and a Western
>Digital My Book World Edition 1TB Network Drive. For some reason after
>several hours (haven't timed it so I don't actually know how long)on the
>network the WD Network drive becomes inaccessible. I sent back the first
>drive and got another one brand new right out of the box and I have the
>same issues.
>
> Contacted WD Supprt and so far no success on the problem as to why this
> happens. the only way that I can get then network to see the drive again
> is to unplug the power from the back of the WD Network drive. I have an HP
> Officejet that is on the network and I don't have any problems with it.
>
> Anyone familiar with the router and network drive I have? Will taking any
> help at this point.
>
>
>

Iced Tea
12-02-08, 08:56 AM
I have switched everything iver to static IPs on my network a little while
ago. Both my desktop and laptop, my network printer and my NAS.

In the 'Setup' under 'Basic Setup' I did change mt internet connection type
to a static IP, but I am not sure if I need to do that or not. I know I have
searched and I have found that all IPs for my ISP are DHCP and that if you
need a static IP you must call.

So do I need to switch that part back?

In the 'Network Setup' I disabled the DHCP Server, I guess that was all I
needed to do on the router other than the change I made above.

I can access the printer and the NAS with the new IPs so I guess all is
working and I have internet access on both computers.

Let me know if I missed something and I will give an update later this
evening, to let everyone know if the static IPs worked for the keeping the
NAS 'alive' on the network.

Carl

"Iced Tea" <icedteas@cox.net> wrote in message
news:gEyRk.5952$ih7.1486@newsfe01.iad...
>I have a Linksys WRT54GL Wireless Router on my network and a Western
>Digital My Book World Edition 1TB Network Drive. For some reason after
>several hours (haven't timed it so I don't actually know how long)on the
>network the WD Network drive becomes inaccessible. I sent back the first
>drive and got another one brand new right out of the box and I have the
>same issues.
>
> Contacted WD Supprt and so far no success on the problem as to why this
> happens. the only way that I can get then network to see the drive again
> is to unplug the power from the back of the WD Network drive. I have an HP
> Officejet that is on the network and I don't have any problems with it.
>
> Anyone familiar with the router and network drive I have? Will taking any
> help at this point.
>
>
>

1PW
12-02-08, 01:26 PM
On 12/02/2008 06:56 AM, Iced Tea sent:
> I have switched everything over to static IPs on my network a little while
> ago. Both my desktop and laptop, my network printer and my NAS.
>
> In the 'Setup' under 'Basic Setup' I did change mt internet connection type
> to a static IP, but I am not sure if I need to do that or not. I know I have
> searched and I have found that all IPs for my ISP are DHCP and that if you
> need a static IP you must call.
>
> So do I need to switch that part back?
>
> In the 'Network Setup' I disabled the DHCP Server, I guess that was all I
> needed to do on the router other than the change I made above.
>
> I can access the printer and the NAS with the new IPs so I guess all is
> working and I have internet access on both computers.
>
> Let me know if I missed something and I will give an update later this
> evening, to let everyone know if the static IPs worked for the keeping the
> NAS 'alive' on the network.
>
> Carl
>
> "Iced Tea" <icedteas@cox.net> wrote in message
> news:gEyRk.5952$ih7.1486@newsfe01.iad...
>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>> Digital My Book World Edition 1TB Network Drive. For some reason after
>> several hours (haven't timed it so I don't actually know how long)on the
>> network the WD Network drive becomes inaccessible. I sent back the first
>> drive and got another one brand new right out of the box and I have the
>> same issues.
>>
>> Contacted WD Support and so far no success on the problem as to why this
>> happens. the only way that I can get then network to see the drive again
>> is to unplug the power from the back of the WD Network drive. I have an HP
>> OfficeJet that is on the network and I don't have any problems with it.
>>
>> Anyone familiar with the router and network drive I have? Will taking any
>> help at this point.

Hello Carl:

If cox.net is like my own ISP, your IP address, from them, will probably
go unchanged unless something changes a MAC address that they 'see'.
However, leaving the "Internet" side of your router in static would be
just fine. Requesting a static IP from your ISP might engender needless
fees to be paid to them. Do make a note to yourself though, that the
Cox DHCP server /could/ change your IP address from them without warning.

For a period of about a week then, please leave *everything* in static.
This will remove any suspicions, for that period, with regard to your
NAS and DHCP lease expiration. Please let us know how things progress.

Thank you.

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
12-03-08, 09:21 AM
Well the static IPs on everything didn't seem to fix the issue. Port light
on the router still continues to blink steadily when the connection becomes
in accessible. It is still in an unspecified amount of time this happens and
on occasion right after I manually reset the NAS. I don't get the same error
as I did when the NAS loses the network connection. I now get the following
when I try to access it:

An error occurred while reconnecting Z: to \\Mybookworld\public.

Microsoft Windows Network: The local device name is already in use.

This connection has not been restored.


I am going to set the router back to DHCP for my internet connection as this
morning it seems very slow. I am counting on you guys for some assistance on
where to look now. A few thing sthat have comes to mind but at this point I
am just grasping for straws.

#1 Problem with the network setup in Windows XP Home?
#2 Could my McAfee Sercurity Suite be causing a problem?
#3 Windows XP Home?

When I checked the NAS at my brother's last week he did in fact have a
different router and then he also runs Windows Vista (not sure which version
though).

I think I have everything set correctly, let me know if there is anything I
should double check or anything I can look into further.

Carl
"Iced Tea" <icedteas@cox.net> wrote in message
news:gEyRk.5952$ih7.1486@newsfe01.iad...
>I have a Linksys WRT54GL Wireless Router on my network and a Western
>Digital My Book World Edition 1TB Network Drive. For some reason after
>several hours (haven't timed it so I don't actually know how long)on the
>network the WD Network drive becomes inaccessible. I sent back the first
>drive and got another one brand new right out of the box and I have the
>same issues.
>
> Contacted WD Supprt and so far no success on the problem as to why this
> happens. the only way that I can get then network to see the drive again
> is to unplug the power from the back of the WD Network drive. I have an HP
> Officejet that is on the network and I don't have any problems with it.
>
> Anyone familiar with the router and network drive I have? Will taking any
> help at this point.
>
>
>

Bill
12-03-08, 10:21 AM
Sounds like the drive bios settings are causing your problems.
Wonder if you removed the drive from the enclosure, and put it in a PC, and
changed the drive bios settings?

I had to do that with a 2.5 drive to get it to work in a USB enclosure.

> My Book World Edition 1TB Network Drive. For some reason after several
> hours (haven't timed it so I don't actually know how long)on the network
> the WD Network drive becomes inaccessible.

1PW
12-04-08, 08:04 PM
On 12/03/2008 07:21 AM, Iced Tea sent:
> Well the static IPs on everything didn't seem to fix the issue. Port light
> on the router still continues to blink steadily when the connection becomes
> in accessible. It is still in an unspecified amount of time this happens and
> on occasion right after I manually reset the NAS. I don't get the same error
> as I did when the NAS loses the network connection. I now get the following
> when I try to access it:
>
> An error occurred while reconnecting Z: to \\Mybookworld\public.
>
> Microsoft Windows Network: The local device name is already in use.
>
> This connection has not been restored.
>
>
> I am going to set the router back to DHCP for my internet connection as this
> morning it seems very slow. I am counting on you guys for some assistance on
> where to look now. A few thing sthat have comes to mind but at this point I
> am just grasping for straws.
>
> #1 Problem with the network setup in Windows XP Home?
> #2 Could my McAfee Sercurity Suite be causing a problem?
> #3 Windows XP Home?
>
> When I checked the NAS at my brother's last week he did in fact have a
> different router and then he also runs Windows Vista (not sure which version
> though).
>
> I think I have everything set correctly, let me know if there is anything I
> should double check or anything I can look into further.
>
> Carl
> "Iced Tea" <icedteas@cox.net> wrote in message
> news:gEyRk.5952$ih7.1486@newsfe01.iad...
>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>> Digital My Book World Edition 1TB Network Drive. For some reason after
>> several hours (haven't timed it so I don't actually know how long)on the
>> network the WD Network drive becomes inaccessible. I sent back the first
>> drive and got another one brand new right out of the box and I have the
>> same issues.
>>
>> Contacted WD Supprt and so far no success on the problem as to why this
>> happens. the only way that I can get then network to see the drive again
>> is to unplug the power from the back of the WD Network drive. I have an HP
>> Officejet that is on the network and I don't have any problems with it.
>>
>> Anyone familiar with the router and network drive I have? Will taking any
>> help at this point.
>>
>>
>>
>
>
Hello Carl:

At this point, I too am out of ideas. Maybe a refund from Western
Digital to be used on another similar product is in order.

Was this unit ever replaced in-warranty. Sorry if you told us before.

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
12-04-08, 08:51 PM
Yes, but not from WD from NewEgg as the it was in the first 30 days. Now any
type of replacement must be made from WD. I have my uncle and my nephew
sniffing it out to see if they can come up with anything. My uncle told me
my nephew is a network expert as has set up many around town for residences
and business. The only draw back is that they won't be here for a couple of
weeks. It worked on my brothers network with his D-Link router. I know at
this point before I shell out $80. (that is what the cost of the router my
brother has) I know I would want to hook it up on my network first. Will
post any further findings here.

Again thanks for you help and everyone else that has contributed!!!

Carl

"1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
news:gha27j$il9$1@news.motzarella.org...
> On 12/03/2008 07:21 AM, Iced Tea sent:
>> Well the static IPs on everything didn't seem to fix the issue. Port
>> light
>> on the router still continues to blink steadily when the connection
>> becomes
>> in accessible. It is still in an unspecified amount of time this happens
>> and
>> on occasion right after I manually reset the NAS. I don't get the same
>> error
>> as I did when the NAS loses the network connection. I now get the
>> following
>> when I try to access it:
>>
>> An error occurred while reconnecting Z: to \\Mybookworld\public.
>>
>> Microsoft Windows Network: The local device name is already in use.
>>
>> This connection has not been restored.
>>
>>
>> I am going to set the router back to DHCP for my internet connection as
>> this
>> morning it seems very slow. I am counting on you guys for some assistance
>> on
>> where to look now. A few thing sthat have comes to mind but at this point
>> I
>> am just grasping for straws.
>>
>> #1 Problem with the network setup in Windows XP Home?
>> #2 Could my McAfee Sercurity Suite be causing a problem?
>> #3 Windows XP Home?
>>
>> When I checked the NAS at my brother's last week he did in fact have a
>> different router and then he also runs Windows Vista (not sure which
>> version
>> though).
>>
>> I think I have everything set correctly, let me know if there is anything
>> I
>> should double check or anything I can look into further.
>>
>> Carl
>> "Iced Tea" <icedteas@cox.net> wrote in message
>> news:gEyRk.5952$ih7.1486@newsfe01.iad...
>>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>>> Digital My Book World Edition 1TB Network Drive. For some reason after
>>> several hours (haven't timed it so I don't actually know how long)on the
>>> network the WD Network drive becomes inaccessible. I sent back the first
>>> drive and got another one brand new right out of the box and I have the
>>> same issues.
>>>
>>> Contacted WD Supprt and so far no success on the problem as to why this
>>> happens. the only way that I can get then network to see the drive again
>>> is to unplug the power from the back of the WD Network drive. I have an
>>> HP
>>> Officejet that is on the network and I don't have any problems with it.
>>>
>>> Anyone familiar with the router and network drive I have? Will taking
>>> any
>>> help at this point.
>>>
>>>
>>>
>>
>>
> Hello Carl:
>
> At this point, I too am out of ideas. Maybe a refund from Western
> Digital to be used on another similar product is in order.
>
> Was this unit ever replaced in-warranty. Sorry if you told us before.
>
> Pete
>
> --
> 1PW
>
> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

1PW
12-04-08, 11:46 PM
On 12/04/2008 06:51 PM, Iced Tea sent:
> Yes, but not from WD from NewEgg as the it was in the first 30 days. Now any
> type of replacement must be made from WD. I have my uncle and my nephew
> sniffing it out to see if they can come up with anything. My uncle told me
> my nephew is a network expert as has set up many around town for residences
> and business. The only draw back is that they won't be here for a couple of
> weeks. It worked on my brothers network with his D-Link router. I know at
> this point before I shell out $80. (that is what the cost of the router my
> brother has) I know I would want to hook it up on my network first. Will
> post any further findings here.
>
> Again thanks for you help and everyone else that has contributed!!!
>
> Carl
>
> "1PW" <barcrnahgjuvfgyr@nby.pbz> wrote in message
> news:gha27j$il9$1@news.motzarella.org...
>> On 12/03/2008 07:21 AM, Iced Tea sent:
>>> Well the static IPs on everything didn't seem to fix the issue. Port
>>> light
>>> on the router still continues to blink steadily when the connection
>>> becomes
>>> in accessible. It is still in an unspecified amount of time this happens
>>> and
>>> on occasion right after I manually reset the NAS. I don't get the same
>>> error
>>> as I did when the NAS loses the network connection. I now get the
>>> following
>>> when I try to access it:
>>>
>>> An error occurred while reconnecting Z: to \\Mybookworld\public.
>>>
>>> Microsoft Windows Network: The local device name is already in use.
>>>
>>> This connection has not been restored.
>>>
>>>
>>> I am going to set the router back to DHCP for my internet connection as
>>> this
>>> morning it seems very slow. I am counting on you guys for some assistance
>>> on
>>> where to look now. A few thing sthat have comes to mind but at this point
>>> I
>>> am just grasping for straws.
>>>
>>> #1 Problem with the network setup in Windows XP Home?
>>> #2 Could my McAfee Sercurity Suite be causing a problem?
>>> #3 Windows XP Home?
>>>
>>> When I checked the NAS at my brother's last week he did in fact have a
>>> different router and then he also runs Windows Vista (not sure which
>>> version
>>> though).
>>>
>>> I think I have everything set correctly, let me know if there is anything
>>> I
>>> should double check or anything I can look into further.
>>>
>>> Carl
>>> "Iced Tea" <icedteas@cox.net> wrote in message
>>> news:gEyRk.5952$ih7.1486@newsfe01.iad...
>>>> I have a Linksys WRT54GL Wireless Router on my network and a Western
>>>> Digital My Book World Edition 1TB Network Drive. For some reason after
>>>> several hours (haven't timed it so I don't actually know how long)on the
>>>> network the WD Network drive becomes inaccessible. I sent back the first
>>>> drive and got another one brand new right out of the box and I have the
>>>> same issues.
>>>>
>>>> Contacted WD Supprt and so far no success on the problem as to why this
>>>> happens. the only way that I can get then network to see the drive again
>>>> is to unplug the power from the back of the WD Network drive. I have an
>>>> HP
>>>> Officejet that is on the network and I don't have any problems with it.
>>>>
>>>> Anyone familiar with the router and network drive I have? Will taking
>>>> any
>>>> help at this point.
>>>>
>>>>
>>>>
>>>
>> Hello Carl:
>>
>> At this point, I too am out of ideas. Maybe a refund from Western
>> Digital to be used on another similar product is in order.
>>
>> Was this unit ever replaced in-warranty. Sorry if you told us before.
>>
>> Pete
>>
>> --
>> 1PW
>>
>> @?6A62?FEH9:DE=6o2@=]4@> [r4o7t]
>
>

Hello Carl:

Would you and your brother like to make a permanent exchange routers?

Pete

--
1PW

@?6A62?FEH9:DE=6o2@=]4@> [r4o7t]

Iced Tea
12-13-08, 02:30 AM
My cousin who is very network savvy came over to take a gander at all this
mess and couldn't find anything wrong. He said it is probably that 1 in a
million chance the the NAS and router just don't like each other. I did ask
him about adding another network card to the computer itself so I could hook
the NAS up directly. When I hooked the NAS up directly to the NIC card it
never lost the connection. So with that said I guess I am going to try and
get a network card today and see what happens.

Anybody reccommend a particular NIC? I am a little hesitant about buying a
Linksys card since I had a problem with the router.

Carl

"Iced Tea" <icedteas@cox.net> wrote in message
news:gEyRk.5952$ih7.1486@newsfe01.iad...
>I have a Linksys WRT54GL Wireless Router on my network and a Western
>Digital My Book World Edition 1TB Network Drive. For some reason after
>several hours (haven't timed it so I don't actually know how long)on the
>network the WD Network drive becomes inaccessible. I sent back the first
>drive and got another one brand new right out of the box and I have the
>same issues.
>
> Contacted WD Supprt and so far no success on the problem as to why this
> happens. the only way that I can get then network to see the drive again
> is to unplug the power from the back of the WD Network drive. I have an HP
> Officejet that is on the network and I don't have any problems with it.
>
> Anyone familiar with the router and network drive I have? Will taking any
> help at this point.
>
>
>

Iced Tea
12-14-08, 09:04 AM
I picked up an NIC today and have it installed (with a static IP). The NAS
works like a champ and has been online with my deskstop for over 12 hours.

Now mt next question(s) is it possible to be able to set this up so my
entire network can see and have access to the NAS?

Carl

"Iced Tea" <icedteas@cox.net> wrote in message
news:gEyRk.5952$ih7.1486@newsfe01.iad...
>I have a Linksys WRT54GL Wireless Router on my network and a Western
>Digital My Book World Edition 1TB Network Drive. For some reason after
>several hours (haven't timed it so I don't actually know how long)on the
>network the WD Network drive becomes inaccessible. I sent back the first
>drive and got another one brand new right out of the box and I have the
>same issues.
>
> Contacted WD Supprt and so far no success on the problem as to why this
> happens. the only way that I can get then network to see the drive again
> is to unplug the power from the back of the WD Network drive. I have an HP
> Officejet that is on the network and I don't have any problems with it.
>
> Anyone familiar with the router and network drive I have? Will taking any
> help at this point.
>
>
>