Before starting the
DCC-"Guest", make use, that
the DCC-"Host" is running:
If your settings are
still proper, just
click on "Listen",
on "Change" to check
the setup and to
modify it (if required)
If you make a change,
select again your
role to be a Host.
Select again your
You can define a password
Such a DCC password has nothing
to do with any other password
on your system, but if you define it,
a system connection via DCC must
define it (like when connection
Your system will then wait for an
incoming Direct Cable connection.
Note: Without a DCC host waiting
for a connection, a DCC client (or guest)
can NOT make a connection.
If you did not install on the "Host"
the "File and Printer Sharing"
and if you did NOT share something, you will be reminded
So, make sure, that the "Host"
has "Shared" something:
The "Guest" will display then
the list of available resources on the "Host":
If you need this list again, call up up from the "View
Host" on the "Direct Cable
Connection" and from your "Network
BUT: If you call up the Network
Neighborhood too quickly, you
still may get the error-message : "Unable to browse the
First, if you have no Ethernet board installed in the DCC-hosts
did you "ENABLE"
on the DCC-host the Browse-Master ?
If not, Network-Neighborhood will NEVER
If yes, be patient for a few minutes (for the systems to adjust)
and then try it again.
Make sure, that "File-and-Print Sharing"
is installed on the DCC Client system
and that SOMETHING is shared.
Trying on the DCC Host to browse the "Network
Neighborhood" give the usual error
message "Unable to browse the network".
So, lets use the other access-methods: FIND
The DCC-client is found, but double-clicking on it does NOT show
the shared resources, but gives an error-message (which
means nothing to me, I cannot explain it).
So, we try now the most direct access method, using from the
Windows Start-Menu the RUN-command to enter the name of the
DCC-client in server-format: \\<name>:
The system still cannot access the
DCC client, and proposes to use
dialup-networking to connect to it:
close it by selecting NO.
so, no luck.
Last try: type into the RUN-box the
URL of the shared resource on the
The Dialup-Networking box may
popup again, close it.
But then you should see now the
data shared on the DCC client and
can access it, copy files via drag&drop. However: you still cannot map
a network drive.
Why do we have all these limitations on
accessing the data, why does the
Network Neighborhood not work ?
It all depends on your Windows Logon:
The network is configured for:
"Client for Microsoft networks"
which is also defined as
"Primary Network Logon"
but on starting Windows, we
get 'only' the Windows Logon,
(NOT the Network Logon).
All this is different, if the DCC Host has a network card
installed and the DCC Client connects to a
Network: the Network Neighborhood works(this is actually the same behavior on using
"Can I share my Internet
Connection via a Direct Cable Connection ? "