Tried DHCP, now can't get static IP connection

Old Forum

posted May 22 '19 at 1:59 pm

One was running fine with a static IP, either communicating using telnet by Ethernet to a terminal emulator program on my PC or communicating by serial port.

It reported temperatures all last night by the telnet connection. This morning I tried (by browsing to its web page) setting it to Auto addressing (they don't like handing out static IPs on our company network) and did not succeed. So I tried to set it back to the static IP I had been using, but have not been able to communicate via Ethernet since.

Two of us carefully went through the procedure in the manual (starting on page 179 and particularly pages 185-186) for "Network Connection - Static IP address". Communicating by serial port we can get the unit to report back it is using the address we want, which also appears in its LCD display.

The green Ethernet LED stays lit and the yellow one lights sporadically, which looks right. But we can't open its web page, or telnet to it, or ping it. We have a DT800 sitting next to it and wired through the same switch, and we still telnet and ping it just fine.

We've tried changing switch ports, pinging from another PC, SINGLEPUSH, INIT, HRESET, FACTORYDEFAULTS, and anything else we could think of. So we brought out our other DT80 and tried all the same things with it.

Note, we had not been using this one with a static IP, and don't remember the history of its Ethernet settings - however we saw it was set to Auto addressing. We are having the same experience with it.

One mystery is that several times the units unexpectedly reverted to Auto setting, and we often find that the LCD display and the reply to PROFILE ETHERNET disagree with one another. We have not figured out what we are doing to trigger this (though obviously FACTORYDEFAULTS does it).

However, the unit I am connected to now (via serial) has been consistently reporting the static address and other profile settings we want, for the past half hour, both by serial port and by its LCD (except temporarily whenever we do FACTORYDEFAULTS until we change it).

Here's some captured text from the serial terminal session to verify what we're doing:

FACTORYDEFAULTS 
dataTaker 80 E10 - Command error at column 1 [ <err>FACTORYD ] 

DT80> 
DT80> FACTORYDEFAULTS 
DT80> PROFILE ETHERNET 
[ETHERNET] 
  ENABLE = YES 
  IP_ADDRESS = AUTO 
  SUBNET_MASK = 255.255.255.0 
  GATEWAY = 0.0.0.0 

DT80> PROFILE ETHERNET IP_ADDRESS=157.204.37.45 
DT80> PROFILE ETHERNET SUBNET_MASK=255.255.255.0 
DT80> PROFILE ETHERNET GATEWAY=154.207.37.1 
DT80> PROFILE NETWORK DNS_SERVER_1=157.204.84.63 
DT80> PROFILE NETWORK DNS_SERVER_2=157.204.7.84 

DT80> PROFILE ETHERNET 
[ETHERNET] 
  ENABLE = YES 
*IP_ADDRESS = 157.204.37.45 
  SUBNET_MASK = 255.255.255.0 
*GATEWAY = 154.207.37.1 

DT80> PROFILE NETWORK 
[NETWORK] 
*DNS_SERVER_1 = 157.204.84.63 
*DNS_SERVER_2 = 157.204.7.84 

DT80> 
DT80> PROFILE ETHERNET 
[ETHERNET] 
  ENABLE = YES 
*IP_ADDRESS = 157.204.37.45 
  SUBNET_MASK = 255.255.255.0 
*GATEWAY = 154.207.37.1 
DT80> INIT 
Initializing...Done. 

DT80> PROFILE ETHERNET 
[ETHERNET] 
  ENABLE = YES 
*IP_ADDRESS = 157.204.37.45 
  SUBNET_MASK = 255.255.255.0 
*GATEWAY = 154.207.37.1 

DT80> HRESET 
DT80> PROFILE ETHERNET 
[ETHERNET] 
  ENABLE = YES 
*IP_ADDRESS = 157.204.37.45 
  SUBNET_MASK = 255.255.255.0 
*GATEWAY = 154.207.37.1 

DT80> STATUS 
dataTaker 80 E10 - Command error at column 1 [ <err>STATUS ] 

DT80> STATUS 
dataTaker 80 Version 8.08.0001 
Flash 2010/11/16 13:54:46 none,S Scan 
Schedules Active,Halted 0,0 
Alarms/Ifs Active,Halted 0 
Polynomials/Spans Defined none,none 
Scan Schedules LOGON,LOGOFF 
114750,11944 Internal kB free, used 0,0 External kB free, used 
/C/d/E/f/h/i/K/l/M/N/R/S/t/U/w/x/Z 

DT80>

At several points during the above session, we tried "ping 154.207.37.45" and got four "Request timed out" replies. I just did it again, same result, and also see DT80 LCD display currently reads: Eth IP: Manual 157.204.37.45.

We don't think it can be an address conflict, because nothing else ever replies back to our pings, and the static IP is officially ours. What are we doing wrong? This is making us crazy!

We are having what seems like the same trouble with two DT80's running Version 8.08.0001. It seems as though once they have been set to use Auto IP addressing, we can't get them set back to a static IP. One was running fine with a static IP, either communicating using telnet by Ethernet to a terminal emulator program on my PC or communicating by serial port. It reported temperatures all last night by the telnet connection. This morning I tried (by browsing to its web page) setting it to Auto addressing (they don't like handing out static IPs on our company network) and did not succeed. So I tried to set it back to the static IP I had been using, but have not been able to communicate via Ethernet since. Two of us carefully went through the procedure in the manual (starting on page 179 and particularly pages 185-186) for "Network Connection - Static IP address". Communicating by serial port we can get the unit to report back it is using the address we want, which also appears in its LCD display. The green Ethernet LED stays lit and the yellow one lights sporadically, which looks right. But we can't open its web page, or telnet to it, or ping it. We have a DT800 sitting next to it and wired through the same switch, and we still telnet and ping it just fine. We've tried changing switch ports, pinging from another PC, SINGLEPUSH, INIT, HRESET, FACTORYDEFAULTS, and anything else we could think of. So we brought out our other DT80 and tried all the same things with it. Note, we had not been using this one with a static IP, and don't remember the history of its Ethernet settings - however we saw it was set to Auto addressing. We are having the same experience with it. One mystery is that several times the units unexpectedly reverted to Auto setting, and we often find that the LCD display and the reply to PROFILE ETHERNET disagree with one another. We have not figured out what we are doing to trigger this (though obviously FACTORYDEFAULTS does it). However, the unit I am connected to now (via serial) has been consistently reporting the static address and other profile settings we want, for the past half hour, both by serial port and by its LCD (except temporarily whenever we do FACTORYDEFAULTS until we change it). Here's some captured text from the serial terminal session to verify what we're doing: ```` FACTORYDEFAULTS dataTaker 80 E10 - Command error at column 1 [ <err>FACTORYD ] DT80> DT80> FACTORYDEFAULTS DT80> PROFILE ETHERNET [ETHERNET] ENABLE = YES IP_ADDRESS = AUTO SUBNET_MASK = 255.255.255.0 GATEWAY = 0.0.0.0 DT80> PROFILE ETHERNET IP_ADDRESS=157.204.37.45 DT80> PROFILE ETHERNET SUBNET_MASK=255.255.255.0 DT80> PROFILE ETHERNET GATEWAY=154.207.37.1 DT80> PROFILE NETWORK DNS_SERVER_1=157.204.84.63 DT80> PROFILE NETWORK DNS_SERVER_2=157.204.7.84 DT80> PROFILE ETHERNET [ETHERNET] ENABLE = YES *IP_ADDRESS = 157.204.37.45 SUBNET_MASK = 255.255.255.0 *GATEWAY = 154.207.37.1 DT80> PROFILE NETWORK [NETWORK] *DNS_SERVER_1 = 157.204.84.63 *DNS_SERVER_2 = 157.204.7.84 DT80> DT80> PROFILE ETHERNET [ETHERNET] ENABLE = YES *IP_ADDRESS = 157.204.37.45 SUBNET_MASK = 255.255.255.0 *GATEWAY = 154.207.37.1 DT80> INIT Initializing...Done. DT80> PROFILE ETHERNET [ETHERNET] ENABLE = YES *IP_ADDRESS = 157.204.37.45 SUBNET_MASK = 255.255.255.0 *GATEWAY = 154.207.37.1 DT80> HRESET DT80> PROFILE ETHERNET [ETHERNET] ENABLE = YES *IP_ADDRESS = 157.204.37.45 SUBNET_MASK = 255.255.255.0 *GATEWAY = 154.207.37.1 DT80> STATUS dataTaker 80 E10 - Command error at column 1 [ <err>STATUS ] DT80> STATUS dataTaker 80 Version 8.08.0001 Flash 2010/11/16 13:54:46 none,S Scan Schedules Active,Halted 0,0 Alarms/Ifs Active,Halted 0 Polynomials/Spans Defined none,none Scan Schedules LOGON,LOGOFF 114750,11944 Internal kB free, used 0,0 External kB free, used /C/d/E/f/h/i/K/l/M/N/R/S/t/U/w/x/Z DT80> ```` At several points during the above session, we tried "ping 154.207.37.45" and got four "Request timed out" replies. I just did it again, same result, and also see DT80 LCD display currently reads: **Eth IP: Manual 157.204.37.45**. We don't think it can be an address conflict, because nothing else ever replies back to our pings, and the static IP is officially ours. What are we doing wrong? This is making us crazy!

Roger

posted May 22 '19 at 2:00 pm

Hi Chris B,

The bit that is worrying is not getting a response to the ping. Ping is a very low level network function and not responding indicates problems with the network.

The fact that the DHCP didn't work. First what version of firmware? Check the cabling to the switch, subnet masks and gateway (if used).

Try connecting a computer to the same switch and let it get an IP address. Once it has open a command window and type in the command IPCONFIG /All
This will return the network configuration on the computer. Then check the network settings in the DT80's match.

Cheers,
Roger

Hi Chris B, The bit that is worrying is not getting a response to the ping. Ping is a very low level network function and not responding indicates problems with the network. The fact that the DHCP didn't work. First what version of firmware? Check the cabling to the switch, subnet masks and gateway (if used). Try connecting a computer to the same switch and let it get an IP address. Once it has open a command window and type in the command IPCONFIG /All This will return the network configuration on the computer. Then check the network settings in the DT80's match. Cheers, Roger

Pending draft

Selected posts

Confirm move posts

Insufficient permissions

Select a different topic

Confirm selection

Edit history