Browsing remote network using a remote client
I have been having trouble browsing one of my remote networks using the Dameware mini remote control client. This network is connected to our main network over a T1 connection using cisco 2500 routers. It will let me connect with the remote client from the main network to remote workstations remotely once in a while but other times it will not connect. The workstations that refuse the remote connection also refuse pings from the main network. When physically on the remote workstation, all services that rely on the main network operate correctly, such as Exchange (outlook mail / calendar), network browsing, etc, at the same time not allowing remote connections and ICMP pings from the main network to the remote PC. None of these connectivity problems occured when we used an NT4 domain controller, they only began occuring when we upgraded to 2003 Server. I have modified the registries on all these remote workstations to disable slow link detection by adding / modifying these keys:
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_CURRENT_USER\Software
I've also set the "slow link detect for GPO = 0" under the domain GPO.
When I do a GPRESULT on these remote workstations, both the Computer Settings and User Settings sections of the results have "Group Policy Slow Link Threshold = 0", it seems that these registry entries have disabled the slow link threshold but I am still having the same remote connectivity problems. Anybody have any suggestions,
Thanks
Kevin
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_CURRENT_USER\Software
I've also set the "slow link detect for GPO = 0" under the domain GPO.
When I do a GPRESULT on these remote workstations, both the Computer Settings and User Settings sections of the results have "Group Policy Slow Link Threshold = 0", it seems that these registry entries have disabled the slow link threshold but I am still having the same remote connectivity problems. Anybody have any suggestions,
Thanks
Kevin
ASKER
None of the machines have netbeui. They all use only TCP-IP.
Sorry here's a few straws to grasp...
Is ISA installed on the server? Have you added the IP's from the taget LAN to the LAT on ISA?
also,
Dulplex setting on the ports for the machines
Do they match the duplex on the workstartion NIC's
sometimes a mismatch can cause packets to periodically drop.
Is ISA installed on the server? Have you added the IP's from the taget LAN to the LAT on ISA?
also,
Dulplex setting on the ports for the machines
Do they match the duplex on the workstartion NIC's
sometimes a mismatch can cause packets to periodically drop.
ASKER
We don't currently have any ISA services on the server. The duplex settings on the NICS are all set to Auto Detect.
is there a Domain Controller at each site? does it work when you try using Microsoft Remote Desktop?
ASKER
The domain controller is only on the main site. We only have 1 domain controller for the whole network. I wasn't able to get remote desktop to connect either.
did you try the Telnet test to see if the port is listening?
for ex: Remote Desktop listens on 3389, but remember that this has to be enabled for it to be listening, so at a command promptr try..
telnet CompName 3389
you could also try it for the Dameware, which I believed uses port 6129
telnet CompName 6129
see if you are getting responses...
what OS are the client computers running? also as a side not, you should seriously consider having at least 1 backup Domain Cont.
for ex: Remote Desktop listens on 3389, but remember that this has to be enabled for it to be listening, so at a command promptr try..
telnet CompName 3389
you could also try it for the Dameware, which I believed uses port 6129
telnet CompName 6129
see if you are getting responses...
what OS are the client computers running? also as a side not, you should seriously consider having at least 1 backup Domain Cont.
ASKER
Remote desktop is turned off by default on all the machines. Telnetting to the dameware port works only intermittently (ie, when pings go through and when the dameware client connects). When the pings are blocked and the dameware connections are refused, the telnet connection is also refused. The client PC's all run windows XP, except for 1 windows 2000 machine.
how are these sites connected? Dedicated T1? VPN? Can you ping from the other site back to the original site at all times?
ASKER
They are connected over a dedicated T1. I can ping from the remote site back to the original at all times.
This is kind of a longshot, but I have experienced a similar issue, and we changed the KEEP ALIVE connection setting, and that resolved the line issues we were experiencing.....
There are no firewalls on either side, if there are, what kind of firewalls? is there a difference in ACL's on your side verses the other site?
There are no firewalls on either side, if there are, what kind of firewalls? is there a difference in ACL's on your side verses the other site?
ASKER
We have one firewall, but it is between our internet T1 and our network. The remote site is on a separate T1 that is directly connected to our main internal network. The ACL's on the PC's at the remote site are the same as on our main network. Do you have any more information about that KEEP ALIVE connection setting and where it is found?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SBS does not come with netbeui.
Perhapse there has been a problem before you changed to the new server and the lack of netbeui has showen you the fault.
Liam