[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: xAP framework based apps problem
- Subject: RE: xAP framework based apps problem
- From: "David Pullen" <dpullen@xxxxxxxxxxxxxxxx>
- Date: Wed, 23 Mar 2005 10:29:21 -0000
Mark
Here is the result of a working machine - also a docked Dell Latitude.
Thank you for you all taking time to look at this. It is at least
reassuring that I am not the only one that is perplexed by this problem!
BR
David
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : dplaptop
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter RHLAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-B0-D0-2E-E6-8D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.51
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 212.23.3.11
212.23.6.35
Lease Obtained. . . . . . . . . . : 23 March 2005 00:13:09
Lease Expires . . . . . . . . . . : 26 March 2005 00:13:09
-----Original Message-----
From: Mark Harrison (Groups) [mailto:mph@xxxxxxx]
Sent: 23 March 2005 09:29
To: xap_automation@xxxxxxx
Subject: Re: [xap_automation] xAP framework based apps problem
Edward Pearson wrote:
> Disclaimer: I'm not an IP expert.
>
> I'm wondering if the class A address with a class C subnet mask is
> causing trouble (eg, in the calculation of the broadcast address). Are
> other machines on your network configured like this?
Disclaimer: I know rather less about .NET than Edward knows about IP
The "Class A / Class C" stuff is pretty much entirely a footnote
of
historical interest these days. The CIDR (classless inter-domain
routing) standard has been supported by the MS IP stack for a long time.
As such, broadcast addresses are just calculating by a binary operation
on the S/N and IP without worrying about what class of addresses the IP
in question came from.
Hence it's very unlikely that this would be the problem.
The one thing that may be an issue is the "Primary DNS suffix"
being
missing. I've just checked, and all my machines have one.
David - can you run "IPCONFIG /ALL" on a known working machine
too, so
we can see any differences?
Regards,
Mark
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|