gethostbyname() in Multi-homed systems...

[thammond]

I am using XP Embedded on a multi-homed SBC. Each of the network cards
is given its own IP address and may be given additional IP addresses as
well. How can I specify which of these IP Addresses is used to resolve
the system's responses to GetHostname( ) and GetHostByName( )?

I tried assigning the IP addresses (to the network cards) in different
orders thinking maybe it used a rule like "last IP added" or something
similar to that. I tried adding an entry to the hosts file. I tried
voodoo like unplugging one of the network connections at powerup,
thinking that maybe it is related to "first network card found at
startup." Nothing has worked so far. I have tried this on two cards -
one of them works the way I want it to (uses the first NIC's first
address), but the second one is using an address from the second NIC.

If this is not the proper forum for this question, my apologies. ...
and could you point me to a better location?

Thanks.
- Tony H.

 

[Slobodan Brcin \(eMVP\)]

I must be tired or something similar but I do not understand what you want to do, or why do you want to do it in the first place :-(

Have you looked at function "getaddrinfo"?

Regards,
Slobodan

 

[thammond]

Hi Slobodan,

I realize it's an unusual question, and maybe I didn't phrase it
correctly. Perhaps a general description of the operation scenario
would help. I am not a network guy, so my terminology may not be
correct.

I have a 3rd-party piece of software that must run on my multi-homed
target. That software creates a set of Windows sockets for users to
interface with it. For my application to connect to these sockets, I
must know (at compile time) what IP address those sockets are bound to.
Also, applications external to the target must be able to connect to
these sockets, so they must also know the IP address in use.

It appears that the 3rd-party software is using gethostbyname() to
determine which IP Address it binds its sockets to. Several times, I
have seen it use a different IP address than the first one on the first
network card (the one I want it to use). I am trying to find out how I
can tell Windows to use a specific IP address when resolving its
hostname. Perhaps this is not a standard use of network facilities,
but it's what I'm stuck with.

Any ideas? Or would a different forum be more appropriate?

Thanks
- Tony H.

I must be tired or something similar but I do not understand what you

want to do, or why do you want to do it in the first place :-(

 

[Slobodan Brcin \(eMVP\)]

Hi Tony,

Crosspost (add few more NG to this thread) reply or additional question with this NG and other network related NG so we all might
try to help.
If you have third party application that you have no control over than there might be something in registry that we can do.

Please check windows\system32\drivers\etc folder and based on lmhosts sample file create one "lmhosts." file it might help you.

Regards,
Slobodan

 

[Slobodan Brcin \(eMVP\)]

While searching for my problems I have accidentally stumbled in MSDN on article that tell following:

NetBIOS over TCP/IP (NetBT) binds to the first IP address for each network adapter only.
When a NetBIOS name registration is sent out, only one IP address is registered per adapter. This registration occurs over the IP
address that is listed first in the properties of the TCP/IP protocol for the adapter.

I hope that this is info that you needed. Now you will need to figure out how to add additional IP in order. I would attach registry
directly.

Regards,
Slobodan
Multihoming Considerations
If TCP/IP is configured for multiple network adapters, or for a single network adapter with multiple IP addresses, you must consider
the following issues:

NetBIOS over TCP/IP (NetBT) binds to the first IP address for each network adapter only.

When a NetBIOS name registration is sent out, only one IP address is registered per adapter. This registration occurs over the IP
address that is listed first in the properties of the TCP/IP protocol for the adapter.

A unique IP address and subnet mask are defined for each adapter.

For each network adapter, an instance of TCP/IP is bound to the adapter. You can choose to have IP addresses dynamically assigned by
DHCP (or APIPA if a DHCP server is not present) or defined manually as static addresses.

Domain Name System (DNS) configuration settings are global.

The settings on the DNS tab in Advanced TCP/IP Properties are used for all adapters on the computer. Therefore, for a multihomed
computer, you must carefully define options for DNS that are applicable for all adapters using TCP/IP. Usually, this means that if
you want to use DNS for name resolution with any TCP/IP connection, make sure DNS is configured.

Windows Internet Name Service (WINS) configuration settings are defined for each adapter.

The settings on the WINS configuration tab are used only for the adapter you are configuring. For example, NetBIOS over TCP/IP
(NetBT) can be enabled or disabled for each network adapter. If you enable the option Disable NetBIOS over TCP/IP for a LAN adapter,
this option is enabled only for that adapter, not for other LAN adapters on the computer.

The default gateway can be different for each adapter.

While it is possible to configure a default gateway IP address for each network interface, there is only a single active default
route in the IP route table. If there are multiple default routes in the IP route table (assuming a metric of 1), then the specific
default route is chosen randomly when TCP/IP is initialized. This behavior can lead to confusion and loss of connectivity.

It is recommended that when you are configuring a computer to be multihomed on two disjoint networks, configure a default gateway IP
on the interface that is attached to the portion of the IP internetwork that contains the most network segments. Then, either add
static routes or use a routing protocol to provide connectivity to remote networks reachable through the other interfaces.

Only one default gateway is used at a time.

Although you can have a different default gateway for each adapter, Windows 2000 Professional uses only one default gateway at a
time. This means that only certain hosts are reachable:

a.. Hosts on the local subnet
b.. Hosts that are reachable by the default gateway
As a result, in some cases you might lose network connectivity. For example, suppose your computer is first connected to the
corporate TCP/IP network and you make a PPP dial-up connection to the Internet. Your computer stops using the default gateway that
connects your computer to the corporate network and instead uses the default gateway that connects your computer to the Internet.
Therefore, you can reach hosts on your local subnet, but you cannot reach other hosts on your network.

To discover methods to access multiple gateways, see "Configure Local Route Table" later in this chapter.

 

[thammond]

Hi Slobodan,

That answer was almost there, but not exactly what I am looking for. I
can already add IP Addresses to network connectors using "netsh
interface ip add ..." in a predictable manner.

But when my 3rd party application goes to bind its Windows sockets,
which network connector will it use to retrieve the binding IP Address
from? I need it to always bind to "Local Area Connection," but I have
seen it bind to "Local Area Connection 2" on other identical targets.

I posted this question on the XP networking newsgroup as well and have
not received any responses. Perhaps I am trying to do something that
can not be done, or someething that is not commonly done in embedded
systems.

Thanks again.
- Tony H.

 

[KM]

Tony,

I read your message. What was not clear to me why changing lmhosts on the machine with the 3rd party software running did not help?

I mean if you set it in lmhosts that particular name is bound to a particular IP address, then you will have more predictable
behavior from the 3rd party software that calls to gethostbyname.

Just make sure that "EnableLMHOSTS" value set to dword:1 under [HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters].

Also look at the "RandomAdapter" parameter of NetBT ([HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]).

 

[Slobodan Brcin \(eMVP\)]

Hi Tony,

Do you have any control oven computer name passed to gethostbyname ?
Also do you know how that program obtained this name?

Only way that I see for you is to make your network adapters disabled on boot and then trough your application to enable them in
required order so that you always have consistent behavior.

Other way for you would be to make your service provider wrapper:

http://msdn.microsoft.com/library/d...nsock/name_resolution_model_for_the_spi_2.asp
http://msdn.microsoft.com/library/d...sock/sample_code_for_a_service_provider_2.asp

This way you should have full control.

Or to use undocumented codes to talk with netbt drivers and to unregister and register different NetBIOS names on different
adapters.

Regards,
Slobodan

 

[thammond]

I'll try these tips later today.

Thanks KM and Slobodan!
- Tony H

 

[thammond]

KM,

I made sure that the EnableLMHOSTS vaule was set to 1.
I then tried adding the computer name to the lmhosts
file as follows:

192.168.100.101 XPE-DEVICE

(Note: "XPE-DEVICE" is the name of my computer - the
name returned when you type "hostname" at a command
prompt)

This still does not work. I have tried this in the
hosts file as well with the same results. From my
own experiments, it seems that the hosts file can be
used to resolve any name _except_ the computer's own
name. I have seen this on full blown Windows PCs
as well. Is this true?

Also, I did not see a RandomAdapter parameter.
Should it have been there?

Thanks.
- Tony H.

Tony,

I read your message. What was not clear to me why changing lmhosts on

the machine with the 3rd party software running did not help?

I mean if you set it in lmhosts that particular name is bound to a

particular IP address, then you will have more predictable

behavior from the 3rd party software that calls to gethostbyname.

Just make sure that "EnableLMHOSTS" value set to dword:1 under [HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters].

Also look at the "RandomAdapter" parameter of NetBT ([HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]).

--
Regards,
KM, BSquare Corp.

Hi Slobodan,

That answer was almost there, but not exactly what I am looking for. I
can already add IP Addresses to network connectors using "netsh
interface ip add ..." in a predictable manner.

But when my 3rd party application goes to bind its Windows sockets,
which network connector will it use to retrieve the binding IP Address
from? I need it to always bind to "Local Area Connection," but I have
seen it bind to "Local Area Connection 2" on other identical targets.

I posted this question on the XP networking newsgroup as well and have
not received any responses. Perhaps I am trying to do something that
can not be done, or someething that is not commonly done in embedded
systems.

Thanks again.
- Tony H.

 

[Slobodan Brcin \(eMVP\)]

Hi Tony,

I have been battling with NETBIOS for almost last two months but from much different level and for different purpose. (Unfortunately
I must do much more settings that you need from "Limited user account" :-( What I'm trying to accomplish is on scale next to
impossible).

XPE-DEVICE is some NetBIOS name. What that name mean is not certain.

"XPE-DEVICE " This would be for instance NetBIOS name of SMB server.

NetBIOS names are 15 ASCII characters long. 16th byte is value (0-255) that describe service that NetBIOS name describe. There is a
table of these values defined.
0x20 (Space character) represent for instance SMB server representation per that table.

If you want to specify certain IP addresses to NetBT driver then you will have to use undocumented IOCTL values on
\Device\NetBT_Tcpip_{GUID} to set remove NetBIOS/service names to IP addresses.
IOCTL code for netbt driver used for adding new name to cache for selected adapter is 0x2100d0.

I have no idea if this can help you, but you have a better start then I had.

Regards,
Slobodan

KM,

I made sure that the EnableLMHOSTS vaule was set to 1.
I then tried adding the computer name to the lmhosts
file as follows:

192.168.100.101 XPE-DEVICE

(Note: "XPE-DEVICE" is the name of my computer - the
name returned when you type "hostname" at a command
prompt)

This still does not work. I have tried this in the
hosts file as well with the same results. From my
own experiments, it seems that the hosts file can be
used to resolve any name _except_ the computer's own
name. I have seen this on full blown Windows PCs
as well. Is this true?

Also, I did not see a RandomAdapter parameter.
Should it have been there?

Thanks.
- Tony H.

Tony,

I read your message. What was not clear to me why changing lmhosts on

the machine with the 3rd party software running did not help?

I mean if you set it in lmhosts that particular name is bound to a

particular IP address, then you will have more predictable

behavior from the 3rd party software that calls to gethostbyname.

Just make sure that "EnableLMHOSTS" value set to dword:1 under [HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters].

Also look at the "RandomAdapter" parameter of NetBT ([HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]).

--
Regards,
KM, BSquare Corp.

Hi Slobodan,

That answer was almost there, but not exactly what I am looking for. I
can already add IP Addresses to network connectors using "netsh
interface ip add ..." in a predictable manner.

But when my 3rd party application goes to bind its Windows sockets,
which network connector will it use to retrieve the binding IP Address
from? I need it to always bind to "Local Area Connection," but I have
seen it bind to "Local Area Connection 2" on other identical targets.

I posted this question on the XP networking newsgroup as well and have
not received any responses. Perhaps I am trying to do something that
can not be done, or someething that is not commonly done in embedded
systems.

Thanks again.
- Tony H.

 

[KM]

Slobodan,

Hi Tony,

I have been battling with NETBIOS for almost last two months but from much different level and for different purpose. (Unfortunately
I must do much more settings that you need from "Limited user account" :-( What I'm trying to accomplish is on scale next to
impossible).

XPE-DEVICE is some NetBIOS name. What that name mean is not certain.

"XPE-DEVICE " This would be for instance NetBIOS name of SMB server.

NetBIOS names are 15 ASCII characters long. 16th byte is value (0-255) that describe service that NetBIOS name describe. There is a
table of these values defined.
0x20 (Space character) represent for instance SMB server representation per that table.

MSDN says: "The NetBIOS name is derived from the host name, but the two names might not be identical. The NetBIOS name is a 16-byte
string that uniquely identifies a computer or service for network communication. It is used by all the Windows 2000 network services
to uniquely identify themselves. If the DNS host name is 15 or fewer bytes, the NetBIOS name is the host name plus enough spaces to
form a 15-byte name, followed by a unique identifier, the sixteenth byte, that specifies the network service. If the DNS host name
is longer than 15 bytes, then by default, the NetBIOS name is the host name, truncated to 15 bytes, plus the service identifier. If
you try to create two DNS host names and the first 15 bytes are the same, you are prompted to enter a new name for NetBIOS."


It also says: "The NetBIOS name is used to uniquely identify the NetBIOS services listening on the first IP address that is bound to
an adapter. This unique NetBIOS name is resolved to the IP address of the server through broadcast, WINS, or the LMHosts file. By
default, it is the same as the host name up to 15 bytes, plus any spaces necessary to make the name 15 bytes long, plus the service
identifier.
The NetBIOS name is also known as a NetBIOS computer name.

For example, a NetBIOS name might be Client1."

This is just to confirm the point.

Regards,
Konstantin

If you want to specify certain IP addresses to NetBT driver then you will have to use undocumented IOCTL values on
\Device\NetBT_Tcpip_{GUID} to set remove NetBIOS/service names to IP addresses.
IOCTL code for netbt driver used for adding new name to cache for selected adapter is 0x2100d0.

I have no idea if this can help you, but you have a better start then I had.

Regards,
Slobodan

KM,

I made sure that the EnableLMHOSTS vaule was set to 1.
I then tried adding the computer name to the lmhosts
file as follows:

192.168.100.101 XPE-DEVICE

(Note: "XPE-DEVICE" is the name of my computer - the
name returned when you type "hostname" at a command
prompt)

This still does not work. I have tried this in the
hosts file as well with the same results. From my
own experiments, it seems that the hosts file can be
used to resolve any name _except_ the computer's own
name. I have seen this on full blown Windows PCs
as well. Is this true?

Also, I did not see a RandomAdapter parameter.
Should it have been there?

Thanks.
- Tony H.

Tony,

I read your message. What was not clear to me why changing lmhosts on

the machine with the 3rd party software running did not help?

I mean if you set it in lmhosts that particular name is bound to a

particular IP address, then you will have more predictable

behavior from the 3rd party software that calls to gethostbyname.

Just make sure that "EnableLMHOSTS" value set to dword:1 under [HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters].

Also look at the "RandomAdapter" parameter of NetBT ([HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]).

--
Regards,
KM, BSquare Corp.

Hi Slobodan,

That answer was almost there, but not exactly what I am looking for. I
can already add IP Addresses to network connectors using "netsh
interface ip add ..." in a predictable manner.

But when my 3rd party application goes to bind its Windows sockets,
which network connector will it use to retrieve the binding IP Address
from? I need it to always bind to "Local Area Connection," but I have
seen it bind to "Local Area Connection 2" on other identical targets.

I posted this question on the XP networking newsgroup as well and have
not received any responses. Perhaps I am trying to do something that
can not be done, or someething that is not commonly done in embedded
systems.

Thanks again.
- Tony H.

 

[Slobodan Brcin \(eMVP\)]

Konstantin,

In addition to documented ways. There is always undocumented IOCTL approach of forcing NetBIOS names to certain drivers.

Regards,
Slobodan

Slobodan,

Hi Tony,

I have been battling with NETBIOS for almost last two months but from much different level and for different purpose. (Unfortunately
I must do much more settings that you need from "Limited user account" :-( What I'm trying to accomplish is on scale next to
impossible).

XPE-DEVICE is some NetBIOS name. What that name mean is not certain.

"XPE-DEVICE " This would be for instance NetBIOS name of SMB server.

NetBIOS names are 15 ASCII characters long. 16th byte is value (0-255) that describe service that NetBIOS name describe. There

is

a
table of these values defined.
0x20 (Space character) represent for instance SMB server representation per that table.

MSDN says: "The NetBIOS name is derived from the host name, but the two names might not be identical. The NetBIOS name is a 16-byte
string that uniquely identifies a computer or service for network communication. It is used by all the Windows 2000 network services
to uniquely identify themselves. If the DNS host name is 15 or fewer bytes, the NetBIOS name is the host name plus enough spaces to
form a 15-byte name, followed by a unique identifier, the sixteenth byte, that specifies the network service. If the DNS host name
is longer than 15 bytes, then by default, the NetBIOS name is the host name, truncated to 15 bytes, plus the service identifier. If
you try to create two DNS host names and the first 15 bytes are the same, you are prompted to enter a new name for NetBIOS."


It also says: "The NetBIOS name is used to uniquely identify the NetBIOS services listening on the first IP address that is bound to
an adapter. This unique NetBIOS name is resolved to the IP address of the server through broadcast, WINS, or the LMHosts file. By
default, it is the same as the host name up to 15 bytes, plus any spaces necessary to make the name 15 bytes long, plus the service
identifier.
The NetBIOS name is also known as a NetBIOS computer name.

For example, a NetBIOS name might be Client1."

This is just to confirm the point.

Regards,
Konstantin

If you want to specify certain IP addresses to NetBT driver then you will have to use undocumented IOCTL values on
\Device\NetBT_Tcpip_{GUID} to set remove NetBIOS/service names to IP addresses.
IOCTL code for netbt driver used for adding new name to cache for selected adapter is 0x2100d0.

I have no idea if this can help you, but you have a better start then I had.

Regards,
Slobodan

KM,

I made sure that the EnableLMHOSTS vaule was set to 1.
I then tried adding the computer name to the lmhosts
file as follows:

192.168.100.101 XPE-DEVICE

(Note: "XPE-DEVICE" is the name of my computer - the
name returned when you type "hostname" at a command
prompt)

This still does not work. I have tried this in the
hosts file as well with the same results. From my
own experiments, it seems that the hosts file can be
used to resolve any name _except_ the computer's own
name. I have seen this on full blown Windows PCs
as well. Is this true?

Also, I did not see a RandomAdapter parameter.
Should it have been there?

Thanks.
- Tony H.

KM wrote:
Tony,

I read your message. What was not clear to me why changing lmhosts on
the machine with the 3rd party software running did not help?

I mean if you set it in lmhosts that particular name is bound to a
particular IP address, then you will have more predictable
behavior from the 3rd party software that calls to gethostbyname.

Just make sure that "EnableLMHOSTS" value set to dword:1 under
[HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters].

Also look at the "RandomAdapter" parameter of NetBT
([HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]).

--
Regards,
KM, BSquare Corp.

Hi Slobodan,

That answer was almost there, but not exactly what I am looking
for. I
can already add IP Addresses to network connectors using "netsh
interface ip add ..." in a predictable manner.

But when my 3rd party application goes to bind its Windows sockets,
which network connector will it use to retrieve the binding IP
Address
from? I need it to always bind to "Local Area Connection," but I
have
seen it bind to "Local Area Connection 2" on other identical
targets.

I posted this question on the XP networking newsgroup as well and
have
not received any responses. Perhaps I am trying to do something
that
can not be done, or someething that is not commonly done in
embedded
systems.

Thanks again.
- Tony H.

 

[KM]

Slobodan,

Certainly

Sometimes I think that programming under Windows is all about using undocumented functionality.
With a debugger and other useful tools in hands, it is always possible to reverse engineer the undocumented functions. The question
is how much time a developer has to spend to figure out all the required info.

Anyway, Google is always our friend to help with that.


--
Regards,
Konstantin

Konstantin,

In addition to documented ways. There is always undocumented IOCTL approach of forcing NetBIOS names to certain drivers.

Regards,
Slobodan

Slobodan,
is

MSDN says: "The NetBIOS name is derived from the host name, but the two names might not be identical. The NetBIOS name is a 16-byte
string that uniquely identifies a computer or service for network communication. It is used by all the Windows 2000 network services
to uniquely identify themselves. If the DNS host name is 15 or fewer bytes, the NetBIOS name is the host name plus enough spaces to
form a 15-byte name, followed by a unique identifier, the sixteenth byte, that specifies the network service. If the DNS host name
is longer than 15 bytes, then by default, the NetBIOS name is the host name, truncated to 15 bytes, plus the service identifier. If
you try to create two DNS host names and the first 15 bytes are the same, you are prompted to enter a new name for NetBIOS."


It also says: "The NetBIOS name is used to uniquely identify the NetBIOS services listening on the first IP address that is

bound

to
an adapter. This unique NetBIOS name is resolved to the IP address of the server through broadcast, WINS, or the LMHosts file. By
default, it is the same as the host name up to 15 bytes, plus any spaces necessary to make the name 15 bytes long, plus the service
identifier.
The NetBIOS name is also known as a NetBIOS computer name.

For example, a NetBIOS name might be Client1."

This is just to confirm the point.

Regards,
Konstantin

If you want to specify certain IP addresses to NetBT driver then you will have to use undocumented IOCTL values on
\Device\NetBT_Tcpip_{GUID} to set remove NetBIOS/service names to IP addresses.
IOCTL code for netbt driver used for adding new name to cache for selected adapter is 0x2100d0.

I have no idea if this can help you, but you have a better start then I had.

Regards,
Slobodan

KM,

I made sure that the EnableLMHOSTS vaule was set to 1.
I then tried adding the computer name to the lmhosts
file as follows:

192.168.100.101 XPE-DEVICE

(Note: "XPE-DEVICE" is the name of my computer - the
name returned when you type "hostname" at a command
prompt)

This still does not work. I have tried this in the
hosts file as well with the same results. From my
own experiments, it seems that the hosts file can be
used to resolve any name _except_ the computer's own
name. I have seen this on full blown Windows PCs
as well. Is this true?

Also, I did not see a RandomAdapter parameter.
Should it have been there?

Thanks.
- Tony H.

KM wrote:
Tony,

I read your message. What was not clear to me why changing lmhosts on
the machine with the 3rd party software running did not help?

I mean if you set it in lmhosts that particular name is bound to a
particular IP address, then you will have more predictable
behavior from the 3rd party software that calls to gethostbyname.

Just make sure that "EnableLMHOSTS" value set to dword:1 under
[HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters].

Also look at the "RandomAdapter" parameter of NetBT
([HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]).

--
Regards,
KM, BSquare Corp.

Hi Slobodan,

That answer was almost there, but not exactly what I am looking
for. I
can already add IP Addresses to network connectors using "netsh
interface ip add ..." in a predictable manner.

But when my 3rd party application goes to bind its Windows sockets,
which network connector will it use to retrieve the binding IP
Address
from? I need it to always bind to "Local Area Connection," but I
have
seen it bind to "Local Area Connection 2" on other identical
targets.

I posted this question on the XP networking newsgroup as well and
have
not received any responses. Perhaps I am trying to do something
that
can not be done, or someething that is not commonly done in
embedded
systems.

Thanks again.
- Tony H.

 

[thammond]

Slobodan,

"XPE-DEVICE" is the computer name that I entered in the Standard PC
component of my XPe project (I followed Jon Fincher's instructions for
setting up remote debugging with XPe). This is the host name that I
have been talking about in this discussion.

So is the "Computer Name" field of the Standard PC component used as a
NetBIOS name? Are we still talking about the same thing? (Please
forgive my lack of networking knowledge).
- Tony H.

Hi Tony,

...

XPE-DEVICE is some NetBIOS name. What that name mean is not certain.

"XPE-DEVICE " This would be for instance NetBIOS name of SMB server.

NetBIOS names are 15 ASCII characters long. 16th byte is value

(0-255) that describe service that NetBIOS name describe. There is a

table of these values defined.
0x20 (Space character) represent for instance SMB server representation per that table.

If you want to specify certain IP addresses to NetBT driver then you

will have to use undocumented IOCTL values on

 

[Slobodan Brcin \(eMVP\)]

Hi Tony,

I have been talking about your lmhost file based on your prior response.

Also long time ago you should have added few other news-groups to this discussion, since there are developers that only deal with
network programming and they might be able to fill in the gaps.
I think that we have strayed from the source of the problem :-(

Please create new thread with current detailed problem description and cross-post (make one linked post to all these NG) it to:
microsoft.public.win32.programmer.networks
microsoft.public.windowsxp.embedded

Include other programming news groups as well.

Please do not do multi-post thing like you did before. You have posted same question to different news groups. This is bad because
we can't see answers to these questions and there are people that monitor more NG and have to download your same message more than
once.


Regards,
Slobodan

 

[thammond]

Sorry about the posting mixup. I'm kinda new to this.
And thanks for trying to help anyway.
- Tony H.