Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Browsing remote network using a remote client

Posted on 2006-05-16
15
Medium Priority
?
833 Views
Last Modified: 2013-12-07
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\SOFTWARE\Microsoft\Windows\SlowLinkDetectEnabled = Dword(0)
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GroupPolicyMinTransferRate = Dword(0)
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System\GroupPolicyMinTransferRate = Dword(0)

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
0
Comment
Question by:nmmcfk
  • 6
  • 5
  • 2
13 Comments
 
LVL 2

Expert Comment

by:liamkellycabra
ID: 16690011
Do these workstations have netbeui protocol installed?

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
0
 

Author Comment

by:nmmcfk
ID: 16690142
None of the machines have netbeui.  They all use only TCP-IP.
0
 
LVL 2

Expert Comment

by:liamkellycabra
ID: 16690190
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.

0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:nmmcfk
ID: 16690215
We don't currently have any ISA services on the server.  The duplex settings on the NICS are all set to Auto Detect.
0
 
LVL 3

Expert Comment

by:rickyclourenco
ID: 16691618
is there a Domain Controller at each site?  does it work when you try using Microsoft Remote Desktop?
0
 

Author Comment

by:nmmcfk
ID: 16698272
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.
0
 
LVL 3

Expert Comment

by:rickyclourenco
ID: 16699201
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.
0
 

Author Comment

by:nmmcfk
ID: 16699243
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.
0
 
LVL 3

Expert Comment

by:rickyclourenco
ID: 16699535
how are these sites connected?  Dedicated T1?  VPN?  Can you ping from the other site back to the original site at all times?
0
 

Author Comment

by:nmmcfk
ID: 16699552
They are connected over a dedicated T1.  I can ping from the remote site back to the original at all times.
0
 
LVL 3

Expert Comment

by:rickyclourenco
ID: 16699617
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?
0
 

Author Comment

by:nmmcfk
ID: 16699684
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?
0
 
LVL 3

Accepted Solution

by:
rickyclourenco earned 1000 total points
ID: 16699758
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Originally, this post was published on Monitis Blog, you can check it here . It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…
In this article I will be showing you how to subnet the easiest way possible for IPv4 (Internet Protocol version 4). This article does not cover IPv6. Keep in mind that subnetting requires lots of practice and time.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

580 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question