Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
Remote desktop connection
Name: Nimbus Date: October 30, 2003 at 08:10:16 Pacific 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??
Summary: Has anyone written/called Micro$oft on this one? I find it incredibly stupid that after installing their latest IE patch (I use win XP), I cant connect to my employers computer using Explorer anymore....
Summary: The only remote desktop you can have is with 3rd party products, like PC Anywhere, VNC, etc. Either a broadband or dial up connection. SBS 4.5 NT40 does not support the microsoft remote desktop. Ran...
