"Tim Coker" <TimCo***@discussions.microsoft.com> wrote in message
news:6E3F4990-38DD-43D4-8ECC-B15CBDF945C4@microsoft.com...
>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" wrote:

> 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?
>
> --
> Vadym Stetsyak aka Vadmyst
> http://vadmyst.blogspot.com
>
> "Tim Coker" <TimCo***@discussions.microsoft.com> wrote in message
> news:6E3F4990-38DD-43D4-8ECC-B15CBDF945C4@microsoft.com...
> >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? :)
>
>
>

"Tim Coker" wrote:

> 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? :)