Re: Cannot access other computer!
From: MS (ms_at_nospam.com)
Date: 09/02/04
- Next message: skeeta: "Starting Internet Connection From Run Command"
- Previous message: Chuck: "Re: Wireless - No Network Browse - No Permissions?"
- In reply to: Chuck: "Re: Cannot access other computer!"
- Next in thread: Chuck: "Re: Cannot access other computer!"
- Reply: Chuck: "Re: Cannot access other computer!"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Sep 2004 16:22:32 -0700
Thank you, Chuck,
Using your checklist, I got it working. I'll explain a little more.
Yes, I was able to successfully ping the other, still when I couldn't see
the other's drive.
Yes, I was running both Client for Microsoft Networks, and File and Printer
Sharing
for Microsoft Networks, as well as several others. (Is there a list
somewhere, of which of these protocols one should have running for basic
networking. Could having protocols one doesn't need running all the time be
a resource drain?)
As mentioned, I did have sharing set up on the root directory (and all
subdirectories) of both drives.
The "Computer Browser" service was running on one, but not the other. I just
checked this now, however, after I already was able to see the shared drive,
so I don't think the fact that one computer didn't have it running caused
the problem, as later the problem was solved, and that computer was still
not running that service (set to manual). I started it now though, and set
it to "Automatic", just in case.
No, I did not have "NetBIOS over TCP/IP" selected. The default selection
there is otherwise. I made the change you suggested. (Curious though, how
most people would know to do that. The default is otherwise, it is in an
obscure place, I didn't see any mention of it in any of my searching of
networking guides on the web, the Microsoft Knowledge Base, etc. If that
setting is necessary to see the files on a connected network computer, how
would most people know to do that? Why is the default setting otherwise?
Anyhow, it worked for me.
Also, in looking at my protocols, I figured (although I really don't know
anything about these protocols), that if "NetBios over TCP/IP" is selected,
that all the protocols with Netbios in the name probably should be selected.
On one of the two computers NWLink NetBIOS was checked, but not "NWLink
IPX/SPX NetBIOS Compatible Transport Protocol". I checked that one also. On
the other computer neither of those two protocols were selected, and I
selected both. I don't know if selecting those protocols had anything to do
with getting the sharing to work, or whether only the change discussed in
the preceding paragraph was necessary. As I discussed further up, which
protocols are necessary for most networking? Of course "Client for Microsoft
Networks", and "File and Printer Sharing for Microsoft Networks", and
"Internet Protocol (TCP/IP)". But how about "Microsoft TCP/IP version 6"? (I
have it selected, but don't understand how it differs or adds to the other
TCP/IP.) How about "QoS Packet Scheduler"? (I have it selected, but haven't
the slightest idea what it is.) And as I mentioned, those two NWLink
protocols, which I just selected due to them having NetBIOS in the name.
Therefore--what made the sharing work on my setup--the change to "NetBIOS
over TCP/IP", as you suggested. Perhaps also the addition of the two NWLink
protocols with NetBIOS in the name, but I really don't know if that had
anything to do with it.
Thanks again for your suggestions, which succeeded when no other guides did.
Furhter clarification would be interesting.
"Chuck" <none@example.net> wrote in message
news:62tej0hak68fkcun6moku2kcivlu38bmve@4ax.com...
> Start by verifying that you do have connectivity between the two. Can you
> ping
> each from the other? By name and by ip address? If not, exactly what
> error
> (provide text please) do you get when pinging?
>
> Many wireless cards report "excellent signal strength" when the total
> "signal"
> includes a lot of noise. Have you tried other channels on the wireless
> cards?
> What security features are enabled?
>
> Are you running both Client for Microsoft Networks, and File and Printer
> Sharing
> for Microsoft Networks (Local Area Connection - Properties), on each
> computer?
> Do you have shares setup on each?
>
> Are you running NetBIOS Over TCP/IP (Local Area Connection - Properties -
> TCP/IP
> - Properties - Advanced - WINS) on each computer?
>
> Make sure the browser service is running on each computer. Control
> Panel -
> Administrative Tools - Services. Verify that the Computer Browser service
> is
> started.
>
> If, in fact, you have connectivity (successful pings), and all necessary
> protocols and services, how about shares visibility? From each computer
> (use
> actual name / address of each computer as appropriate):
> Start - Run then:
> 1) \\ThisComputerByName
> 2) \\ThisComputerByIPAddress
> 3) \\OtherComputerByName
> 4) \\OtherComputerByIPAddress
> Report visibility of shares / exact error displayed in each test (8 tests
> total).
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
- Next message: skeeta: "Starting Internet Connection From Run Command"
- Previous message: Chuck: "Re: Wireless - No Network Browse - No Permissions?"
- In reply to: Chuck: "Re: Cannot access other computer!"
- Next in thread: Chuck: "Re: Cannot access other computer!"
- Reply: Chuck: "Re: Cannot access other computer!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
