Computing.Net > Forums > Windows NT > Remote desktop connection

Remote desktop connection

Reply to Message Icon

Original Message
Name: Nimbus
Date: October 30, 2003 at 08:10:16 Pacific
Subject: Remote desktop connection
OS: NT4 - XP - 2000
CPU/Ram: 256
Comment:

OK. On one side, we have the office network with an ADSL connection, two hub, a watchguard firewall and an NT 4 Server. We have 5 licenses for Remote Users to connect through a VPN. Remote users authenticates on NT Server. Anybody with the correct key, software and password can logon with a 56k modem, browse the network and even do Remote Desktop connection on our XP machines.
Anybody except me and a bunch of people here. Why you ask? DSL. As soon as we use a DSL line to connect, things get bad. We can successfully authenticate on the server and browse a little bit but not much. What's more, we don't see the network. We need to know the exact IP of the machine we want to get to. Remote desktop is an utopic since we only get a blank blue screen and a "connection broken timeout network screwed-up" type of message.
But then again, with a 56k modem, it work just fine.
Can someone explain me this??



Report Offensive Message For Removal


Response Number 1
Name: wanderer
Date: October 30, 2003 at 09:45:47 Pacific
Reply: (edit)

Its your firewall doing its job.


Report Offensive Follow Up For Removal

Response Number 2
Name: Nimbus
Date: October 30, 2003 at 09:54:29 Pacific
Reply: (edit)

Can you be more specific. Why 56k is ok but not DSL???


Report Offensive Follow Up For Removal







Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Remote desktop connection

Comments:

 


  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 
Data Recovery Software




Have you ever used OpenOffice?

Yes, as my main suite.
Yes, occationally.
Yes, but only once.
No, never.


View Results

Poll Finishes In 6 Days.
Discuss in The Lounge