Jump to content

Patrickp65

Members
  • Posts

    2
  • Joined

  • Last visited

Reputation

0 Neutral

About Patrickp65

Personal Information

  • Occupation
    ICT Operations Manager
  • Location
    Birmingham

Employer (optional)

  • Company Represented
    Tec-Heads
  1. Thanx Guys I Managed to find out the culprit!! Nic was picking up a 192.168 IP instead of one from the DHCP server:doh:, plus deleted and recreated Setup & packagebuilder accounts. Build process would only go so far so in the end I installed XP manually and then checked IP addie. Once IP renewed, recreated Builddisk and both machine built perfectly!!! Its true that more heads are better than one!!
  2. Hi all, I am sure that there is someone out there would can shed some light on my problem. I have a couple of workstations that I use to package build on. Up to this week there as not been a problem with them until a member of staff asked me to install some software. As I have not packaged built software for a few months and I could not remember if I have a clean image or not I decided to restore to my backed up clean image on the workstation.....Everything was going okay until this point: Found Network card (Accton EN1297D-TX) Testing network connection initialising TCP/IP via DHCP... Microsoft DOS TCP/IP 1.0a Could not locate Server...Could not resolve server name. This is usually a problem with the lmhosts file...blah blah blah. I have check the LMhost and it has the correct IP and server name ***-SR-001. The only way I can get the machine to join the domain is to install XP then "smartclient" it onto the network. Any Ideas???
×
×
  • Create New...