CONNECTED - but an AUTOCONFIGURED IP?! How does this happen?
Still one problem to be solved: TCP/IP is required to send the tracking data from the tracking laptop to the mapping PC. Everything worked fine from April until Wednesday 02005/10/19 16:00 - then one of the network connections lost its ability to receive an IP.
It is still connected to the network - but not recognised by DHCP. How is this possible?!
The friendly and competent technicians are aware of the problem.
Update: It took about three weeks to sort this out. Why? Something like that is normally solved within a couple of hours.