Есть такая железка, держит один сегмент сети. Железка подключена к другому сегменту сети, в котором есть сервер DHCP. Настроен релэй. Из сегмента с длинком XP нормально получают свой адрес по DHCP. Однако клиенты с Win98 не получают нифига. Посмотрел сниффером, ответа не приходит просто вообще. Ниже расшифровки пакетов из Ethereal.
XP:
Код:
No. Time Source Destination Protocol Info
148 42.945568 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8d57aa6f
Frame 148 (342 bytes on wire, 342 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-24_f3:7f:13:35 (02:18:f3:7f:13:35), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
Message type: Boot Request (1)
Hardware type: Ethernet
Hardware address length: 6
Hops: 0
Transaction ID: 0x8d57aa6f
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
0... .... .... .... = Broadcast flag: Unicast
.000 0000 0000 0000 = Reserved flags: 0x0000
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Relay agent IP address: 0.0.0.0 (0.0.0.0)
Client MAC address: MS-NLB-PhysServer-24_f3:7f:13:35 (02:18:f3:7f:13:35)
Server host name not given
Boot file name not given
Magic cookie: (OK)
Option 53: DHCP Message Type = DHCP Discover
Option 116: DHCP Auto-Configuration (1 bytes)
Option 61: Client identifier
Hardware type: Ethernet
Client MAC address: MS-NLB-PhysServer-24_f3:7f:13:35 (02:18:f3:7f:13:35)
Option 12: Host Name = "winxp_client"
Option 60: Vendor class identifier = "MSFT 5.0"
Option 55: Parameter Request List
1 = Subnet Mask
15 = Domain Name
3 = Router
6 = Domain Name Server
44 = NetBIOS over TCP/IP Name Server
46 = NetBIOS over TCP/IP Node Type
47 = NetBIOS over TCP/IP Scope
31 = Perform Router Discover
33 = Static Route
249 = Classless static routes
43 = Vendor-Specific Information
End Option
Padding
На что DHCP нормально отвечает.
И вот Win98:
Код:
No. Time Source Destination Protocol Info
12 7.305769 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x9917682c
Frame 12 (342 bytes on wire, 342 bytes captured)
Ethernet II, Src: CadmusCo_29:58:38 (08:00:27:29:58:38), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
Message type: Boot Request (1)
Hardware type: Ethernet
Hardware address length: 6
Hops: 0
Transaction ID: 0x9917682c
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
0... .... .... .... = Broadcast flag: Unicast
.000 0000 0000 0000 = Reserved flags: 0x0000
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Relay agent IP address: 0.0.0.0 (0.0.0.0)
Client MAC address: CadmusCo_29:58:38 (08:00:27:29:58:38)
Server host name not given
Boot file name not given
Magic cookie: (OK)
Option 53: DHCP Message Type = DHCP Discover
Option 61: Client identifier
Hardware type: Ethernet
Client MAC address: CadmusCo_29:58:38 (08:00:27:29:58:38)
Option 12: Host Name = "USER"
Option 60: Vendor class identifier = "MSFT 98"
Option 55: Parameter Request List
1 = Subnet Mask
15 = Domain Name
3 = Router
6 = Domain Name Server
44 = NetBIOS over TCP/IP Name Server
46 = NetBIOS over TCP/IP Node Type
47 = NetBIOS over TCP/IP Scope
43 = Vendor-Specific Information
77 = User Class Information
End Option
Padding
Пакет уходит просто в никуда. В чем может быть проблема? Баг железки? Как побороть кроме сноса 98/железки?
Вход
Регистрация
FAQ
Поиск
