I am at my wit's end right now, so I'm tossing this up for anyone to take a shot...
I just reconfigured my cable router at my new house as a pass-through device in order to allow my Airport Extreme to handle the DHCP duties. However, in my haste to do so, I forgot that my Drobo FS has a fixed IP address that I set some time ago when I was using the cable router's DHCP server.
The problem is that the cable router's DHCP server used a 192.168.0.x range, while my AE uses a 10 dot range.
As a result, my Drobo is no longer visible, nor can I connect to it. And no, I don't recall what the static IP address was that I set for it in the "old" range, which is the rub.
I tried connecting to it over ethernet directly with my MBP and multicasting using the 224.0.0.1 range, which has worked for me in the past. Unfortunately, using Netstat to do this yielded nothing.
I could reconfigure everything back to the old range to be able to once again connect to the Drobo FS and recover the IP address, but I would rather not.
Any suggestions for identifying the IP of the Drobo, or what I may be doing wrong?
It's late, I'm frustrated and punchy, so rather than continue to struggle with this I'm calling it a night and hoping I'll have a resolution in the morning.
Thanks in advance to anyone who can help.
MacDann
I just reconfigured my cable router at my new house as a pass-through device in order to allow my Airport Extreme to handle the DHCP duties. However, in my haste to do so, I forgot that my Drobo FS has a fixed IP address that I set some time ago when I was using the cable router's DHCP server.
The problem is that the cable router's DHCP server used a 192.168.0.x range, while my AE uses a 10 dot range.
As a result, my Drobo is no longer visible, nor can I connect to it. And no, I don't recall what the static IP address was that I set for it in the "old" range, which is the rub.
I tried connecting to it over ethernet directly with my MBP and multicasting using the 224.0.0.1 range, which has worked for me in the past. Unfortunately, using Netstat to do this yielded nothing.
I could reconfigure everything back to the old range to be able to once again connect to the Drobo FS and recover the IP address, but I would rather not.
Any suggestions for identifying the IP of the Drobo, or what I may be doing wrong?
It's late, I'm frustrated and punchy, so rather than continue to struggle with this I'm calling it a night and hoping I'll have a resolution in the morning.
Thanks in advance to anyone who can help.
MacDann