🚀 go-pugleaf

I don't know if this will help, but
 a. normally I connect using the standard Win2k dialup (over g5, FWIW)
 b. over the years I have tried setting up my IP and DNS addresses manually,
and tried leaving it to Win2k/Demon to sort them out. Both approaches
usually work, but occasionally I've found I've had to switch to the other
approach temporarily to overcome some problem whose origin I've never been
able to determine.
 c. I just looked at my IPConfig and it also says 255.255.255.255 for the
subnet mask. But things seem to be working fine on this connection - for
now.
 d. I've had very similar problems recently (i.e. pinging the DNS servers
works but I often can't get through to web sites unless I muck around with
my config and redial, and it's frequently difficult to get through to the g5
numbers in the first place). Normally I put those down to more general
problems at the BT/Demon end, but I often wonder whether there is something
in the standard way things are set up on Windows that interacts badly with
the way Demon configure their various systems. Maybe the fact that something
thinks the subnet mask is 255.255.255.255 is one of those "somethings".

I've just been looking at the new Helpdesk pages on the demon site and
notice that there is a slight difference between the suggested configuration
for ISDN (don't specify DNS addresses, or indeed, any addresses) and
non-ISDN (do specify DNS addresses). What is the likely reason for that?

Peter Jamieson