Re: remoting - nasty bug?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thank you for your effort... I discovered something important..

The problem only arises when you get the reference from the SAO to some
MarshaledByRef object on the server.

I wrote a simple example.. here
http://www.david13.com/cases/DotNet/Remoting-BUG-Server-Inaccessible-From-Local-Machine/LANCableProblemReproduction.zip

just start the server.exe with LAN cable plugged in, run the client.exe and
observe that it works.. then unplug the cable and try to run the client
again.. it shouldn't run... now plug the cable back in and run the client
again.. it works without restarting the server..

So.. you will see from the example what I am trying to do.. I use the same
technique in two of my programs.. but for different reasons.. the sample I
am sending is for some simple notes.. please tell me if what I am doing is a
bad practice or not, but even more important - tell me if this behaviour is
normal or not..

I've seen some peole experience the same problem, but nobody found a good
solution for it.. or at least they didn't post it / or I can't find it!!

=====[not related to the problem]===========================================
S dniom razhdjenia! (hehe I found that one on some web page..)
cool! where are you from exactly.. maybe we can chat about all that
privately once we solve the problem (thank you for helping me out again!!)
oh about languages... :) it is very rewarding.. I hope I'll have more time
in the future to learn a few more languages. that would be cool!
Russian is not very far from my language - Slovenian!


"Sergey Radkevich" <sergeyr@xxxxxxxxxxxx> wrote in message
news:%239xZdU5UFHA.1404@xxxxxxxxxxxxxxxxxxxxxxx
> > > 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

  • Re: [WARNING] The DNS Resolver Cache service is not running.
    ... The hosts file is over 100K in size and can be found at the following ... the hosts file work for the DNS server for client browsing. ... Ipconfig /displaydns confirms that the XP client is going to the ...
    (microsoft.public.win2000.dns)
  • Re: remoting - nasty bug?
    ... > can reference the server through this address.. ... > although I cannot connect to the server with my client. ... HOSTS file is located in "%SystemRoot%\system32\drivers\etc" for WindowsNT ... There are various considerations while writing a channel. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: failed test MachineAccount
    ... DHPC Client is running and is set to automatic. ... There is a Server Protect running on the DC. ... The hosts file is there with only the following entry ... Windows Management Instrumentation Driver Extensions ...
    (microsoft.public.win2000.active_directory)
  • Re: Office 2007 slow to open files stored on SBS 2003
    ... Thanks Cliff. ... I'm going to login to the Win 7 client when it is free this ... hosts file in WinSxS actively used by the OS during normal operation. ... is disabled on both client and server. ...
    (microsoft.public.windows.server.sbs)
  • Re: [WARNING] The DNS Resolver Cache service is not running.
    ... The hosts file is over 100K in size and can be found at the following ... the hosts file work for the DNS server for client browsing. ... When Ipconfig /displaydns is run on the DNS server. ... Ipconfig /displaydns confirms that the XP client is going to the ...
    (microsoft.public.win2000.dns)