Unsolved
This post is more than 5 years old
1 Rookie
•
8 Posts
0
95652
June 26th, 2014 07:00
Optiplex 3020 Network Connectivity Issues
Hello:
I have a customer who is in the process of deploying approx 20 Optiplex 3020 SFF machines. All are configured and tested at her desk before deploying and network connectivity is tested.
One of the batch (configured identical to the rest) will not connect. When this happens the Link LED on the NIC is solid and the traffic LED flashes as if connected. The unit was tried at a proved working wall jack and the same symptom.
BIOS version A03, latest drivers installed from the DELL download site.
The customer brought the unit back to her testing area, the unit connected momentarily and then blue screened.
Ran the DELL diags over the course of 2 days and at one point the diags stopped and received this message:
Continued on with the diags and when i attempted to exit the diags to check the BIOS errorlog, received the same message again.
Any suggestions on what might be causing these issues??? If it's hardware what is it?
thanx
dave
0 events found
speedstep
9 Legend
•
47K Posts
0
June 26th, 2014 08:00
The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
DJ454 24 KEYBOARD, 104, UNITED STATES, KB212B, W8, PRIMAX ELECTRONICS LTD
V3171 24 ASSEMBLY, DVD+/-RW, 8, 12.7T, HLD, ACROSS LINE OF BUSINESS
34VD5 24 ASSEMBLY, CHASSIS, PWA INTEGRATED, SLIM FORM FACTOR, 3020, APFC
9RRC7 24 Kit, Mouse, Universal Serial Bus, Point Of Sale, Logitech, MS111
MX4D1 24 CARD (CIRCUIT), GRAPHICS, 1G, OUGA10, LOOP
531R8 24 DUAL IN-LINE MEMORY MODULE, 4G, 1600, 1RX8, 4G, DDR3, NU
RD6XX 24 Assembly, Heatsink, Fan, Slim Form Factor, Performance, 9020
9CF26 24 HARD DRIVE, 500G, S3, 7.2K, 512E, SGT-PHAR
5GDM4 24 PROCESSOR, HSL, I5-4570, 3.2, 86W, 4C, L
5120P 24 CORD, POWER, 125V, 6FT, SPT2, UNSHIELDED
0U615 24 SWITCH/SWITCHING, PUSHBUTTON, NO CONTROLLER/WITH CABLES, RAMJET
8001 (0x1F41)
The file replication service API was called incorrectly.
FRS_ERR_STARTING_SERVICE
8002 (0x1F42)
The file replication service cannot be started.
FRS_ERR_STOPPING_SERVICE
8003 (0x1F43)
The file replication service cannot be stopped.
FRS_ERR_INTERNAL_API
8004 (0x1F44)
The file replication service API terminated the request. The event log may have more information.
FRS_ERR_INTERNAL
8005 (0x1F45)
The file replication service terminated the request. The event log may have more information.
FRS_ERR_SERVICE_COMM
8006 (0x1F46)
The file replication service cannot be contacted. The event log may have more information.
FRS_ERR_INSUFFICIENT_PRIV
8007 (0x1F47)
The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.
FRS_ERR_AUTHENTICATION
8008 (0x1F48)
The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
FRS_ERR_PARENT_INSUFFICIENT_PRIV
8009 (0x1F49)
The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information.
FRS_ERR_PARENT_AUTHENTICATION
8010 (0x1F4A)
The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information.
FRS_ERR_CHILD_TO_PARENT_COMM
8011 (0x1F4B)
The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.
FRS_ERR_PARENT_TO_CHILD_COMM
8012 (0x1F4C)
The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information.
FRS_ERR_SYSVOL_POPULATE
8013 (0x1F4D)
The file replication service cannot populate the system volume because of an internal error. The event log may have more information.
FRS_ERR_SYSVOL_POPULATE_TIMEOUT
8014 (0x1F4E)
The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.
FRS_ERR_SYSVOL_IS_BUSY
8015 (0x1F4F)
The file replication service cannot process the request. The system volume is busy with a previous request.
FRS_ERR_SYSVOL_DEMOTE
8016 (0x1F50)
The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.
FRS_ERR_INVALID_SERVICE_PARAMETER
8017 (0x1F51)
The file replication service detected an invalid parameter.
File Replication Service (FRS) cannot be used for replicating Distributed File System (DFS) folders or custom (non-SYSVOL) data. A Windows Server 2008 R2 domain controller can still use FRS to replicate the contents of the SYSVOL share in a domain that uses FRS for replicating the SYSVOL share between domain controllers. However, Windows Server 2008 R2 servers cannot use FRS to replicate the contents of any replica set apart from the SYSVOL share. The DFS Replication service is a replacement for FRS and can be used to replicate the contents of the SYSVOL share, DFS folders as well as other custom (non-SYSVOL) data. Migrate all non-SYSVOL FRS replica sets to DFS Replication.
It is also highly recommend that you migrate replication of the SYSVOL share from
FRS to DFS Replication because DFS Replication is more robust,
scalable and has better replication performance than FRS.
Manifestation
FRS replication of custom data will break irreversibly upon in-place upgrade. The only way to recover from this situation would be to reinstall an older operating system on the server and reinitialize FRS replication.
Servers that have been upgraded to Windows Server 2008 R2 are not allowed to participate in existing FRS replication groups.
Mitigation of Impact
To prevent issues that might occur as a result of these changes, migrate custom FRS replication sets to DFS Replication. The DFS Replication service has many benefits over FRS, including improved management tools, higher performance, and delegated management.
whatwave
1 Rookie
•
8 Posts
0
June 26th, 2014 12:00
Thanx. I am now in touch with DELL Support in regards to this issue.