Re: WNetAddConnection doesn't work without DHCP
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Thu, 23 Oct 2008 08:07:29 -0700
It's not obsolete, just used for other things, in this case NetWare servers.
I'm not saying that that, specifically, is required, but you need your
Windows machines to respond to LAN Manager requests, which I think means
that you need *one* of the Net BIOS protocols. The fact that you can ping
the server by name means *nothing* about being able to connect to the name.
That name is being mapped, by the IP stack, using hosts or whatever, to the
indicated IP address. That won't work for the Net BIOS operation that you
need to perform.
Your DHCP server is sending some piece of information to the adapter being
configured that way that you have not set yourself on the adapter that is
using static addressing. I don't, off-hand, know what that is, but you
could look at the configuration of the DHCP server to see what requests it
will respond to, or capture the messages between the client and the server
to see what they are.
Paul T.
"Ulrich Eckhardt" <eckhardt@xxxxxxxxxxxxxx> wrote in message
news:si46t5-4pk.ln1@xxxxxxxxxxxxxxxxxxxxxxxxx
"Paul G. Tobey [eMVP]" wrote:
The only way is for the device to include the redirector, which you
obviously have, which includes the NetBIOS component. That, however,
doesn't have any means to add names to it. If the device you're trying
to
map doesn't already have a name and NetBIOS support on it, the name
doesn't exist on the network and sharing won't work. I'm not sure
exactly
what your scenario is, but here's what mine looks like:
I have a bunch of Windows machines, mostly Windows XP. They all have
TCP/IP, IPX/SPX (with NetBIOS), and NetBEUI protocols installed on them
(and, of course, they have names that are assigned via the System Control
Panel applets in Windows on the Computer Name page).
Actually, I would be surprised to find IPX/SPX running on my desktop, I
was
under the impression that that was an obsolete network protocol. Anyway, I
added it to the network settings and it didn't get me any further. I also
activated NETBIOS over TCP/IP, in the advanced settings, but that still
didn't get me any further.
My Windows CE devices all have custom names assigned to them, not the
default "WindowsCE", but something else entered via the Device Name page
of the System Control Panel applet in Windows CE.
Once you've set that device name for Windows CE *and rebooted the
device*,
you can grab any share on any of the Windows machines using
\\<name>\<share>. Where is this falling down for you?
I have static addresses assigned to both the CE device and my desktop. I
can
ping my desktop via its name from the CE device (I have added according
entries under HKLM/Comms/Tcpip/Hosts). However, I can neither map nor use
a
share on my desktop machine, I always get error 53 (network path not
found).
If I use the second network adapter on the CE machine, which is configured
to use DHCP, it works. However, I can't use DHCP in the setup I need.
Thanks for your suggestion!
Uli
--
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
.
- References:
- WNetAddConnection doesn't work without DHCP
- From: Ulrich Eckhardt
- Re: WNetAddConnection doesn't work without DHCP
- From: Paul G. Tobey [eMVP]
- Re: WNetAddConnection doesn't work without DHCP
- From: Ulrich Eckhardt
- WNetAddConnection doesn't work without DHCP
- Prev by Date: RE: Precise timing
- Next by Date: Re: add oleobject on c#
- Previous by thread: Re: WNetAddConnection doesn't work without DHCP
- Next by thread: Usb Device Serial Number
- Index(es):
Relevant Pages
|
