G
Guest
While I appreciate the suggestion that the problem is entirely due to
misconfiguration of the Windows Firewall I cannot relate it to the problem as
originally stated. We have PCs on a network behind a router. The router
allocates addresses on the LAN from a DHCP address pool to all PCs that have
not been configured with a static address. Steve got me to run certain tests
- specifically designed to determine whether the PC with a static address
could ping the other PCs by their computer names. The tests showed that it
could not - the network path was not found. His comment was "When computer
access by IP address succeeds but computer access by name fails, it indicates
a problem with NetBIOS name resolution". Can you tell us which ports are used
on the LAN that have to be opened in the firewall to get round this problem?
I am sure this will be of great interest to anyone having problems with
workgroups.
misconfiguration of the Windows Firewall I cannot relate it to the problem as
originally stated. We have PCs on a network behind a router. The router
allocates addresses on the LAN from a DHCP address pool to all PCs that have
not been configured with a static address. Steve got me to run certain tests
- specifically designed to determine whether the PC with a static address
could ping the other PCs by their computer names. The tests showed that it
could not - the network path was not found. His comment was "When computer
access by IP address succeeds but computer access by name fails, it indicates
a problem with NetBIOS name resolution". Can you tell us which ports are used
on the LAN that have to be opened in the firewall to get round this problem?
I am sure this will be of great interest to anyone having problems with
workgroups.