Strange issues.
Warning: Today's entry contains copious techobabble. Reader discretion is advised.
Either I'm missing something, or the customer is lying.
The client is reporting that on their test network, that has three to five computers and a router serving dhcp addresses, but no internet access and no dns server entries being handed out by the router. They say that on this network, the licensing service for GURU won't start.
I tried reproducing this on an isolated network at the office. Two Windows desktops and a switch between them. I sneaker-netted a DHCP server to one of them, setting it up to hand out IP addresses, but not DNS information. I was able to stop, start, and restart the service on the DHCP client. I was able to connect the GURU client on the DHCP server to the GURU Service on the DHCP client with no issues. The program functioned as designed. I was unable to reproduce the error.
Before I installed the DHCP server, I set both workstations to be DHCP clients. With no DHCP server, Windows assigned itself an address in the 169.254.0.0 network. The two could talk to eachother and the GURU client/server worked fine.
I told my boss about my results, and he seemed concerned that it wasn't a faithful replication because I had a switch in there, not a router handing out DHCP addresses. There are no spare routers laying around the office, that I know of anyway, but I happen to have a spare router at home. It's the old Linksys BEFSR41 I had for years that finally got replaced by a WRT54G when I accidentally fried the WEP by plugging in the wrong power supply after the move out here.
I doubt the results will be any different.
Either I'm missing something, or the customer is lying.
The client is reporting that on their test network, that has three to five computers and a router serving dhcp addresses, but no internet access and no dns server entries being handed out by the router. They say that on this network, the licensing service for GURU won't start.
I tried reproducing this on an isolated network at the office. Two Windows desktops and a switch between them. I sneaker-netted a DHCP server to one of them, setting it up to hand out IP addresses, but not DNS information. I was able to stop, start, and restart the service on the DHCP client. I was able to connect the GURU client on the DHCP server to the GURU Service on the DHCP client with no issues. The program functioned as designed. I was unable to reproduce the error.
Before I installed the DHCP server, I set both workstations to be DHCP clients. With no DHCP server, Windows assigned itself an address in the 169.254.0.0 network. The two could talk to eachother and the GURU client/server worked fine.
I told my boss about my results, and he seemed concerned that it wasn't a faithful replication because I had a switch in there, not a router handing out DHCP addresses. There are no spare routers laying around the office, that I know of anyway, but I happen to have a spare router at home. It's the old Linksys BEFSR41 I had for years that finally got replaced by a WRT54G when I accidentally fried the WEP by plugging in the wrong power supply after the move out here.
I doubt the results will be any different.