Facing a challenging networking issue at work (WINS connected)
Facing a challenging networking issue at work (WINS connected)
that's what I meant by "we setup a test machine as if it were an "imaginary" user (though it was actually one of our users that had all of the specific software requirements... we duplicated it down to all of their needs, even the windows password, and the dock continued to work despite our efforts) So I want to say the issue only occurs in their office and the problem is the networking setup for their office. There's a missing piece to this puzzle that I don't know. I want to bring one of the test/spare machines and a dock into their office and see what happens... I'm trying to work on that now. Kind of hard to make things happen as an intern though.
I meant to perform the test in the same environment where the problems are happening, such as their office. Apologies for not being clear earlier. Could you tell me more about what you did with the test once it was deployed? That should help us pinpoint the issue more accurately. Also, do you have complete documentation for the network setup, including layout diagrams and technical details of the exact deployment? Comparing the working environment with the faulty one might be useful.
I managed to set up a backup machine in one of the user's offices by connecting it to their network. It functioned perfectly once everything was properly configured. However, when I tried to connect to the WINS server and disabled netBIOS, there was no connection or drive mapping. It seems the issue lies with the machines themselves rather than the network setup. My plan is to bring in the user for deployment and ensure the dock works flawlessly before and during each setup step.
it stays the same. the issue isn't resolved. I have some good updates. The device we planned to send today decided to double-check and verify the dock in the IT department before we handed it over to the user. To our dismay, it failed! We therefore canceled the appointment and are now working to identify the problem with this faulty unit. First, we compiled a list of all installed applications, using one of the spare PCs (which functions properly) to replicate her setup. Each missing software was installed sequentially to pinpoint the issue. The only difference between the two should be the software installed... everything else matches. If this doesn't resolve the matter, I'm uncertain what to attempt next. We could certainly provide the spare instead of the machine she was meant to receive, but that wouldn't be the best solution, would it?
Reviewing changes step by step ensures accuracy. Each adjustment requires verification that the dock remains functional until problems emerge. Replace faulty devices and confirm behavior. Check network settings like ACLs, VLAN configurations, and DHCP usage. Identify the DHCP server type—hardware or software—and determine if subnets are segmented or uniform across the network.
So I've reviewed every difference between the two PCs and added one software at a time to the spare to match the "broken" machine. Still, the dock remains functional. -______- I'm certain we're dealing with Avaya 4000 series switches. The network admin said there should be no problems, everything works uniformly. The current setup shows one laptop working while the other isn't, which confirms this. We're using DHCP, but I don't know which device manages it. There are several subnets, yet all user PCs are on the same one.
I've verified the details on both functional and non-functional units. At this stage, that's all we have. Please share any suggestions you might have.
It appears the issue may stem from a driver problem. On laptops lacking the additional NICs, try connecting the dock and check for hardware updates via Device Manager.