Unable to map drive with private ip address (using crossover cable)

  • Thread starter Thread starter rob
  • Start date Start date
R

rob

I have a server cluster and have added a crossover cable so I may copy
files directly between the two rather than use up potential bandwidth.
I've set-up the IP to be
ip: 10.10.10.20 and 10.10.10.21
subnet 255.0.0.0
gateway: none
dns : none

and 10.10.10.21 without DNS and netBIOS etc as I want to copy directly
using the IP. I can ping between the two servers on this address but
whenever I try to map it says "The network name can not be found"

I've tried adding a new share but the same thing occurs. Any thoughs
as to why? Help appreciated!
 
[snip]... without DNS and netBIOS etc ...
Click to expand...

DNS is a TCP/IP function
netBios is what Windows Networking is build on.
as I want to copy
directly using the IP. I can ping between the two servers on this
address
Click to expand...

"ping-ing" is a TCP/IP operation
but whenever I try to map it says "The network name can
not be found"
Click to expand...

"mapping" is a Windows Networking operation
I've tried adding a new share but the same thing occurs. Any
thoughs as to why? Help appreciated!
Click to expand...

You seem to be confusing Windows Networking with TCP/IP.
If you want to copy "directly using IP", then you'd need to set up a
FTP server on one machine and a FTP client on the other machine.

If you want copy files using Windows Networking over the TCP/IP
ethernet to map a drive, then you need Windows Networking
operational which means that at a minimum that you need to have
NetBIOS-over-TCP/IP (NetBT) enabled and a client for Microsoft
Networks installed.

HTH,
John
 
John said:
[snip]... without DNS and netBIOS etc ...
Click to expand...

DNS is a TCP/IP function
netBios is what Windows Networking is build on.
as I want to copy
directly using the IP. I can ping between the two servers on this
address
Click to expand...

"ping-ing" is a TCP/IP operation
but whenever I try to map it says "The network name can
not be found"
Click to expand...

"mapping" is a Windows Networking operation
I've tried adding a new share but the same thing occurs. Any
thoughs as to why? Help appreciated!
Click to expand...

You seem to be confusing Windows Networking with TCP/IP.
If you want to copy "directly using IP", then you'd need to set up a
FTP server on one machine and a FTP client on the other machine.

If you want copy files using Windows Networking over the TCP/IP
ethernet to map a drive, then you need Windows Networking
operational which means that at a minimum that you need to have
NetBIOS-over-TCP/IP (NetBT) enabled and a client for Microsoft
Networks installed.

HTH,
John
Click to expand...

Thankyou John I was basing the setup on my SQL heartbeat cluster
requirement.

I thought it wouldn't need any DNS or netBIOS as I was supplying the IP
myself - and so not using any names resolution of the DNS.

I have enabled netbios and found the [File and Printer Sharing for
Microsoft Networks] were all I needed. No gateway, DNS, WINS, Client
for Microsoft Networks were required.
Many thanks!
 
Thankyou John I was basing the setup on my SQL heartbeat cluster
requirement.

I thought it wouldn't need any DNS or netBIOS as I was supplying
the IP myself - and so not using any names resolution of the DNS.

I have enabled netbios and found the [File and Printer Sharing for
Microsoft Networks] were all I needed. No gateway, DNS, WINS,
Client for Microsoft Networks were required.
Many thanks!
Click to expand...

I'm glad your problem is resolved.
- The Gateway only needs to be specified if packets need to leave
your local subnet -- It's your default packet route for addreses
outside your local network.
- DNS is a TCP/IP name lookup -- Windows Networking will consult it
as a last resort if it can't resolve a name.
- WINS is the Windows networking name lookup and is only needed to
find computers that are outside your local subnet (a broadcast is
usually done to find clients in the local subnet).
- "Client for Microsoft Networks" is more interesting -- I thought
was required but apparently a Direct Hosted SMB can replace it in
Windows 2000/XP Pro/Server. Even though Microsoft claims that NetBT
is not required, from what I've read in these newsgroups, things work
better when NetBT is enabled.

Interesting reading:

"Client for Microsoft Networks Functions When Unbound from Network
Adapter"
<http://support.microsoft.com/kb/253959/en-us>

"Direct hosting of SMB over TCP/IP"
<http://support.microsoft.com/kb/204279/EN-US/>

-- John
 
Back
Top