Question

Locked

TotalDeploy with a switch?

By lfruchter ·
Hello Sages,

Due to time and aspirational constraints, I am trying to preserve my ignorance of linux by using TotalDeploy to clone multiple workstations across a network. I'm proud of myself for getting this far:

1) I have a Dell PowerEdge 400sc running Win Server 2003 r2 set up as my TotalDeploy console and TFTP server with a static IP address. It holds the image to be cloned to the workstations.
2) I connect only a switch and workstation to the server so that my "network" (really a workgroup, right?) consists of those 3 machines, nothing else: no domain, no Internet, no router, no gateway, nuthin'.
3) I can successfully PXE boot a workstation into the TotalDeploy client environment.

The problems then kick in:
a) The workstation says it's connected to a TotalDeploy server but then also says it's waiting for a connection to the TotalDeploy server.
b) The TotalDeploy console on the server says that no workstations are connected.
c) Both machines just sit there, waiting to be introduced to each other somehow.

What have I left out? I have kept the services running on the 400sc to a minimum since it's only purpose is to clone workstations with TotalDeploy. I only have File Server and DHCP services running. Do I need to set up a domain? Are more services necessary for TotalDeploy to operate? I desperately need to get this working and TotalDeploy's tech support is sluggish and cryptic, to say the best.

Thanks for any help,
Lev in Brooklyn

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Well for starters

by robo_dev In reply to TotalDeploy with a switch ...

Can you ping the workstations from the server?

Do you have Windows Firewall enabled on the server?

I've never used PXE....how does it know what IP address to use, what default gateway to set?

If the PXE machines had a blank default gateway, they could not see the server.

Remember the server IP address must be the default gateway, the DHCP, the DNS, the whole shebang....

Have you tried booting from USB to see if that works?

Collapse -

Reponse To Answer

by lfruchter In reply to Well for starters

Thanks for your swift response, robo_dev. I forgot to mention that the server and the workstation can ping each other under normal conditions. Windows Firewall is disabled since there's no Internet involved.

The PXE-booted machine gets its IP address from the TFTP server. That part works fine.

TotalDeploy lets you export a client agent to a CD which boots the workstation without using PXE, but the results are exactly the same.

Thanks for the advice on DNS, gateway, etc. I will double check all that. Any other clues?

Much thanks, Lev

Collapse -

Couple of possibilities

by robo_dev In reply to TotalDeploy with a switch ...

Can you ping the workstations from the server?

Do you have Windows Firewall enabled on the server?

I've never used PXE....how does it know what IP address to use, what default gateway to set?

If the PXE machines had a blank default gateway, they could not see the server.

Remember the server IP address must be the default gateway, the DHCP, the DNS, the whole shebang....

Have you tried booting from USB to see if that works?

If you're working with PXE and TFTP, there should be nothing else you need, such as a domain.

I would guess that the totaldeploy starts as a service, and if it had any dependencies, it would complain about that. Check to see that the service is running

Back to Networks Forum
4 total posts (Page 1 of 1)  

Hardware Forums