serv said:
4strings,
What happens if you renew DHCP lease for Parallels Host-Guest Adapter via System Preferences? If that doesn't help issue 'ps axuww|grep prl_dhcpd' and see if it's running.
serv, i tried this out in the office and renewing the DHCP lease seemed to work to get an ip address assigned to the 'en2' address.
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::201:23ff:fe45:6789%en2 prefixlen 64 scopeid 0x8
inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
ether 00:01:23:45:67:89
media: autoselect status: active
supported media: autoselect
However, i still couldn't get wireless connectivity to work in xp. to debug further, i installed ethereal and captured packets on the parallels adapter interface. i saw that dhcp discover messages were going out but nothing is received back from the dhcp server.
so i ran 'tcpdump -i en1' to monitor the traffic on my wireless interface (airport). i saw the outbound dhcp discover packets as well as replies from the server, so it seems that the problem has to do with incoming packets not forwarded back to the en2 interface so windows network adapter can see it.
here's the output of tcpdump.
listening on en1, link-type EN10MB (Ethernet), capture size 4096 bytes
14:22:25.221689 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request from 00:d7:62:5b:92:04 (oui Unknown), length: 300
0x0000: 4500 0148 0112 0000 8011 3894 0000 0000
0x0010: ffff ffff 0044 0043 0134 86ea 0101 0600
0x0020: e7a8 2851 0000 8000 0000 0000 0000 0000
0x0030: 0000 0000 0000 0000 00d7 625b 9204 0000
0x0040: 0000 0000 0000 0000 0000 0000 0000 0000
0x0050: 0000 0000 0000 0000 0000 0000 0000 0000
0x0060: 0000 0000 0000 0000 0000 0000 0000 0000
0x0070: 0000 0000 0000 0000 0000 0000 0000 0000
0x0080: 0000 0000 0000 0000 0000 0000 0000 0000
0x0090: 0000 0000 0000 0000 0000 0000 0000 0000
0x00a0: 0000 0000 0000 0000 0000 0000 0000 0000
0x00b0: 0000 0000 0000 0000 0000 0000 0000 0000
0x00c0: 0000 0000 0000 0000 0000 0000 0000 0000
0x00d0: 0000 0000 0000 0000 0000 0000 0000 0000
0x00e0: 0000 0000 0000 0000 0000 0000 0000 0000
0x00f0: 0000 0000 0000 0000 0000 0000 0000 0000
0x0100: 0000 0000 0000 0000 6382 5363 3501 0174
0x0110: 0101 3d07 0100 d762 5b92 040c 0c63 6c69
0x0120: 6666 2d6d 6163 2d78 703c 084d 5346 5420
0x0130: 352e 3037 0b01 0f03 062c 2e2f 1f21 f92b
0x0140: ff00 0000 0000 0000
14:22:25.433348 IP 4strings.xxx.net.49531 > dc.xxx.net.domain: 58679+ PTR? 0.0.0.0.in-addr.arpa. (38)
0x0000: 4500 0042 7215 0000 4011 0f24 ac18 9137
0x0010: ac18 100a c17b 0035 002e 462a e537 0100
0x0020: 0001 0000 0000 0000 0130 0130 0130 0130
0x0030: 0769 6e2d 6164 6472 0461 7270 6100 000c
0x0040: 0001
14:22:25.435123 IP dc.xxx.net.domain > 4strings.xxx.net.49531: 58679 NXDomain* 0/1/0 (113)
0x0000: 4500 008d 25ad 0000 7e11 1d41 ac18 100a
0x0010: ac18 9137 0035 c17b 0079 7188 e537 8583
0x0020: 0001 0000 0001 0000 0130 0130 0130 0130
0x0030: 0769 6e2d 6164 6472 0461 7270 6100 000c
0x0040: 0001 0130 0769 6e2d 6164 6472 0461 7270
0x0050: 6100 0006 0001 0000 0e10 0031 0a64 636a
0x0060: 6e70 726d 7263 3104 6a6e 7072 036e 6574
0x0070: 0005 6164 6d69 6ec0 4b00 0000 0100 0003
0x0080: 8400 0002 5800 0151 8000 000e 10
14:22:26.450817 IP 4strings.xxx.net.49532 > dc.xxx.net.domain: 3551+ PTR? 10.16.24.172.in-addr.arpa. (43)
0x0000: 4500 0047 723a 0000 4011 0efa ac18 9137
0x0010: ac18 100a c17c 0035 0033 ec9a 0ddf 0100
0x0020: 0001 0000 0000 0000 0231 3002 3136 0232
0x0030: 3403 3137 3207 696e 2d61 6464 7204 6172
0x0040: 7061 0000 0c00 01
...
any thoughts on what could be wrong?
thanks.