Ghost Solution Suite

 View Only

 DAgent Status: Connection Close, Session Terminated

  • User Created
  •   2
Christopher Kerry's profile image
Christopher Kerry posted Dec 11, 2024 04:13 PM

During the process of trying to connect a client to the Ghost server, the DAgent will change the status to Connection Close, Session Terminated, and the computer will restart. I am looking for someone who has seen this issue before and has a resolution or a way to look at logs to get a specific error I can look up for a resolution. 

We have tried

  • Testing with another client's computer
  • Restarted the server
  • Upgraded from Ghost Server 3.3. RU11 to 3.3 12

We have used this setup for the past year and have not had an issue until this week. 

  • The client computer boots and
  • Connects to the PXE server
  • Mounts network drive
  • Finds DAgent (6.9.6523)
  • Copies DAgent
  • Launches DAgent


Popup window "Symantec DAgent Serice
Fields that are filled out by the system

  • Status: Client Record Updated
  • Computer name: Correct
  • Ghost Solution address ( Correct IP address of server and port)
  • Interface (Client IP address)
  • Multicast (Connecting through TCP)
  • MAC Address (Correct MAC for client)

 
Then Status changes to: 

  • Connection Close, Session Terminated

See Screenshots below
See Specs below

We are running 
Server

  • All Ghost services are running on the same box
  • Ghost Solution Suite Server 3.3 12
  • Win OS = Windows Server 2022 Standard 21H2
  • PXE Server setup and enabled

On the client's computer

  • Secure boot is turned off
  • RAID is disabled


DHCP 

  • Via the network firewall

Screenshot of WinPE client on the client's computer

  1. GhostServer-Connection-Closed-Session-Teminated
  2. GhostServer_ClientRecordUpdated


PxeLog_Mtftp Logs after one of the connections failed

2024-12-11T20:10:36.474308Z ERROR tftp_server::connection: Error serving connection: PacketError(ErrCodeOutOfBounds)    
2024-12-11T20:10:36.882970Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.884097Z ERROR tftp_server::connection: Error message received with code NotDefined: "TFTP Aborted"    
2024-12-11T20:10:36.884190Z ERROR tftp_server::connection: Error serving connection: TftpError(NotDefined)    
2024-12-11T20:10:36.889124Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.889394Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.889618Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.889857Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.890108Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.890351Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.890562Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.890800Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.891143Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.891347Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.891591Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.891801Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.892100Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.892307Z ERROR tftp_server::server: Error creating path from filename: FileNotFound
2024-12-11T20:10:36.942995Z ERROR tftp_server::connection: Error message received with code NotDefined: "TFTP Aborted"    
2024-12-11T20:10:36.943070Z ERROR tftp_server::connection: Error serving connection: TftpError(NotDefined)    
2024-12-11T20:10:36.944011Z ERROR tftp_server::connection: Error message received with code NotDefined: "TFTP Aborted"    
2024-12-11T20:10:36.944075Z ERROR tftp_server::connection: Error serving connection: TftpError(NotDefined)    
2024-12-11T20:10:36.944708Z ERROR tftp_server::connection: Error message received with code NotDefined: "TFTP Aborted"    
2024-12-11T20:10:36.944765Z ERROR tftp_server::connection: Error serving connection: TftpError(NotDefined)    
2024-12-11T20:10:52.082254Z ERROR tftp_server::server: Error creating path from filename: FileNotFound

ScreenShot #1

GhostServer-Connection-Closed-Session-Teminated
Screenshot #2
GhostServer_ClientRecordUpdated
Scott Andreas's profile image
Broadcom Employee Scott Andreas

Hello Chrisopher

The issue you described is usually a case that there is no job assigned to the endpoint. If this is a unmanaged machine ( no agent installed ) then and there is no job assigned under 'Initial Deployment' and the computer will restart. Also if this is an unmanaged computer it is imperative that you delete the computer from under 'New Computer' each time. 

I will usually create a wait job or imaging job under 'Initial Deployment' by Double click on 'Initial Deployment' under the Jobs section > jobs tab and care a new job or pull in an existing job.

Also with computers using 'Initial Deployment' you can create a jobs list that gets displayed on the endpoint when it gets into Automation. Allowing the technican to pull down a desired image.

If you want to just hold open the 'Automation' environment create a wait job. This will hold open the agent allowing look peruse the environment or even push down a job from the console

Scott Andreas

Scott Andreas