Hi,
I asked a question relating to this 2 weeks ago however after investigation I think im closer to a solution.
I currently have 1 x windows 2000 server with Active Directory, DNS, WINS, Remote Access installed.
Basicly the original problem was the network browse list kept resetting causing problems that users couldnt see network resouces (however if you select the resouce using unc paths everything worked).
After further investigation it appears the problem is being causes by the Remote Access Virtual Adaptor.
Basicly with the Remote Access Service the virtual adaptor is allocated an internal ip from the DHCP server and then also allocates an IP to the client dialing in from the DHCP server, the second part isnt a problem and works fine however the first part seems to be causing the problem.
When the internal IP is allocated to the remote access server (say its 192.168.5.89) this ip remains with the service until its restarted and can be pinged by anybody on the network, the device also shows up if you carry out an IPCONFIG /all as the second device to the primary network adaptor.
Basicly if you check the network browsing activity using the BROWMON utility 2 transport methods are displayed one for the primary adaptor (which displays the correct master browser which is the domain controller ie this server) and one for the virtual adaptor being used by the remote access service (which displays "unknown"
which seems to be fighting with the primary network adaptor for control of the browse list.
If i restart the remote access service the IP is released until the first user dials at which point the IP is reallocated to the service which seems to cure the problem until a user dials in.
Is there any way of configuring the remote access adaptor so it doenst use Netbios or does anybody know of a fix for this problem (in NT you could change the bindings on remote access adaptors but you dont seem to be able to do this in NT as the "advanced settings" dont allow changes to remote adaptops)
Does anybody have any ideas?? ;O(
I asked a question relating to this 2 weeks ago however after investigation I think im closer to a solution.
I currently have 1 x windows 2000 server with Active Directory, DNS, WINS, Remote Access installed.
Basicly the original problem was the network browse list kept resetting causing problems that users couldnt see network resouces (however if you select the resouce using unc paths everything worked).
After further investigation it appears the problem is being causes by the Remote Access Virtual Adaptor.
Basicly with the Remote Access Service the virtual adaptor is allocated an internal ip from the DHCP server and then also allocates an IP to the client dialing in from the DHCP server, the second part isnt a problem and works fine however the first part seems to be causing the problem.
When the internal IP is allocated to the remote access server (say its 192.168.5.89) this ip remains with the service until its restarted and can be pinged by anybody on the network, the device also shows up if you carry out an IPCONFIG /all as the second device to the primary network adaptor.
Basicly if you check the network browsing activity using the BROWMON utility 2 transport methods are displayed one for the primary adaptor (which displays the correct master browser which is the domain controller ie this server) and one for the virtual adaptor being used by the remote access service (which displays "unknown"
which seems to be fighting with the primary network adaptor for control of the browse list.If i restart the remote access service the IP is released until the first user dials at which point the IP is reallocated to the service which seems to cure the problem until a user dials in.
Is there any way of configuring the remote access adaptor so it doenst use Netbios or does anybody know of a fix for this problem (in NT you could change the bindings on remote access adaptors but you dont seem to be able to do this in NT as the "advanced settings" dont allow changes to remote adaptops)
Does anybody have any ideas?? ;O(
