500GB Drive on WLAN; access thru workgroup and domain?

Hello all!

I have the following setup:

1. A TeleWell TW-EA510 ADSL modem/router is connected to a 2MBit line
to the Internet.

2. Two laptops use this Internet connection and WLAN network with no
problems.

3. I installed a Western Digital 500GB My Book World Edition drive to
the ADSL router. It picked up an IP with no troubles, becoming
192.168.0.100 on the WLAN.

4. The home laptop, running XP Home, is part of a workgroup, sees the
drive, and allows to map it to a drive letter.

5. The work laptop, part of a domain for office use, sees the WD drive
management tool at http://192.168.0.100, can change properties on it,
but cannot access the drive itself for file management.

Now, my question: How can I make the drive fully accessible to the
laptop on the domain? Is it a question of how the WLAN is set up, or
do I have to come out of the domain and into a workgroup (very nasty)
to access the disk?

Thank you for any leads!

usenetfan@hotmail.com wrote:
> Hello all!
>
> I have the following setup:
>
> 1. A TeleWell TW-EA510 ADSL modem/router is connected to a 2MBit line
> to the Internet.
>
> 2. Two laptops use this Internet connection and WLAN network with no
> problems.
>
> 3. I installed a Western Digital 500GB My Book World Edition drive to
> the ADSL router. It picked up an IP with no troubles, becoming
> 192.168.0.100 on the WLAN.
>
> 4. The home laptop, running XP Home, is part of a workgroup, sees the
> drive, and allows to map it to a drive letter.
>
> 5. The work laptop, part of a domain for office use, sees the WD drive
> management tool at http://192.168.0.100, can change properties on it,
> but cannot access the drive itself for file management.
>
> Now, my question: How can I make the drive fully accessible to the
> laptop on the domain? Is it a question of how the WLAN is set up, or
> do I have to come out of the domain and into a workgroup (very nasty)
> to access the disk?
>
> Thank you for any leads!

Actually, it's easy, if the hd is offering a share. (Works for me in
similar situation.)

On work laptop, @ shell: "net view \\192.168.0.100" You'll see non-admin
shares. Try something like "net use l: \\192.168.0.100\<share-name>"
where <share-name> is maybe c$, or whatever else partition is shared as.
(c$ is admin-share name for boot-partition.) This is standard Windows
netbios client/server stuff.

John

usenetfan@hotmail.com wrote:
> Hello all!
>
> I have the following setup:
>
> 1. A TeleWell TW-EA510 ADSL modem/router is connected to a 2MBit line
> to the Internet.
>
> 2. Two laptops use this Internet connection and WLAN network with no
> problems.
>
> 3. I installed a Western Digital 500GB My Book World Edition drive to
> the ADSL router. It picked up an IP with no troubles, becoming
> 192.168.0.100 on the WLAN.
>
> 4. The home laptop, running XP Home, is part of a workgroup, sees the
> drive, and allows to map it to a drive letter.
>
> 5. The work laptop, part of a domain for office use, sees the WD drive
> management tool at http://192.168.0.100, can change properties on it,
> but cannot access the drive itself for file management.
>
> Now, my question: How can I make the drive fully accessible to the
> laptop on the domain? Is it a question of how the WLAN is set up, or
> do I have to come out of the domain and into a workgroup (very nasty)
> to access the disk?
>
> Thank you for any leads!

Not sure how the software is set or how you use it, my nas has an ethernet
connection, and when plugged into the router it's just a general share with
anyone on the network, but if I plug it directly into the 'puter, it's set
as an exclusive control, and i can only do maint stuff when it's set for
exclusive... Sounds like you may have it set for a general sharing rather
than exclusive control (course then you can't share it till you set it back)

usenetfan@hotmail.com wrote:
> Hello all!
>
> I have the following setup:
>
> 1. A TeleWell TW-EA510 ADSL modem/router is connected to a 2MBit line
> to the Internet.
>
> 2. Two laptops use this Internet connection and WLAN network with no
> problems.
>
> 3. I installed a Western Digital 500GB My Book World Edition drive to
> the ADSL router. It picked up an IP with no troubles, becoming
> 192.168.0.100 on the WLAN.
>
> 4. The home laptop, running XP Home, is part of a workgroup, sees the
> drive, and allows to map it to a drive letter.
>
> 5. The work laptop, part of a domain for office use, sees the WD drive
> management tool at http://192.168.0.100, can change properties on it,
> but cannot access the drive itself for file management.
>
> Now, my question: How can I make the drive fully accessible to the
> laptop on the domain? Is it a question of how the WLAN is set up, or
> do I have to come out of the domain and into a workgroup (very nasty)
> to access the disk?
>
> Thank you for any leads!
Are you using the "WD Anywhere Access" s'ware on both machines?
Have you tried setting the share so it can be accessed without using "WD
Anywhere Access"?
<http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1531&p_created=1176311730&p_si d=wdh-ChTi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9 zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jb nQ9MjE3LDIxNyZwX3Byb2RzPTIwOSwyMjEmcF9jYXRzPTAmcF9 wdj0yLjIyMSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc 2VhcmNoX2ZubCZwX3BhZ2U9MQ**&p_li=&p_topview=1>
I have been put off these drives because of the recent inclusion of
"drm" style management in the "WD Anywhere Access" s'ware.
<http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1495&p_created=1168641440&p_si d=2WC7BhTi&p_accessibility=0&p_redirect=&p_lva=&p_ sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3J vd19jbnQ9NzYsNzYmcF9wcm9kcz0yMDksMjIxJnBfY2F0cz0xM zAmcF9wdj0yLjIyMSZwX2N2PTEuMTMwJnBfc2VhcmNoX3R5cGU 9YW5zd2Vycy5zZWFyY2hfZm5sJnBfcGFnZT0x&p_li=&p_topv iew=1>

Hello all again, and thanks already. Here's a dump of what I get whet
I use the commands you suggested:

************************************************** **********************

C:\Documents and Settings\hh>net view \\192.168.0.100
System error 53 has occurred.

The network path was not found.


C:\Documents and Settings\heikki.hietala>ping 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Reply from 192.168.0.100: bytes=32 time=2ms TTL=64
Reply from 192.168.0.100: bytes=32 time=1ms TTL=64
Reply from 192.168.0.100: bytes=32 time=1ms TTL=64
Reply from 192.168.0.100: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Documents and Settings\hh>net view \\192.168.0.100\c$
System error 123 has occurred.

The filename, directory name, or volume label syntax is incorrect.


C:\Documents and Settings\hh>net view \\192.168.0.100\public
System error 123 has occurred.

The filename, directory name, or volume label syntax is incorrect.


C:\Documents and Settings\hh>net use I: \\192.168.0.100\vintti
System error 53 has occurred.

The network path was not foun

************************************************
So it pings and responds. And when I use the http://192.168.0.100
address in a browser, I see the drive management software and can
create shares etc. It's just getting them into use that sucks at the
moment. I wonder if that's a problem with my WLAN Settings? I have
turned on MS File and printer sharing etc. so that my domain and
workgroup computers have the same options turned on.

Thanks again!

Ahh one more thing, I have not installed the WD Access thing on the
home (workgroup) computer, and yet it contacts the drive - no problem.
It's the domain machine (with WD installed and removed) that doesn't.

Hello all again, and thanks already. Here's a dump of what I get whet
I use the commands you suggested:

************************************************** **********************

C:\Documents and Settings\hh>net view \\192.168.0.100
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\hh>ping 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Reply from 192.168.0.100: bytes=32 time=2ms TTL=64
Reply from 192.168.0.100: bytes=32 time=1ms TTL=64
Reply from 192.168.0.100: bytes=32 time=1ms TTL=64
Reply from 192.168.0.100: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Documents and Settings\hh>net view \\192.168.0.100\c$
System error 123 has occurred.

The filename, directory name, or volume label syntax is incorrect.

C:\Documents and Settings\hh>net view \\192.168.0.100\public
System error 123 has occurred.

The filename, directory name, or volume label syntax is incorrect.

C:\Documents and Settings\hh>net use I: \\192.168.0.100\vintti
System error 53 has occurred.

The network path was not found

************************************************
So it pings and responds. And when I use the http://192.168.0.100
address in a browser, I see the drive management software and can
create shares etc. It's just getting them into use that sucks at the
moment. I wonder if that's a problem with my WLAN Settings? I have
turned on MS File and printer sharing etc. so that my domain and
workgroup computers have the same options turned on.

Thanks again!

what are the operating systems involved ?

I have a Maxtor NAS, and it works fine with Win98se and XP,
but has a problem with Vista because of the way Vista attempts to authenticate
with the NAS.
There was a setting I could change in Vista, but don't recall right now.

The NAS uses the Samba software to create the file shares,
and the newer Vista authentication is a problem with Samba,
therefore you can see and touch it via IP, just not get into it via Windows
Sharing.

here's a link for a basic info discussion on potential probs
with Vista (if that's the OS involved on the domain computer)
and connecting to NAS type devices.... like MAC or Samba-based NAS drives

<http://aspadvice.com/blogs/ssmith/ar...k-Connection-I
ssue-Solved.aspx>

Ahh, sorry for omitting such a vital piece of info. The one that
reaches the drive is XP Home and the one that does not is XP Pro. The
drive itself is reputedly some Linux-based disk OS.

On 17 joulu, 08:11, usenetfan <usenet...@hotmail.com> wrote:
> Ahh, sorry for omitting such a vital piece of info. The one that
> reaches the drive is XP Home and the one that does not is XP Pro. The
> drive itself is reputedly some Linux-based disk OS.

One more thing: I can access it in Safe Mode with Networking. Does
this enable anyone to pinpoint the problem?

Thanks!

Hmh, problem solved: there was a nondescript VPN remnant sitting in
the corner, and when that was removed from the starting lineup, full
access became available to the drive.

Thank you all for your time and effort!