PXE boot error / Setup help

WTware network boot ways - bootable floppy, DOS, PXE-loaders, BootROM chips.
Post Reply
Combie81
Posts: 5
Joined: Thu May 24, 2018 4:23 pm

PXE boot error / Setup help

Post by Combie81 » Thu May 24, 2018 6:43 pm

Afternoon all,

I have a client that is looking to migrame to a full cloud solution with only thin clients left at each of their sites. I am hoping to re-use the existing PC's with no HDD and use PXE to boot to and RDS session on an azure based server. At the moment I am having trouble getting the boot image to d/l to the PC and getting TFTP errors where it times out.

Here is the H/W setup:
Client PC with PXE
>>
Draytek router onsite with "DHCP relay" set to azure server IP 1.1.1.1 (I've changed IP's as placeholders for simplicity)
>>
Azure server running Server 2016, Runs as a DC, No DHCP role, static IP 192.168.10.4, running WTware 5.8.20
>>
(Clients should be RDP'd to here once they get image) Azure server, RDS client for thinclients to connect to, static IP 192.168.10.6

What I've got so far:
The test client is getting an 192.168.10.xx address from WTware and are showing in the terminals options 3 - auto, 6 - auto, 666, 192.168.10.4, 67 - auto
TFTP, HTTP, DHCP services of WTware are all running
Terminal version shows MAC of the client and version 5.8.20
Boot type HTTP
Remote update files - Image generated and there are files in the folder

Client log:
14-06-57-789| [DHCP] Processing DHCPDISCOVER package...
14-06-57-789| [DHCP] Determine IP...
14-06-57-805| [DHCP] IP 192.168.10.21 for MAC xxxxxxxx determined from terminalDHCP parameters.
14-06-57-805| [DHCP] Sending ARP to check if IP 192.168.10.21 is busy...
14-06-58-102| [DHCP] Send DHCPOFFER IP: 192.168.10.21.
14-07-01-834| [DHCP] Processing DHCPREQUEST package...
14-07-01-834| [DHCP] Determine IP...
14-07-01-834| [DHCP] IP 192.168.10.21 for MAC xxxxxxxx determined from terminalDHCP parameters.
14-07-01-834| [DHCP] Stored in catalog IP 192.168.10.21 for MAC xxxxxxxx
14-07-01-897| [DHCP] Send DHCPACK.

Can anyone help and advise where I'm gonig wrong in the setup process/what I'm missing? Client stops with errors PXE-E11, PXE-E38.

If successful in getting this working I can then proceed to the client and purchase licences for all their terminals at all there stores accross the country.

Let me know if you need any logs/more info and I'll gladly provide them as I've been tearing my hair out trying to set this up.

Many thanks,

Steven

akatik
SUPPORT
SUPPORT
Posts: 265
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: PXE boot error / Setup help

Post by akatik » Thu May 24, 2018 7:30 pm

http://wtware.com/docs5/dhcp.html
last part "dhcp relay"

Combie81
Posts: 5
Joined: Thu May 24, 2018 4:23 pm

Re: PXE boot error / Setup help

Post by Combie81 » Fri May 25, 2018 6:05 pm

I'm still getting same error after setting up DHCP relay as suggested. Here is the DHCP server log from WTware(partial Mac/IP obfuscation):

15-47-49-757| select() worked, trying to get data by recvfrom()...
15-47-49-773| Received packet: 548 bytes from 92.26.xxxxx:67.
15-47-49-773| Source: 92.26.xxxxx Destination: 192.168.10.4.
15-47-49-773| Reading packet...
15-47-49-773| Reading received packet data...
15-47-49-773| Packet type is: DHCPDISCOVER
15-47-49-789| No ignore MACs listed.
15-47-49-789| List of request parameters: 1 2 3 4 5 6 11 12 13 15 16 17 18 22 23 28 40 41 42 43 50 51 54 58 59 60 66 67 128 129 130 131
15-47-49-804| Checking packet...
15-47-49-804| Print packet data...
15-47-49-804| Bootstrap Protocol
15-47-49-820| Message type: bootp BOOTREQUEST (1)
15-47-49-820| Hardware type: Ethernet 10Mb
15-47-49-820| Hardware address length: 6
15-47-49-820| Hops: 0
15-47-49-836| Transaction ID: 0xb7bfc5da
15-47-49-836| Seconds elapsed: 1024
15-47-49-836| Bootp flags: 0x0080
15-47-49-836| Client IP address (ciaddr): 0.0.0.0
15-47-49-852| Your (client) IP address (yiaddr): 0.0.0.0
15-47-49-852| Server IP address (siaddr): 0.0.0.0
15-47-49-868| Relay agent IP address (giaddr): 92.26.xxxxx
15-47-49-868| Client MAC address (chaddr): D4:BE:D9:C5:xxxxx
15-47-49-868| Server host:
15-47-49-868| Boot file name:
15-47-49-882| Magic cookie: (OK)
15-47-49-882| Option: (t=53, l=1) DHCP_OPTION_MESSAGE_TYPE = 1
15-47-49-882| Option: (t=55, l=36) DHCP_OPTION_PARAMETER_REQUEST_LIST = 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87
15-47-49-882| Option: (t=57, l=2) DHCP_OPTION_MESSAGE_LENGTH = 1260
15-47-49-898| Option: (t=97, l=17) Option: 97 = 00 44 45 4c 4c 37 00 10 4b 80 30 c6 c0 4f 42 35 4a, 1279607808 (0x4c454400),
15-47-49-898| Option: (t=93, l=2) Option: 93 = 00 00, 0 (0x00000000),
15-47-49-914| Option: (t=94, l=3) Option: 94 = 01 02 01, 66049 (0x00010201),
15-47-49-914| Option: (t=60, l=32) DHCP_OPTION_CLIENT_CLASS_INFO = PXEClient:Arch:00000:UNDI:002001
15-47-49-914| End Option
15-47-49-914| [D4:BE:D9:C5:xxxxx] Processing DHCPDISCOVER package...
15-47-49-914| Server determines IP for the client...
15-47-49-929| [D4:BE:D9:C5:xxxxx] Determine IP...
15-47-49-929| Search in ClientIP packet options.
15-47-49-929| Search in terminalDHCP directory.
15-47-49-929| [D4:BE:D9:C5:xxxxx] IP 192.168.10.20 for MAC D4:BE:D9:C5:xxxxx determined from terminalDHCP parameters.
15-47-49-945| [D4:BE:D9:C5:xxxxx] Sending ARP to check if IP 192.168.10.20 is busy...
15-47-49-945| Checking ARP table to find IPNetRow for our IP...
15-47-49-945| getIPNetTable returned 0.
15-47-49-961| Found ipNetRow for IP 192.168.10.20 (MAC 00:00:00:00:00:00). Delete it.
15-47-49-961| Sending ARP request for IP 192.168.10.20 (MAC D4:BE:D9:C5:xxxxx, server IP 192.168.10.4)
15-47-50-273| Sending ARP ended by WAIT_TIMEOUT. IP is free. Thread id 5240.
15-47-50-273| [D4:BE:D9:C5:xxxxx] Send DHCPOFFER IP: 192.168.10.20.
15-47-50-273| We are sending packet from 192.168.10.4. Client IP = 192.168.10.20
15-47-50-273| Print packet data...
15-47-50-289| Bootstrap Protocol
15-47-50-289| Message type: bootp BOOTREPLY (2)
15-47-50-289| Hardware type: Ethernet 10Mb
15-47-50-304| Hardware address length: 6
15-47-50-304| Hops: 0
15-47-50-304| Transaction ID: 0xb7bfc5da
15-47-50-304| Seconds elapsed: 0
15-47-50-320| Bootp flags: 0x0080
15-47-50-320| Client IP address (ciaddr): 0.0.0.0
15-47-50-320| Your (client) IP address (yiaddr): 192.168.10.20
15-47-50-320| Server IP address (siaddr): 192.168.10.4
15-47-50-320| Relay agent IP address (giaddr): 92.26.xxxxx
15-47-50-336| Client MAC address (chaddr): D4:BE:D9:C5:xxxxx
15-47-50-336| Server host:
15-47-50-351| Boot file name: 5.8.20\wtware.pxe
15-47-50-351| Magic cookie: (OK)
15-47-50-351| Option: (t=53, l=1) DHCP_OPTION_MESSAGE_TYPE = 2
15-47-50-351| Option: (t=54, l=4) DHCP_OPTION_SERVER_IDENTIFIER = c0 a8 0a 04, 67807424 (0x040aa8c0),
15-47-50-351| Option: (t=1, l=4) DHCP_OPTION_SUBNET_MASK = 255.255.255.0
15-47-50-367| Option: (t=26, l=2) DHCP_OPTION_MTU = 1500
15-47-50-367| Option: (t=66, l=13) DHCP_OPTION_TFTP_SERVER_NAME = 192.168.10.4
15-47-50-367| Option: (t=67, l=18) DHCP_OPTION_TFTP_BOOTFILE_NAME = 5.8.20\wtware.pxe
15-47-50-382| Option: (t=3, l=4) DHCP_OPTION_ROUTER_ADDRESS = 192.168.12.1
15-47-50-382| Option: (t=6, l=0) DHCP_OPTION_DOMAIN_NAME_SERVERS =
15-47-50-382| Option: (t=51, l=4) DHCP_OPTION_LEASE_TIME = -1
15-47-50-398| End Option
15-47-50-398| Sending packet: 309 bytes to 92.26.xxxxx:67.
15-47-50-398| [92.26.xxxxx] Sent 309 bytes to 92.26.xxxxx:67.
15-47-53-821| select() worked, trying to get data by recvfrom()...
15-47-53-836| Received packet: 548 bytes from 92.26.xxxxx:67.
15-47-53-836| Source: 92.26.xxxxx Destination: 192.168.10.4.
15-47-53-836| Reading packet...
15-47-53-836| Reading received packet data...
15-47-53-836| Packet type is: DHCPREQUEST
15-47-53-868| No ignore MACs listed.
15-47-53-868| List of request parameters: 1 2 3 4 5 6 11 12 13 15 16 17 18 22 23 28 40 41 42 43 50 51 54 58 59 60 66 67 128 129 130 131
15-47-53-868| Requested IP is: 192.168.10.20
15-47-53-868| Checking packet...
15-47-53-883| Print packet data...
15-47-53-883| Bootstrap Protocol
15-47-53-883| Message type: bootp BOOTREQUEST (1)
15-47-53-883| Hardware type: Ethernet 10Mb
15-47-53-883| Hardware address length: 6
15-47-53-899| Hops: 0
15-47-53-899| Transaction ID: 0xb7bfc5da
15-47-53-914| Seconds elapsed: 1024
15-47-53-914| Bootp flags: 0x0080
15-47-53-914| Client IP address (ciaddr): 0.0.0.0
15-47-53-914| Your (client) IP address (yiaddr): 0.0.0.0
15-47-53-930| Server IP address (siaddr): 0.0.0.0
15-47-53-930| Relay agent IP address (giaddr): 92.26.xxxxx
15-47-53-930| Client MAC address (chaddr): D4:BE:D9:C5:xxxxx
15-47-53-930| Server host:
15-47-53-930| Boot file name:
15-47-53-946| Magic cookie: (OK)
15-47-53-946| Option: (t=53, l=1) DHCP_OPTION_MESSAGE_TYPE = 3
15-47-53-961| Option: (t=50, l=4) DHCP_OPTION_REQUESTED_ADDRESS = 192.168.10.20
15-47-53-961| Option: (t=55, l=36) DHCP_OPTION_PARAMETER_REQUEST_LIST = 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87
15-47-53-961| Option: (t=57, l=2) DHCP_OPTION_MESSAGE_LENGTH = 1260
15-47-53-961| Option: (t=54, l=4) DHCP_OPTION_SERVER_IDENTIFIER = c0 a8 0a 04, 67807424 (0x040aa8c0),
15-47-53-977| Option: (t=97, l=17) Option: 97 = 00 44 45 4c 4c 37 00 10 4b 80 30 c6 c0 4f 42 35 4a, 1279607808 (0x4c454400),
15-47-53-977| Option: (t=93, l=2) Option: 93 = 00 00, 0 (0x00000000),
15-47-53-977| Option: (t=94, l=3) Option: 94 = 01 02 01, 66049 (0x00010201),
15-47-53-977| Option: (t=60, l=32) DHCP_OPTION_CLIENT_CLASS_INFO = PXEClient:Arch:00000:UNDI:002001
15-47-53-993| End Option
15-47-53-993| [D4:BE:D9:C5:xxxxx] Processing DHCPREQUEST package...
15-47-54-009| Server determines IP for the client...
15-47-54-009| [D4:BE:D9:C5:xxxxx] Determine IP...
15-47-54-009| Search in ClientIP packet options.
15-47-54-009| Search in terminalDHCP directory.
15-47-54-024| [D4:BE:D9:C5:xxxxx] IP 192.168.10.20 for MAC D4:BE:D9:C5:xxxxx determined from terminalDHCP parameters.
15-47-54-024| [D4:BE:D9:C5:xxxxx] Stored in catalog IP 192.168.10.20 for MAC D4:BE:D9:C5:xxxxx
15-47-54-024| [D4:BE:D9:C5:xxxxx] Send DHCPACK.
15-47-54-039| We are sending packet from 192.168.10.4. Client IP = 192.168.10.20
15-47-54-039| Print packet data...
15-47-54-039| Bootstrap Protocol
15-47-54-055| Message type: bootp BOOTREPLY (2)
15-47-54-055| Hardware type: Ethernet 10Mb
15-47-54-055| Hardware address length: 6
15-47-54-055| Hops: 0
15-47-54-071| Transaction ID: 0xb7bfc5da
15-47-54-071| Seconds elapsed: 0
15-47-54-071| Bootp flags: 0x0080
15-47-54-071| Client IP address (ciaddr): 0.0.0.0
15-47-54-071| Your (client) IP address (yiaddr): 192.168.10.20
15-47-54-071| Server IP address (siaddr): 192.168.10.4
15-47-54-071| Relay agent IP address (giaddr): 92.26.xxxxx
15-47-54-071| Client MAC address (chaddr): D4:BE:D9:C5:xxxxx
15-47-54-086| Server host:
15-47-54-086| Boot file name: 5.8.20\wtware.pxe
15-47-54-086| Magic cookie: (OK)
15-47-54-086| Option: (t=53, l=1) DHCP_OPTION_MESSAGE_TYPE = 5
15-47-54-102| Option: (t=54, l=4) DHCP_OPTION_SERVER_IDENTIFIER = c0 a8 0a 04, 67807424 (0x040aa8c0),
15-47-54-102| Option: (t=1, l=4) DHCP_OPTION_SUBNET_MASK = 255.255.255.0
15-47-54-102| Option: (t=26, l=2) DHCP_OPTION_MTU = 1500
15-47-54-102| Option: (t=66, l=13) DHCP_OPTION_TFTP_SERVER_NAME = 192.168.10.4
15-47-54-102| Option: (t=67, l=18) DHCP_OPTION_TFTP_BOOTFILE_NAME = 5.8.20\wtware.pxe
15-47-54-102| Option: (t=3, l=4) DHCP_OPTION_ROUTER_ADDRESS = 192.168.12.1
15-47-54-102| Option: (t=6, l=0) DHCP_OPTION_DOMAIN_NAME_SERVERS =
15-47-54-102| Option: (t=51, l=4) DHCP_OPTION_LEASE_TIME = -1
15-47-54-102| End Option
15-47-54-102| Sending packet: 309 bytes to 92.26.xxxxx:67.
15-47-54-118| [92.26.xxxxx] Sent 309 bytes to 92.26.xxxxx:67.

akatik
SUPPORT
SUPPORT
Posts: 265
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: PXE boot error / Setup help

Post by akatik » Mon May 28, 2018 10:02 am

To obtain help, you should overload me with information. Start from drawing network scheme with all IP addresses on it.

Combie81
Posts: 5
Joined: Thu May 24, 2018 4:23 pm

Re: PXE boot error / Setup help

Post by Combie81 » Mon Jun 04, 2018 5:58 pm

Afternoon, Here's a rough drawing of the setup that we will have in place for each site that will connect ot the central Azure servers.
Attachments
GW Diag.jpg
GW Diag.jpg (66.68 KiB) Viewed 181 times

aka
SUPPORT
SUPPORT
Posts: 628
Joined: Fri Dec 03, 2004 2:05 pm
Contact:

Re: PXE boot error / Setup help

Post by aka » Mon Jun 04, 2018 6:07 pm

This line is wrong:

Code: Select all

15-47-50-273| [D4:BE:D9:C5:xxxxx] Send DHCPOFFER IP: 192.168.10.20.
DHCP offer 192.168.10.20 for terminal.
DHCP should offer 192.168.12.x for terminal in 192.168.12.x network. Not 192.168.10.x.

http://wtware.com/docs5/dhcp.html
last part "dhcp relay".
Digit (3).
Change IP to 192.168.12.x

Combie81
Posts: 5
Joined: Thu May 24, 2018 4:23 pm

Re: PXE boot error / Setup help

Post by Combie81 » Mon Jun 04, 2018 7:15 pm

Firstly thank you for all you prompt help - it is VERY gtreatly appreciated.

Ok I think I've made all the right changes but still having no luck sadly. Here are a whole new set of images/logs to go with the setup exactly as it is - anythigng else you need I will get to you.
Attachments
Client setting.jpg
Client setting.jpg (145.07 KiB) Viewed 177 times
WTware_DHCP_2018-06-04_17-04-02.txt
(17.48 KiB) Downloaded 12 times
GW Diag with IP.jpg
GW Diag with IP.jpg (66.86 KiB) Viewed 177 times

Combie81
Posts: 5
Joined: Thu May 24, 2018 4:23 pm

Re: PXE boot error / Setup help

Post by Combie81 » Mon Jun 04, 2018 7:15 pm

Another 2 images:
Attachments
client screen 20180604_170259.jpg
client screen 20180604_170259.jpg (205.82 KiB) Viewed 177 times
DHCP Range.jpg
DHCP Range.jpg (119.44 KiB) Viewed 177 times

akatik
SUPPORT
SUPPORT
Posts: 265
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: PXE boot error / Setup help

Post by akatik » Mon Jun 04, 2018 8:24 pm

It's wrong network design. Different networks splitted by routers can not have the same network address 192.168.10.0.

Fraal
Posts: 9
Joined: Mon Oct 16, 2017 7:20 am

Re: PXE boot error / Setup help

Post by Fraal » Tue Jun 05, 2018 7:54 am

This would work if you setup a site-to-site VPN, you can do this by using the Azure VPN gateway to the draytek.
This would fix the PXE boot side also as multicast packets will not route between networks. You'll require a router which can support multicast routing, not sure if draytek can or not.

akatik
SUPPORT
SUPPORT
Posts: 265
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: PXE boot error / Setup help

Post by akatik » Tue Jun 05, 2018 9:08 am

1. Azure manual tells to use the same network addresses? Show me it.
2. Will "ping 192.168.10.4" go from windows computer in "Local User Devices"?

Post Reply