The following should narrow down the problem a bit for you.
1) On your PortMaster that your customer is connecting to create a packet filter to watch DNS pakcets.
add filter dns
set fitler dns 1 permit udp src eq 53
set filter dns 2 permit udp dst eq 53
set filter dns 3 permit tcp src eq 53
set filter dns 4 permit tcp dst eq 53
set console
ptrace dns
This packet filter will show any DNS packet arriving at or passing through the PortMaster.
* UDP 53 represent DNS queries
* TCP 53 represent DNS zone transfers (you should not see these with your dialup user)
2) From your customer find out what he has configured for DNS, DNS nameserver, any secondaries, Domain search, etc. Just have him read the whole screen.
"Start", "Settings", "Network", "TCP/IP", "DNS"
3) Also find out if his Win95 host has an ethernet connection as well as a dialup connection. Win95 has trouble figuring out which hole to forward packets out of sometimes.
4) Find out what the customer has configured for a "gateway".
5) With the ptrace running have the customer dialin and try to ping a hostname.
ex/ ping www.livingston.com
>From your console session watch for DNS pakcets.
* If you see DNS queries going out but not coming back then there is a problem with packets returning from the nameserver to the PortMaster.
- Make sure IP of nameserver matches the dst IP address in the DNS queries.
- Make sure the PortMaster can ping the nameserver being used
- Traceroute from the nameserver to customer and see where the packets go
* If you see DNS queries going out and coming back the chances are that the Win95 host is not processing the return packets or the packets are not being received by the Win95 host.
* If you see no DNS packets at all then the Win95 host is not sending DNS queries over its dialup adapter, or not generating DNS queries at all.
-jstorms@livingston.com