Re: remoting - nasty bug?

> > When you install loopback adapter you can specify any address manually,
> > or use automatically configured ip address

> I have to specify it manually, so the client at the machine with the
server
> can reference the server through this address.. it only works then (I
tried
> it). if I continue to reference it with the machine name or "localhost",
> then it continues to produce the same behaviour no matter that the
loopback
> is present.

Currently I think we need to investigate Alex Passos's idea (about incorrect
name resolution)

> After the problem happens, I can still get the prompt
> although I cannot connect to the server with my client.

The reason to check is following:
at this moment telnet uses new name resolution scheme (which is occurs after
disconnection),
but client still use old IP address (which was before disconnection)

> It happened on anothe machine..
> so it is definitelly not the problem just with my machine!

It might be a problem with a whole network configuration
(If you are in domain, then chances are good
that for some aspects all machines behave in the same way)

Please provide the following information at your page with problem
description:
- source code of client application
- dump from "ipconfig /all" command
- content of HOSTS file
- dump from "route print" command
- dump from "ping localhost" and "tracert localhost" commands in
disconnected state
(but "telnet localhost 45326" works so disconnection it is not a problem)
- dump from "nslookup" utility




HOSTS file is located in "%SystemRoot%\system32\drivers\etc" for WindowsNT
family

The following types of problems can occur because of errors related to the
HOSTS file:
- The HOSTS file or the DNS server does not contain the particular host
name.
- The host name in the HOSTS file or in the command is misspelled or uses
different capitalization.
(Note: Host names are case-sensitive.)
- An invalid IP address is entered for the host name in the HOSTS file.
- The HOSTS file contains multiple entries for the same host on separate
lines; if so, the first entry is the one that is used.
- A mapping for a computer name-to-IP-address was mistakenly added to the
HOSTS file (rather than LMHOSTS).
- Last line should ends with carriage return symbol (see KB105998)

The correct format of the file is the following: "IP Address" "Friendly
Name"
For example:
127.0.0.1 localhost # Remarks are denoted with a #.

"ipconfig /flushdns" can be used to clear client name resolution cache






Next thing to check is packet routing (route print)

The resolved IP address is passed to the IP routing component. The routing
component returns either a routing error because a route was not found for
the destination IP address or the forwarding IP address and interface over
which the packet is to be forwarded cannot be found.






About channels I have found following quotes from various sources:

There are various considerations while writing a channel. They include a
balance of performance, scalability and implementation complexity.
Performance of a shared memory implementation would be certainly better than
named pipes. But issues when synchronizing between between reader/writers
could lead to scalibility concerns, especially with multiple clients. Named
Pipes provide good mix of both perf and scalability as compared to the TCP
channel.

Remoting in v2.0 of the framework is introducing a new IPC Channel meant for
x-proc communication on the same machine. It is based on named pipes and
works on win2k based platforms (win2k, winxp, win2k3). It will provide
better performance characteristics than the current TCP channel. It will
also provide a way to control access to the underlying pipe, so that the
server can limit the access to a specific group. As with the new TCP channel
it also supports authentication and impersonation of client identities.

For Framework 1.1 you can try
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=43a1ef11-c57c-45c7-a67f-ed68978f3d6d
(I have not tried it myself)





> Kakva pozivljajete?

Horosho, spasibo. Zavtra moj 27-j denx rozhdeniya :)
Fine, thanks. I am going to celebrate my 27-th birthday anniversary tommorow
:)

> oh yes, I will learn russian some day :))

I visited your homepage and was amused by number of languages which you are
learning :)


.

Relevant Pages

  • Remoting, events and custom encryption channel sinks
    ... - a server app hosts the remotable device service ... - the client app connects to a remote device service which is hosted by the ... The client app instantiates a tcp channel with a given port number because ...
    (microsoft.public.dotnet.framework.remoting)
  • RE: Problems with security requirements in Windows WorkGroups.
    ... "A remote side security requirement was not fulfilled during authentication. ... small chat application between a client and a server ... When I try to use the TCP channel I get the error (with NO inner exception ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: .Net Remoting TCP or HTTP?
    ... John's given a good description of why you would pick either the TCP or HTTP ... The reason is that, when the server needs to notify the client of the event, ... In the TCP case, this means using a bi-directional channel, so that requests ...
    (microsoft.public.dotnet.framework)
  • Re: .Net Remoting TCP or HTTP?
    ... John's given a good description of why you would pick either the TCP or HTTP ... The reason is that, when the server needs to notify the client of the event, ... In the TCP case, this means using a bi-directional channel, so that requests ...
    (microsoft.public.dotnet.framework.remoting)
  • RogerWilco: new funny bugs
    ... versus server and client (channel broadcast) ... RogerWilco is a voice chat application running on Windows and MacOS ...
    (Full-Disclosure)
Loading