Re: only one usage of each socket address is normally permitted?
- From: "Ivar Lumi" <ivar@xxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 10:06:34 +0200
Hi,
Before running program ensure that ports are free.
Run -> type: cmd -> enter
you see command prompt
type:
netstat /a
you see all ports used.
"Beemer Biker" <jstateson@xxxxxxxx> wrote in message
news:12qtim666qtoe47@xxxxxxxxxxxxxxxxxxxxx
I have an app that binds to 5003 and 5004. It works fine on a desktop
VS2005/sp1 dotnet 2. It will not run on a laptop VS2005/sp1 dotnet 2
giving the above error on the very first bind.
I cannot spot what is causing the problem. There is something different
about the laptop no? Both system have xp, sp2 with latest patches and
firewall off. The program should behave the same. I start guessing and
disable spampal, snagit, whatever I can think of but I still cant bind nor
see what is causing the program to fail.
I set a breakpoint at the first bind and examine thecontents of
"audioEndPoint" and sure enough something is different. On the desktop I
see "m_address" and "m_port" listed in the watch window. They are missing
in the laptop but if I expand [+]Non-Public members then I see those two
variables. I would think that since both VS2005 with SP1 and DX90SDK
(same december) one would see the exact layout on each. I do not see the
corresponding [+]Public Members but both system do show [+]Static members.
Maybe that is not significent.
Could port 5002 and 5003 be un-available on my laptop?
The desktop is on a "domain" but the laptop isnt. Could this be a
security policy problem? If anything, I would think that the desktop
beiing on a domain might have a more restrictive security policy. FWIW,
the laptop has wireless.
--
=======================================================================
Joseph "Beemer Biker" Stateson
http://ResearchRiders.org Ask about my 99'R1100RT
=======================================================================
.
- Follow-Ups:
- Re: only one usage of each socket address is normally permitted?
- From: Beemer Biker
- Re: only one usage of each socket address is normally permitted?
- References:
- only one usage of each socket address is normally permitted?
- From: Beemer Biker
- only one usage of each socket address is normally permitted?
- Prev by Date: Re: Is Visual c++.NET 2005 a compromise compared to C# or VB.NET ? advice needed
- Next by Date: INotifyPropertyChanged Bug ?
- Previous by thread: only one usage of each socket address is normally permitted?
- Next by thread: Re: only one usage of each socket address is normally permitted?
- Index(es):
Relevant Pages
|
