Forum Home
Press F1
Thread ID: 45344	2004-05-19 05:03:00	Network error message ???	Woof (2402)	Press F1

Post ID	Timestamp	Content	User
237729	2004-05-19 05:03:00	We are having problems with one 'leg' of our network, the wireless leg. We installed a 'new' workstation and everything worked fine. Workstation pc left on 24/7 and was next attended to 4 days later when the 'new' operator rearranged her desk and cleaned it = mainly shifted printers to the other side, lay down the pc and placed the monitor on top. Alos one day inbetween "working" and "not working" a new switch was added at the server end to provide 100/1000 instead of the previous 10Mbps only Now when we try to use the main accounting program over the network to the server we get this message :- "An error has occurred while reconnecting E: to \\ibmserver\##### Microsoft Windows Network. The local device name is already in use. This connection has not been restored." (#### being the application program name/label) As an absolute newbie to networking this message implies to me that at the server end this remote ("local") workstation is recognised by the server as already "in use" IF this was the case then there is nothing wrong with the wireless leg of the network but could be at the server/switch end where the server thinks that the particular pc/workstation is already connected and so will NOT accept "another" device using that address/name ? Can someone please tell me whether or not this newbie to networking is barking up the wrong tree or not ?	Woof (2402)
237730	2004-05-19 23:38:00	It looks as if the workstation is communicating correctly to the server, so the switch has not killed it's networking capability, and DHCP (if it's in use) is probably not misbehaving . You're getting a message which says the server has refused to make a connection . My guesses about the situation: 1) you installed the workstation, and it automatically logged in tio the accounting server . 2) Installing the new switch probably involved shuitting down at least the accounting programme, or the whole server . This would have logged out all the workstations, and they would have been logged in again afterwards as they were powered up . 3) the problem workstation might have had its network cable unplugged while the operator moved the hardware . It wasn't properly logged out, so it still has a session on the server . (The server won't allow another session from the same workstation -- that's good security, but there's a common security feature which seems to be not enabled: automatic logout of idle sessions ;-)) . Can you (as "administrator", or a privileged user) of the accountiong software log out the workstation? If not, cabn you restart it, so all the workstations are logged out then logged in again? If that fixes the problem, I'd look for an option which automatically logsout any idle/unplugged workstation . Of course I might be wrong, but I think it's just a simple silly thing like this . :D	Graham L (2)
237731	2004-05-19 23:57:00	also check your client network drive letters I think what it is saying the E:\ is already in use on the client machine, cant have to drives using the same drive ID	beama (111)
237732	2004-05-20 21:36:00	Thanks but while pressF1 was down we tracked down the problem to the cheapest part in the most awkward location = a power supply converter to one end of the wireless link. Apart from consultant's labour the biggest cost was borrowing the neighbour's extension ladder ..... Thanks for the responses	Woof (2402)
1