I use the Microchip TCP/IP stack all the time and am at work on a project
right now. I think what you're finding is the DHCP server disables itself
if it finds another one on the network, which is good. The Microchip stack
has both a DHCP server and client. The server allows you to use a direct
connection with your laptop while the laptop is running a DHCP client.
While connected directly to your computer, can you tell the PICDEM that
you want a static IP address? Then provide one that is in your home
network subnet (ideally one out of the DHCP range, but not critical as
long as nothing else ends up at the same IP address). Also, have you tried
Ethernet Device Discoverer? It's handy for finding devices on the network.
We have a customized version at
http://ftp.uslinc.com/?dir=3Dftp/Products/EthernetDeviceDiscoverer .

Harold


> I thought that I would experiment with the IoT so I dug out a PICDEM.net =
2
> demo board. The board will communicate OK when plugged directly into my
> laptop but when connected to my Home Hub I can't get a connection;
> trawling through the User Guide it seems that the issue is that my hub ha=
s
> a built in web server and the Microchip TCP/IP stack can't handle more
> than one DHCP server on the network and disables itself. I am a novice to
> TCP/IP, is there a simple fix for this and if not is there an alternative
> TCP/IP stack that will be more capable? The demo board uses the
> PIC18F97J60.
> TIA
> James
>
> --
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>


--=20
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.