500GB drive on WLAN; workgroup laptop sees it, domain laptop does not

[usenetfan]

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!

 

[John Wunderlich]

(e-mail address removed) wrote in
m:

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?

Whatever you do, do NOT come out of the domain. This should not be
required. Unless you have a *local* Administrator login/password set
up on your machine, you will find yourself locked-out of your own
machine until it can be re-joined to the domain.

Try connecting to the drive directly without the GUI. Bring up a
command prompt (start->run->cmd) and enter the command:
net use * \\192.168.0.100\share
where "share" is the name of the shared folder/disk that you have set
up on the drive (you can probably get this from the machine that
works). If you have user/password authentication, then enter the
command:
net use * \\192.168.0.100\share /user:192.168.0.100\username
(replace "username" with the appropriate user name)
The status returned by this command should be helpful in further
diagnosis.

Also, try disabling all firewall programs on the computer or make
sure that the firewall allows ports 135, 137, 138, and 445 for
Windows networking.

HTH,
John

 

[usenetfan]

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.

The workgroup machine finds the drive and allows it to be maped
without using the WD Anywhere software. I'll try and see about the
ports.

Thanks again!

 

[John Wunderlich]

(e-mail address removed) wrote in
m:

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.

The workgroup machine finds the drive and allows it to be maped
without using the WD Anywhere software. I'll try and see about the
ports.

Thanks again

The System error 53 that you get indicates a communications problem.
Since you can http to the server, we know that your TCP/IP stack is
working. This problem sounds like a firewall problem. If you have a
firewall program installed, make sure that somewhere in the settings
that Microsoft File Sharing is enabled (or try disabling the firewall
program temporarily). If you're using the Windows Firewall, go to
the control panel -> Windows Firewall -> Exceptions Tab and verify
that there is a check beside "File and Printer Sharing". If you use
Cisco VPN Client, it comes with a firewall -- make sure it is
unchecked.

As a test you might also try booting into Safe Mode with Networking
and see if you can connect.

HTH,
John

 

[usenetfan]

As a test you might also try booting into Safe Mode with Networking

and see if you can connect.

HTH,
John

Well I'll be damned! I can access it in Safe Mode with Networking.
Does this enable you to pinpoint the problem?

Thanks, John - much appreciated!

 

[Jack \(MVP-Networking\).]

Hi
I would not play with the work Laptop.
It might be that as part of the work Domain restrictions, the computer has
less control.
You better of checking first with work's IT.
Jack (MVP-Networking).

 

[John Wunderlich]

Well I'll be damned! I can access it in Safe Mode with Networking.
Does this enable you to pinpoint the problem?

It doesn't pinpoint the problem, but it does bracket it. Safe mode
is nothing more than regular mode but with only the bare essential
software running. In your case, it doesn't work with everything
running but does work with only essentials running... so one of the
"non-essentials" is interfering.

The next step is to use a tool like "msconfig"
start -> run -> msconfig
to selectively turn on/off the non-essential programs and services
that normally load at boot. Start with the "Startup" tab, turn them
all off, and reboot. Verify that it still works. Then turn them on
a few at a time until you find the one that causes it not to work.
My bet is a firewall or VPN program... Msconfig is only a diagnostic
tool. Once the offending program is found, you should uninstall the
problem software and return msconfig to "normal".

Good Luck,
John