2.0 Installation and TcpClient

[Guest]

I have an app that uses the TcpClient to query data from a remote device. It
used to work. I installed the 2.0 framework on it yesterday and the app is
broken. I have the 2.0 framework on my desktop and it works there. I
downloaded the redistributable to install it on the remote server. On my
box, it was installed as part of VS2005.

Using Ethereal, I can see the packets when running on my desktop (and could
see them when it was working, obviously), but on the other machine, I get
nothing. Its like they never make it out of the network stack to the
interface card. This machine has two networks on it, and the packets aren't
coming out on either (though maybe routing was confused...).

The machine has been rebooted since the 2.0 framework install, even though
the install didn't ask to be rebooted. I thought maybe the network stack
needed to be restarted or something. The box that its not workign on is
Windows 2003 w/ all the latest updates. There were some updates that were
installed on Tuesday. The updates are handled by the admin guys. I don't
know what they were, and I can't say for sure whether this app was working
after the updates.

I'll look at the updates installed. Any one have any other suggestions or
maybe have seen this before and can tell me what checkbox to uncheck to fix
it?

 

[Vadym Stetsyak]

AFAIR if you've installed VS2005 then you had to install SP1, SP1 tightens
OS security
Did you check builtin firewall if it is disabled?

 

[Guest]

The machine w/ the problem doesn't have visual studio installed. I
downloaded the .Net 2.0 redistributable from MS and installed it. And the
firewall is disabled on the server.

 

[Guest]

Figured my problem out. Turns out the box I was talking to had gotten itself
confused. I didn't see the Ethereal traffic because I was looking for the
devices specific ip. There were ARP packets going out, which were getting
filtered out. I reset the box and all is well now. Thanks for the
suggestions, though.