[Group not accessible]
www_
Posted messages
25
Status
Member
-
www_ Posted messages 25 Status Member -
www_ Posted messages 25 Status Member -
Hello,
I have a Windows Server 2003 that generates the following message in the event viewer:
Source NetBt Type Error Event ID 4321
[[The name "TELECOM :1d" could not be registered on the interface with IP address 192.168.1.101. The computer with IP address 192.168.1.11 did not allow the name to be claimed by this computer.
For more information,
please refer to the Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.]]
The .1.101 corresponds to the server's IP and the .1.11 to a workstation. TELECOM is a workgroup as I do not have a domain.
I noticed that if the PC with .1.11 is turned off, there is no problem, otherwise you cannot access either the PCs in the TELECOM group or those in other groups.
Thank you for your interest in my message.
I have a Windows Server 2003 that generates the following message in the event viewer:
Source NetBt Type Error Event ID 4321
[[The name "TELECOM :1d" could not be registered on the interface with IP address 192.168.1.101. The computer with IP address 192.168.1.11 did not allow the name to be claimed by this computer.
For more information,
please refer to the Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.]]
The .1.101 corresponds to the server's IP and the .1.11 to a workstation. TELECOM is a workgroup as I do not have a domain.
I noticed that if the PC with .1.11 is turned off, there is no problem, otherwise you cannot access either the PCs in the TELECOM group or those in other groups.
Thank you for your interest in my message.
10 answers
Hello!
Think about Google at the end.
Look at what we can find.
http://www.eventid.net/display.asp?eventid=4321&eventno=1822&source=NetBT&phase=1
It’s in English but very enriching!
--
++ Biv
Always at your service
Think about Google at the end.
Look at what we can find.
http://www.eventid.net/display.asp?eventid=4321&eventno=1822&source=NetBT&phase=1
It’s in English but very enriching!
--
++ Biv
Always at your service
Hi,
From this link, I have access to the description of the event, but I don't see how to avoid it; that is, how to resolve the problem.
Thanks!
From this link, I have access to the description of the event, but I don't see how to avoid it; that is, how to resolve the problem.
Thanks!
Hi,
Isn't there something free because EventID.net is paid when we want solutions to problems. Unfortunately, I can't right now.
Cheers
Isn't there something free because EventID.net is paid when we want solutions to problems. Unfortunately, I can't right now.
Cheers
The solution is not written indeed!
But it gives an idea of the reasons for the message display.
Once you have found the reason for this error, all you have to do is correct it.
For your PC .11 to block the entire network, it is the cause. Disconnect it from the network and check its configuration:
- Firewall
- Workgroup name
- IP address / mask / gateway / DNS
- Netbios machine name
- ...
--
++ Biv
Always at your service
But it gives an idea of the reasons for the message display.
Once you have found the reason for this error, all you have to do is correct it.
For your PC .11 to block the entire network, it is the cause. Disconnect it from the network and check its configuration:
- Firewall
- Workgroup name
- IP address / mask / gateway / DNS
- Netbios machine name
- ...
--
++ Biv
Always at your service
Discovering a problem is starting to solve it!
You're right. But actually, what exactly should I look at in the configuration?
- Firewall
- Workgroup name
- IP address / mask / gateway / DNS
- Netbios machine name
- ...
because everything seems to be configured correctly.
You're right. But actually, what exactly should I look at in the configuration?
- Firewall
- Workgroup name
- IP address / mask / gateway / DNS
- Netbios machine name
- ...
because everything seems to be configured correctly.
Here is the translation you requested:
So look:
- if the workstation has a firewall enabled (e.g., Windows, Zone Alarm, ...)
- if it has an antivirus, check that it is not infected (which can cut the network for the safety of others)
- if the workstation does not have a name already used on the network
- if the workstation has a mask corresponding to its IP address (e.g., 192.168.0.10 with 255.255.255.0)
- if the name of the workgroup is correct
If all this is good, you should try to change its name and/or its IP address. If that doesn't work, remove it from the workgroup by setting it to Workgroup and see if the network still crashes.
If the network no longer crashes, put it back in the correct workgroup.
Otherwise, the last solution:
run > execute > cmd > OK
and type:
This resets the workstation's IP configuration properly and without errors.
There you go!
--
++ Biv
Always at your service
- if the workstation has a firewall enabled (e.g., Windows, Zone Alarm, ...)
- if it has an antivirus, check that it is not infected (which can cut the network for the safety of others)
- if the workstation does not have a name already used on the network
- if the workstation has a mask corresponding to its IP address (e.g., 192.168.0.10 with 255.255.255.0)
- if the name of the workgroup is correct
If all this is good, you should try to change its name and/or its IP address. If that doesn't work, remove it from the workgroup by setting it to Workgroup and see if the network still crashes.
If the network no longer crashes, put it back in the correct workgroup.
Otherwise, the last solution:
run > execute > cmd > OK
and type:
netsh int ip reset C:\resetip.txt
This resets the workstation's IP configuration properly and without errors.
There you go!
--
++ Biv
Always at your service
