Jump to content

magikmike

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by magikmike

  1. seems it's definitely the switch - all the procurve 2626 switches we have on site behave exactly the same, and a firmware update hasnt fixed it... not impressed!!!
  2. I've been doing some more testing on-site, and found that anything behind a HP Procurve 2626 switch fails to PXE boot correctly. I looked up the latest firmware, and there in the resolved issues of the release notes it states "DHCP Snooping (PR_0000044797) - When a PXE protocol DHCP-offer packet is sent from a boot server through a trusted port, the switch drops the packet." looks like i'm upgrading firmware tomorrow!
  3. Thanks for your quick replies! F8 doesnt work, as i cant get that far. STP isnt enabled on any of our switches, and i even double checked the switches between this location and the server. I also already have DHCP options set for server and boot file name :-(
  4. Hopefully someone who's used WDS can help me out with this one... I'm beginning a deployment of windows 7, and found that some of our machines just cannot boot into the WDS environment. It seems location specific rather than related to the hardware of the machine - for example in one lab where this error occurs I brought a machine back to my office where it worked perfectly! The machines all get DHCP data correctly, and load the wdsnbp.com file they're directed to in DNS. They then state "DHCP Referral" before they then hang for a few seconds then say "no response from windows deployment services server" and offer the usual press F12 to boot - pressing F12 just gets a winPE error of cannot find boot file. The machines that boot successfully dont say anything about a "DHCP Referral" as it seems they discover the WDS server directly. I'm not sure why this happens - we don't use VLANs, and everything is in a single subnet (although the servers are above the DHCP address range, they're still part of the same subnet) Thanks for your help!!
  5. Thanks for your reply. We had *.apple.com whitelisted, but have now done the same for all the itunes addresses and the issue appears to be resolved. Thanks for your help!
  6. Hi AMLightfoot. The apple support doc you linked to is the same one i was working from. I've opened the ports as it suggests, but it seems to make no difference. Calls can be placed but they never "connect" when answered. We're a private school, so no LEA upstream firewall - direct web connection via BT leased line.
  7. Hi All We've recently discovered that our smoothwall appliance is not allowing facetime calls through, even though we have the correct exceptions in place in the firewall. Nothing appears to have changed in our config, nor does the apple support page we followed to configure it mention any changes... it's just stopped working! Any help or similar experiences would be useful Thanks, Mike
×
×
  • Create New...