|
#11
|
|||
|
|||
|
In article <-5ydnZp5edsahCfeRVn-hQ@comcast.com>, rsparks24@comcast.net
says... > I will be working from home after surgery for about a week. I would like to > be able to connect to my computer at work using remote desktop. I have a > laptop at home with cable internet. Network at the office is is on a > domain, Windows 2003 Server and xp client. Office has DSL for Internet > connection, with DSL modem between the Internet and the network. What do I > need to to to get accomplish the connection from home to the office? > > Thank you for your help in advance! Candace, the we we normally set this up is as follows: For a Office that has a Fixed IP Address and a firewall (not a NAT ROUTER), we would have you make a PPTP connection from your home computer to the Firewall, then the firewall would permit you to make a Remote Desktop Port connection to your desktop in the office - the office computer would be setup to accept your domain user account for Remote Desktop. If your office DSL is not a fixed IP address, well, since it can change on a daily basis, it would be impossible for you to GUESS the office network public IP address - you would have to get someone at the office to tell you the IP address and then you could do it using the other VPN or direct (port forwarding method). What you need to do is ask the Administrator if they have VPN setup on the Windows 2003 server or if they have VPN Setup on the Firewall. If they run a Dual NIC setup and SBS 2003, then you will use one solution path, if a single NIC and a NAT Router, then it's another path. To answer your question properly we need to know more about the office network, but you don't really want to post that information publically, ask your network administrator to set it up for you. -- spam999free@rrohio.com remove 999 in order to email me |
|
#12
|
|||
|
|||
|
Drop your firewall , disconnect routers, and Type conf in Start Run, Tools - Enable Remote Desktop .... Send me the IP address. This will work from 95 onwards. Although I normally use it in Remote Assistance mode (Called Shared Applications but is same as RA if you choose Desktop to share). Either way send me the IP.
AND unlike stupid messenger NM can give audio with a simplex card. If you must stuff about with silly things like firewalls http://66.102.7.104/search?q=cache:M...=en&lr=lang_en -- -------------------------------------------------------------------------------------------------- Goodbye Web Diary http://margokingston.typepad.com/har....html#comments ================================================= "Pegasus (MVP)" <I.can@fly.com> wrote in message news:eGC7VTFEGHA.3904@TK2MSFTNGP10.phx.gbl... >I note that you beat about the bush instead of responding > to my challenge. Why? > ================================== > "David Candy" <.> wrote in message > news:emqOqNFEGHA.2424@TK2MSFTNGP10.phx.gbl... > Remote Desktop is part of Netmeeting. Start it and look. It requires > conf.exe on any windows version. Based on NM there is also Terminal > Services, which the NT specific Remote Desktop (meant for Administration of > servers OR for running apps on the server from a client). In XP this was > renamed Remote Desktop and given a stupid UI. I've only ever used the > multipurpose one on XP as it is stupid to use a delibrately crippled > version, esp as the good version is present (if hidden. > ---------------------------------------------------------------------------- > --------------------- > Goodbye Web Diary > http://margokingston.typepad.com/har....html#comments > ================================================= > "Pegasus (MVP)" <I.can@fly.com> wrote in message > news:uNp1FHFEGHA.2040@TK2MSFTNGP14.phx.gbl... >> Either we're talking about two different things or else >> you are deliberately making misleading statements. >> To clarify: >> >> - This thread is about Remote Desktop. It is not about >> NetMeeting, WinVNC, pcAnywhere or any other product. >> >> - Remote Desktop requires a host machine, to host the >> the Remote Desktop session. This host must run the >> Terminal Server service. This service runs on Windows >> Server and it runs on WinXP Professional. It does not >> run on any other version of Windows. >> >> - Remote Desktop requires the remote machine to run >> mstsc.exe. This program is freely downloadable. It will >> run on any version of Windows. >> >> - There is no native Windows command called "conf" >> as you suggest in your latest reply. >> >> Now if you still think that Windows 98 will host a Remote >> Desktop session then I challenge you to post full details on >> how to configure this Win98 PC, including firewall tunnels >> etc. I will then rig up a test Win98 machine especially for >> you and I will give you its external IP address. If you can >> create a text file on my Windows 98 machine then I will >> believe you. If you can't then I suggest you stop confusing >> the OP. >> >> >> "David Candy" <.> wrote in message >> news:OxRZp6EEGHA.2320@TK2MSFTNGP11.phx.gbl... >> No it doesn't. Type conf in any windows version and turn on Remote > Desktop. >> Remote Desktop is installed on all Windows versions except the very first > 95 >> versions (you had to download it there). There is two remote desktops in > XP >> Pro. >> >> -- >> -------------------------------------------------------------------------- > -- >> ---------------------- >> Goodbye Web Diary >> > http://margokingston.typepad.com/har....html#comments >> ================================================= >> "Pegasus (MVP)" <I.can@fly.com> wrote in message >> news:uzhZcuEEGHA.2436@TK2MSFTNGP15.phx.gbl... >>>I beg to disagree. The OP's subject is "Remote Desktop" >>> and Remote Desktop requires WinXP Pro at the office. >>> >>> >>> "David Candy" <.> wrote in message >>> news:%23lZPRgEEGHA.312@TK2MSFTNGP09.phx.gbl... >>> You don't need WinXP Pro at the office. Any windows will do since 95. >>> Netmeeting. >>> >>> -- >>> ------------------------------------------------------------------------- > - >> -- >>> ---------------------- >>> Goodbye Web Diary >>> >> > http://margokingston.typepad.com/har....html#comments >>> ================================================= >>> "Pegasus (MVP)" <I.can@fly.com> wrote in message >>> news:eOonkqDEGHA.3820@TK2MSFTNGP12.phx.gbl... >>>> >>>> "Candace Sparks" <rsparks24@comcast.net> wrote in message >>>> news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... >>>>> I will be working from home after surgery for about a week. I would >> like >>>> to >>>>> be able to connect to my computer at work using remote desktop. I have >> a >>>>> laptop at home with cable internet. Network at the office is is on a >>>>> domain, Windows 2003 Server and xp client. Office has DSL for Internet >>>>> connection, with DSL modem between the Internet and the network. What >> do >>>> I >>>>> need to to to get accomplish the connection from home to the office? >>>>> >>>>> Thank you for your help in advance! >>>>> >>>>> Candace >>>>> >>>>> >>>> >>>> Here is what you need: >>>> - WinXP Professional on the office PC. >>>> - Remote Desktop enabled on the office PC. >>>> - Your account listed under the Remote Desktop users on >>>> the office PC. >>>> - A fixed internal IP address on your office PC. >>>> - An known external IP address address for your office network. >>>> - A tunnel through your office firewall that directs port 3389 >>>> packets to your office PC. >>>> - The Remote Desktop client on your home PC. If your home PC >>>> does not run WinXP then can get it from here: >>>> http://www.microsoft.com/windowsxp/p...rdclientdl.asp >>>> >>>> >>> >>> >> >> > > |
|
#13
|
|||
|
|||
|
You're talking about NetMeeting, not Remote Desktop.
Furthermore your prerequisites are totally unrealistic: - Drop the fireawall: Really? In a corporate environment? - Disconnect routers: Open up my network to the outside world? You also did not specify a port number. Are you seriously proposing to the OP to implement a scheme that renders his company's network wide open to the outside world? If so then you should explain the risks to him in detail. "David Candy" <.> wrote in message news:%23TZ6qhFEGHA.3200@tk2msftngp13.phx.gbl... Drop your firewall , disconnect routers, and Type conf in Start Run, Tools - Enable Remote Desktop .... Send me the IP address. This will work from 95 onwards. Although I normally use it in Remote Assistance mode (Called Shared Applications but is same as RA if you choose Desktop to share). Either way send me the IP. AND unlike stupid messenger NM can give audio with a simplex card. If you must stuff about with silly things like firewalls http://66.102.7.104/search?q=cache:M...=en&lr=lang_en -- ---------------------------------------------------------------------------- ---------------------- Goodbye Web Diary http://margokingston.typepad.com/har....html#comments ================================================= "Pegasus (MVP)" <I.can@fly.com> wrote in message news:eGC7VTFEGHA.3904@TK2MSFTNGP10.phx.gbl... >I note that you beat about the bush instead of responding > to my challenge. Why? > ================================== > "David Candy" <.> wrote in message > news:emqOqNFEGHA.2424@TK2MSFTNGP10.phx.gbl... > Remote Desktop is part of Netmeeting. Start it and look. It requires > conf.exe on any windows version. Based on NM there is also Terminal > Services, which the NT specific Remote Desktop (meant for Administration of > servers OR for running apps on the server from a client). In XP this was > renamed Remote Desktop and given a stupid UI. I've only ever used the > multipurpose one on XP as it is stupid to use a delibrately crippled > version, esp as the good version is present (if hidden. > -------------------------------------------------------------------------- -- > --------------------- > Goodbye Web Diary > http://margokingston.typepad.com/har....html#comments > ================================================= > "Pegasus (MVP)" <I.can@fly.com> wrote in message > news:uNp1FHFEGHA.2040@TK2MSFTNGP14.phx.gbl... >> Either we're talking about two different things or else >> you are deliberately making misleading statements. >> To clarify: >> >> - This thread is about Remote Desktop. It is not about >> NetMeeting, WinVNC, pcAnywhere or any other product. >> >> - Remote Desktop requires a host machine, to host the >> the Remote Desktop session. This host must run the >> Terminal Server service. This service runs on Windows >> Server and it runs on WinXP Professional. It does not >> run on any other version of Windows. >> >> - Remote Desktop requires the remote machine to run >> mstsc.exe. This program is freely downloadable. It will >> run on any version of Windows. >> >> - There is no native Windows command called "conf" >> as you suggest in your latest reply. >> >> Now if you still think that Windows 98 will host a Remote >> Desktop session then I challenge you to post full details on >> how to configure this Win98 PC, including firewall tunnels >> etc. I will then rig up a test Win98 machine especially for >> you and I will give you its external IP address. If you can >> create a text file on my Windows 98 machine then I will >> believe you. If you can't then I suggest you stop confusing >> the OP. >> >> >> "David Candy" <.> wrote in message >> news:OxRZp6EEGHA.2320@TK2MSFTNGP11.phx.gbl... >> No it doesn't. Type conf in any windows version and turn on Remote > Desktop. >> Remote Desktop is installed on all Windows versions except the very first > 95 >> versions (you had to download it there). There is two remote desktops in > XP >> Pro. >> >> -- >> ------------------------------------------------------------------------- - > -- >> ---------------------- >> Goodbye Web Diary >> > http://margokingston.typepad.com/har....html#comments >> ================================================= >> "Pegasus (MVP)" <I.can@fly.com> wrote in message >> news:uzhZcuEEGHA.2436@TK2MSFTNGP15.phx.gbl... >>>I beg to disagree. The OP's subject is "Remote Desktop" >>> and Remote Desktop requires WinXP Pro at the office. >>> >>> >>> "David Candy" <.> wrote in message >>> news:%23lZPRgEEGHA.312@TK2MSFTNGP09.phx.gbl... >>> You don't need WinXP Pro at the office. Any windows will do since 95. >>> Netmeeting. >>> >>> -- >>> ------------------------------------------------------------------------ - > - >> -- >>> ---------------------- >>> Goodbye Web Diary >>> >> > http://margokingston.typepad.com/har....html#comments >>> ================================================= >>> "Pegasus (MVP)" <I.can@fly.com> wrote in message >>> news:eOonkqDEGHA.3820@TK2MSFTNGP12.phx.gbl... >>>> >>>> "Candace Sparks" <rsparks24@comcast.net> wrote in message >>>> news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... >>>>> I will be working from home after surgery for about a week. I would >> like >>>> to >>>>> be able to connect to my computer at work using remote desktop. I have >> a >>>>> laptop at home with cable internet. Network at the office is is on a >>>>> domain, Windows 2003 Server and xp client. Office has DSL for Internet >>>>> connection, with DSL modem between the Internet and the network. What >> do >>>> I >>>>> need to to to get accomplish the connection from home to the office? >>>>> >>>>> Thank you for your help in advance! >>>>> >>>>> Candace >>>>> >>>>> >>>> >>>> Here is what you need: >>>> - WinXP Professional on the office PC. >>>> - Remote Desktop enabled on the office PC. >>>> - Your account listed under the Remote Desktop users on >>>> the office PC. >>>> - A fixed internal IP address on your office PC. >>>> - An known external IP address address for your office network. >>>> - A tunnel through your office firewall that directs port 3389 >>>> packets to your office PC. >>>> - The Remote Desktop client on your home PC. If your home PC >>>> does not run WinXP then can get it from here: >>>> http://www.microsoft.com/windowsxp/p...rdclientdl.asp >>>> >>>> >>> >>> >> >> > > |
|
#14
|
|||
|
|||
|
I'm not going to fu#k about with configuring firewalls when they shouldn't be even legal. A terrorist invention. Perhaps you could massage Peter Norton and his terrorist mates for screwing you over.
You have to take the same steps with NM as any other remote access software. I did post a link for the frightened and foolish. Remember firewalls/AV/etc programs only protect fools or bugs. While I run XP's firewall most of the time it isn't needed in SP2 (the bugs being exploited in windows prior to XP2 were fixed). I don't run AV programs as one CANNOT be infected unless one is stupid (or bugs but I'm a better virus checker than any program). As I don't visit sites with stolen software or porn an adware protecting program is completely unnecessary (the dirty secret of adware - it affect thieves and perverts, and the odd stupid smily central person only). The only problems I have is with idiots like NVidia and Raxco installing shìt for no reason. Why would I want nvidia pathetic utilities? Are they available on every single XP machine -NO, NO, NO, just crap. -- -------------------------------------------------------------------------------------------------- Goodbye Web Diary http://margokingston.typepad.com/har....html#comments ================================================= "Pegasus (MVP)" <I.can@fly.com> wrote in message news:%23FshX5FEGHA.516@TK2MSFTNGP15.phx.gbl... > You're talking about NetMeeting, not Remote Desktop. > Furthermore your prerequisites are totally unrealistic: > - Drop the fireawall: Really? In a corporate environment? > - Disconnect routers: Open up my network to the outside world? > You also did not specify a port number. > > Are you seriously proposing to the OP to implement a scheme > that renders his company's network wide open to the outside world? > If so then you should explain the risks to him in detail. > > > "David Candy" <.> wrote in message > news:%23TZ6qhFEGHA.3200@tk2msftngp13.phx.gbl... > Drop your firewall , disconnect routers, and Type conf in Start Run, Tools - > Enable Remote Desktop .... Send me the IP address. This will work from 95 > onwards. Although I normally use it in Remote Assistance mode (Called Shared > Applications but is same as RA if you choose Desktop to share). Either way > send me the IP. > > AND unlike stupid messenger NM can give audio with a simplex card. > > If you must stuff about with silly things like firewalls > http://66.102.7.104/search?q=cache:M...=en&lr=lang_en > -- > ---------------------------------------------------------------------------- > ---------------------- > Goodbye Web Diary > http://margokingston.typepad.com/har....html#comments > ================================================= > "Pegasus (MVP)" <I.can@fly.com> wrote in message > news:eGC7VTFEGHA.3904@TK2MSFTNGP10.phx.gbl... >>I note that you beat about the bush instead of responding >> to my challenge. Why? >> ================================== >> "David Candy" <.> wrote in message >> news:emqOqNFEGHA.2424@TK2MSFTNGP10.phx.gbl... >> Remote Desktop is part of Netmeeting. Start it and look. It requires >> conf.exe on any windows version. Based on NM there is also Terminal >> Services, which the NT specific Remote Desktop (meant for Administration > of >> servers OR for running apps on the server from a client). In XP this was >> renamed Remote Desktop and given a stupid UI. I've only ever used the >> multipurpose one on XP as it is stupid to use a delibrately crippled >> version, esp as the good version is present (if hidden. >> -------------------------------------------------------------------------- > -- >> --------------------- >> Goodbye Web Diary >> > http://margokingston.typepad.com/har....html#comments >> ================================================= >> "Pegasus (MVP)" <I.can@fly.com> wrote in message >> news:uNp1FHFEGHA.2040@TK2MSFTNGP14.phx.gbl... >>> Either we're talking about two different things or else >>> you are deliberately making misleading statements. >>> To clarify: >>> >>> - This thread is about Remote Desktop. It is not about >>> NetMeeting, WinVNC, pcAnywhere or any other product. >>> >>> - Remote Desktop requires a host machine, to host the >>> the Remote Desktop session. This host must run the >>> Terminal Server service. This service runs on Windows >>> Server and it runs on WinXP Professional. It does not >>> run on any other version of Windows. >>> >>> - Remote Desktop requires the remote machine to run >>> mstsc.exe. This program is freely downloadable. It will >>> run on any version of Windows. >>> >>> - There is no native Windows command called "conf" >>> as you suggest in your latest reply. >>> >>> Now if you still think that Windows 98 will host a Remote >>> Desktop session then I challenge you to post full details on >>> how to configure this Win98 PC, including firewall tunnels >>> etc. I will then rig up a test Win98 machine especially for >>> you and I will give you its external IP address. If you can >>> create a text file on my Windows 98 machine then I will >>> believe you. If you can't then I suggest you stop confusing >>> the OP. >>> >>> >>> "David Candy" <.> wrote in message >>> news:OxRZp6EEGHA.2320@TK2MSFTNGP11.phx.gbl... >>> No it doesn't. Type conf in any windows version and turn on Remote >> Desktop. >>> Remote Desktop is installed on all Windows versions except the very first >> 95 >>> versions (you had to download it there). There is two remote desktops in >> XP >>> Pro. >>> >>> -- >>> ------------------------------------------------------------------------- > - >> -- >>> ---------------------- >>> Goodbye Web Diary >>> >> > http://margokingston.typepad.com/har....html#comments >>> ================================================= >>> "Pegasus (MVP)" <I.can@fly.com> wrote in message >>> news:uzhZcuEEGHA.2436@TK2MSFTNGP15.phx.gbl... >>>>I beg to disagree. The OP's subject is "Remote Desktop" >>>> and Remote Desktop requires WinXP Pro at the office. >>>> >>>> >>>> "David Candy" <.> wrote in message >>>> news:%23lZPRgEEGHA.312@TK2MSFTNGP09.phx.gbl... >>>> You don't need WinXP Pro at the office. Any windows will do since 95. >>>> Netmeeting. >>>> >>>> -- >>>> ------------------------------------------------------------------------ > - >> - >>> -- >>>> ---------------------- >>>> Goodbye Web Diary >>>> >>> >> > http://margokingston.typepad.com/har....html#comments >>>> ================================================= >>>> "Pegasus (MVP)" <I.can@fly.com> wrote in message >>>> news:eOonkqDEGHA.3820@TK2MSFTNGP12.phx.gbl... >>>>> >>>>> "Candace Sparks" <rsparks24@comcast.net> wrote in message >>>>> news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... >>>>>> I will be working from home after surgery for about a week. I would >>> like >>>>> to >>>>>> be able to connect to my computer at work using remote desktop. I > have >>> a >>>>>> laptop at home with cable internet. Network at the office is is on a >>>>>> domain, Windows 2003 Server and xp client. Office has DSL for > Internet >>>>>> connection, with DSL modem between the Internet and the network. What >>> do >>>>> I >>>>>> need to to to get accomplish the connection from home to the office? >>>>>> >>>>>> Thank you for your help in advance! >>>>>> >>>>>> Candace >>>>>> >>>>>> >>>>> >>>>> Here is what you need: >>>>> - WinXP Professional on the office PC. >>>>> - Remote Desktop enabled on the office PC. >>>>> - Your account listed under the Remote Desktop users on >>>>> the office PC. >>>>> - A fixed internal IP address on your office PC. >>>>> - An known external IP address address for your office network. >>>>> - A tunnel through your office firewall that directs port 3389 >>>>> packets to your office PC. >>>>> - The Remote Desktop client on your home PC. If your home PC >>>>> does not run WinXP then can get it from here: >>>>> http://www.microsoft.com/windowsxp/p...rdclientdl.asp >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > |
|
#15
|
|||
|
|||
|
You need to talk with your system administrator to setup your work computer
for you, and to tell you what you have to do on your end at home to match his requirements. -- Regards, Richard Urban Microsoft MVP Windows Shell/User Quote from George Ankner: If you knew as much as you think you know, You would realize that you don't know what you thought you knew! "Candace Sparks" <rsparks24@comcast.net> wrote in message news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... >I will be working from home after surgery for about a week. I would like >to be able to connect to my computer at work using remote desktop. I have >a laptop at home with cable internet. Network at the office is is on a >domain, Windows 2003 Server and xp client. Office has DSL for Internet >connection, with DSL modem between the Internet and the network. What do I >need to to to get accomplish the connection from home to the office? > > Thank you for your help in advance! > > Candace > |
|
#16
|
|||
|
|||
|
Wow
David, could you give the unenlightened masses with their heads in the sand (and i count myself as one of these if trying to look after your network is an act of stupidity) a valid reason for opening up their networks by taking their firewalls out of the picture? A terrorist invention? Explain... "David Candy" wrote: > I'm not going to fu#k about with configuring firewalls when they shouldn't be even legal. A terrorist invention. Perhaps you could massage Peter Norton and his terrorist mates for screwing you over. > > You have to take the same steps with NM as any other remote access software. I did post a link for the frightened and foolish. > > Remember firewalls/AV/etc programs only protect fools or bugs. While I run XP's firewall most of the time it isn't needed in SP2 (the bugs being exploited in windows prior to XP2 were fixed). I don't run AV programs as one CANNOT be infected unless one is stupid (or bugs but I'm a better virus checker than any program). As I don't visit sites with stolen software or porn an adware protecting program is completely unnecessary (the dirty secret of adware - it affect thieves and perverts, and the odd stupid smily central person only). The only problems I have is with idiots like NVidia and Raxco installing shìt for no reason. Why would I want nvidia pathetic utilities? Are they available on every single XP machine -NO, NO, NO, just crap. > -- > -------------------------------------------------------------------------------------------------- > Goodbye Web Diary > http://margokingston.typepad.com/har....html#comments > ================================================= > "Pegasus (MVP)" <I.can@fly.com> wrote in message news:%23FshX5FEGHA.516@TK2MSFTNGP15.phx.gbl... > > You're talking about NetMeeting, not Remote Desktop. > > Furthermore your prerequisites are totally unrealistic: > > - Drop the fireawall: Really? In a corporate environment? > > - Disconnect routers: Open up my network to the outside world? > > You also did not specify a port number. > > > > Are you seriously proposing to the OP to implement a scheme > > that renders his company's network wide open to the outside world? > > If so then you should explain the risks to him in detail. > > > > > > "David Candy" <.> wrote in message > > news:%23TZ6qhFEGHA.3200@tk2msftngp13.phx.gbl... > > Drop your firewall , disconnect routers, and Type conf in Start Run, Tools - > > Enable Remote Desktop .... Send me the IP address. This will work from 95 > > onwards. Although I normally use it in Remote Assistance mode (Called Shared > > Applications but is same as RA if you choose Desktop to share). Either way > > send me the IP. > > > > AND unlike stupid messenger NM can give audio with a simplex card. > > > > If you must stuff about with silly things like firewalls > > http://66.102.7.104/search?q=cache:M...=en&lr=lang_en > > -- > > ---------------------------------------------------------------------------- > > ---------------------- > > Goodbye Web Diary > > http://margokingston.typepad.com/har....html#comments > > ================================================= > > "Pegasus (MVP)" <I.can@fly.com> wrote in message > > news:eGC7VTFEGHA.3904@TK2MSFTNGP10.phx.gbl... > >>I note that you beat about the bush instead of responding > >> to my challenge. Why? > >> ================================== > >> "David Candy" <.> wrote in message > >> news:emqOqNFEGHA.2424@TK2MSFTNGP10.phx.gbl... > >> Remote Desktop is part of Netmeeting. Start it and look. It requires > >> conf.exe on any windows version. Based on NM there is also Terminal > >> Services, which the NT specific Remote Desktop (meant for Administration > > of > >> servers OR for running apps on the server from a client). In XP this was > >> renamed Remote Desktop and given a stupid UI. I've only ever used the > >> multipurpose one on XP as it is stupid to use a delibrately crippled > >> version, esp as the good version is present (if hidden. > >> -------------------------------------------------------------------------- > > -- > >> --------------------- > >> Goodbye Web Diary > >> > > http://margokingston.typepad.com/har....html#comments > >> ================================================= > >> "Pegasus (MVP)" <I.can@fly.com> wrote in message > >> news:uNp1FHFEGHA.2040@TK2MSFTNGP14.phx.gbl... > >>> Either we're talking about two different things or else > >>> you are deliberately making misleading statements. > >>> To clarify: > >>> > >>> - This thread is about Remote Desktop. It is not about > >>> NetMeeting, WinVNC, pcAnywhere or any other product. > >>> > >>> - Remote Desktop requires a host machine, to host the > >>> the Remote Desktop session. This host must run the > >>> Terminal Server service. This service runs on Windows > >>> Server and it runs on WinXP Professional. It does not > >>> run on any other version of Windows. > >>> > >>> - Remote Desktop requires the remote machine to run > >>> mstsc.exe. This program is freely downloadable. It will > >>> run on any version of Windows. > >>> > >>> - There is no native Windows command called "conf" > >>> as you suggest in your latest reply. > >>> > >>> Now if you still think that Windows 98 will host a Remote > >>> Desktop session then I challenge you to post full details on > >>> how to configure this Win98 PC, including firewall tunnels > >>> etc. I will then rig up a test Win98 machine especially for > >>> you and I will give you its external IP address. If you can > >>> create a text file on my Windows 98 machine then I will > >>> believe you. If you can't then I suggest you stop confusing > >>> the OP. > >>> > >>> > >>> "David Candy" <.> wrote in message > >>> news:OxRZp6EEGHA.2320@TK2MSFTNGP11.phx.gbl... > >>> No it doesn't. Type conf in any windows version and turn on Remote > >> Desktop. > >>> Remote Desktop is installed on all Windows versions except the very first > >> 95 > >>> versions (you had to download it there). There is two remote desktops in > >> XP > >>> Pro. > >>> > >>> -- > >>> ------------------------------------------------------------------------- > > - > >> -- > >>> ---------------------- > >>> Goodbye Web Diary > >>> > >> > > http://margokingston.typepad.com/har....html#comments > >>> ================================================= > >>> "Pegasus (MVP)" <I.can@fly.com> wrote in message > >>> news:uzhZcuEEGHA.2436@TK2MSFTNGP15.phx.gbl... > >>>>I beg to disagree. The OP's subject is "Remote Desktop" > >>>> and Remote Desktop requires WinXP Pro at the office. > >>>> > >>>> > >>>> "David Candy" <.> wrote in message > >>>> news:%23lZPRgEEGHA.312@TK2MSFTNGP09.phx.gbl... > >>>> You don't need WinXP Pro at the office. Any windows will do since 95. > >>>> Netmeeting. > >>>> > >>>> -- > >>>> ------------------------------------------------------------------------ > > - > >> - > >>> -- > >>>> ---------------------- > >>>> Goodbye Web Diary > >>>> > >>> > >> > > http://margokingston.typepad.com/har....html#comments > >>>> ================================================= > >>>> "Pegasus (MVP)" <I.can@fly.com> wrote in message > >>>> news:eOonkqDEGHA.3820@TK2MSFTNGP12.phx.gbl... > >>>>> > >>>>> "Candace Sparks" <rsparks24@comcast.net> wrote in message > >>>>> news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... > >>>>>> I will be working from home after surgery for about a week. I would > >>> like > >>>>> to > >>>>>> be able to connect to my computer at work using remote desktop. I > > have > >>> a > >>>>>> laptop at home with cable internet. Network at the office is is on a > >>>>>> domain, Windows 2003 Server and xp client. Office has DSL for > > Internet > >>>>>> connection, with DSL modem between the Internet and the network. What > >>> do > >>>>> I > >>>>>> need to to to get accomplish the connection from home to the office? > >>>>>> > >>>>>> Thank you for your help in advance! > >>>>>> > >>>>>> Candace > >>>>>> > >>>>>> > >>>>> > >>>>> Here is what you need: > >>>>> - WinXP Professional on the office PC. > >>>>> - Remote Desktop enabled on the office PC. > >>>>> - Your account listed under the Remote Desktop users on > >>>>> the office PC. > >>>>> - A fixed internal IP address on your office PC. > >>>>> - An known external IP address address for your office network. > >>>>> - A tunnel through your office firewall that directs port 3389 > >>>>> packets to your office PC. > >>>>> - The Remote Desktop client on your home PC. If your home PC > >>>>> does not run WinXP then can get it from here: > >>>>> http://www.microsoft.com/windowsxp/p...rdclientdl.asp > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > > > > > |
|
#17
|
|||
|
|||
|
How are you opening up your network by disabling a firewall. Most networks have security protocols.
-- -------------------------------------------------------------------------------------------------- Goodbye Web Diary http://margokingston.typepad.com/har....html#comments ================================================= "Mort" <Mort@discussions.microsoft.com> wrote in message news:B1912CD6-E9F3-48FB-BDD8-34C330DDF663@microsoft.com... > Wow > > David, could you give the unenlightened masses with their heads in the sand > (and i count myself as one of these if trying to look after your network is > an act of stupidity) a valid reason for opening up their networks by taking > their firewalls out of the picture? A terrorist invention? Explain... > > "David Candy" wrote: > >> I'm not going to fu#k about with configuring firewalls when they shouldn't be even legal. A terrorist invention. Perhaps you could massage Peter Norton and his terrorist mates for screwing you over. >> >> You have to take the same steps with NM as any other remote access software. I did post a link for the frightened and foolish. >> >> Remember firewalls/AV/etc programs only protect fools or bugs. While I run XP's firewall most of the time it isn't needed in SP2 (the bugs being exploited in windows prior to XP2 were fixed). I don't run AV programs as one CANNOT be infected unless one is stupid (or bugs but I'm a better virus checker than any program). As I don't visit sites with stolen software or porn an adware protecting program is completely unnecessary (the dirty secret of adware - it affect thieves and perverts, and the odd stupid smily central person only). The only problems I have is with idiots like NVidia and Raxco installing shìt for no reason. Why would I want nvidia pathetic utilities? Are they available on every single XP machine -NO, NO, NO, just crap. >> -- >> -------------------------------------------------------------------------------------------------- >> Goodbye Web Diary >> http://margokingston.typepad.com/har....html#comments >> ================================================= >> "Pegasus (MVP)" <I.can@fly.com> wrote in message news:%23FshX5FEGHA.516@TK2MSFTNGP15.phx.gbl... >> > You're talking about NetMeeting, not Remote Desktop. >> > Furthermore your prerequisites are totally unrealistic: >> > - Drop the fireawall: Really? In a corporate environment? >> > - Disconnect routers: Open up my network to the outside world? >> > You also did not specify a port number. >> > >> > Are you seriously proposing to the OP to implement a scheme >> > that renders his company's network wide open to the outside world? >> > If so then you should explain the risks to him in detail. >> > >> > >> > "David Candy" <.> wrote in message >> > news:%23TZ6qhFEGHA.3200@tk2msftngp13.phx.gbl... >> > Drop your firewall , disconnect routers, and Type conf in Start Run, Tools - >> > Enable Remote Desktop .... Send me the IP address. This will work from 95 >> > onwards. Although I normally use it in Remote Assistance mode (Called Shared >> > Applications but is same as RA if you choose Desktop to share). Either way >> > send me the IP. >> > >> > AND unlike stupid messenger NM can give audio with a simplex card. >> > >> > If you must stuff about with silly things like firewalls >> > http://66.102.7.104/search?q=cache:M...=en&lr=lang_en >> > -- >> > ---------------------------------------------------------------------------- >> > ---------------------- >> > Goodbye Web Diary >> > http://margokingston.typepad.com/har....html#comments >> > ================================================= >> > "Pegasus (MVP)" <I.can@fly.com> wrote in message >> > news:eGC7VTFEGHA.3904@TK2MSFTNGP10.phx.gbl... >> >>I note that you beat about the bush instead of responding >> >> to my challenge. Why? >> >> ================================== >> >> "David Candy" <.> wrote in message >> >> news:emqOqNFEGHA.2424@TK2MSFTNGP10.phx.gbl... >> >> Remote Desktop is part of Netmeeting. Start it and look. It requires >> >> conf.exe on any windows version. Based on NM there is also Terminal >> >> Services, which the NT specific Remote Desktop (meant for Administration >> > of >> >> servers OR for running apps on the server from a client). In XP this was >> >> renamed Remote Desktop and given a stupid UI. I've only ever used the >> >> multipurpose one on XP as it is stupid to use a delibrately crippled >> >> version, esp as the good version is present (if hidden. >> >> -------------------------------------------------------------------------- >> > -- >> >> --------------------- >> >> Goodbye Web Diary >> >> >> > http://margokingston.typepad.com/har....html#comments >> >> ================================================= >> >> "Pegasus (MVP)" <I.can@fly.com> wrote in message >> >> news:uNp1FHFEGHA.2040@TK2MSFTNGP14.phx.gbl... >> >>> Either we're talking about two different things or else >> >>> you are deliberately making misleading statements. >> >>> To clarify: >> >>> >> >>> - This thread is about Remote Desktop. It is not about >> >>> NetMeeting, WinVNC, pcAnywhere or any other product. >> >>> >> >>> - Remote Desktop requires a host machine, to host the >> >>> the Remote Desktop session. This host must run the >> >>> Terminal Server service. This service runs on Windows >> >>> Server and it runs on WinXP Professional. It does not >> >>> run on any other version of Windows. >> >>> >> >>> - Remote Desktop requires the remote machine to run >> >>> mstsc.exe. This program is freely downloadable. It will >> >>> run on any version of Windows. >> >>> >> >>> - There is no native Windows command called "conf" >> >>> as you suggest in your latest reply. >> >>> >> >>> Now if you still think that Windows 98 will host a Remote >> >>> Desktop session then I challenge you to post full details on >> >>> how to configure this Win98 PC, including firewall tunnels >> >>> etc. I will then rig up a test Win98 machine especially for >> >>> you and I will give you its external IP address. If you can >> >>> create a text file on my Windows 98 machine then I will >> >>> believe you. If you can't then I suggest you stop confusing >> >>> the OP. >> >>> >> >>> >> >>> "David Candy" <.> wrote in message >> >>> news:OxRZp6EEGHA.2320@TK2MSFTNGP11.phx.gbl... >> >>> No it doesn't. Type conf in any windows version and turn on Remote >> >> Desktop. >> >>> Remote Desktop is installed on all Windows versions except the very first >> >> 95 >> >>> versions (you had to download it there). There is two remote desktops in >> >> XP >> >>> Pro. >> >>> >> >>> -- >> >>> ------------------------------------------------------------------------- >> > - >> >> -- >> >>> ---------------------- >> >>> Goodbye Web Diary >> >>> >> >> >> > http://margokingston.typepad.com/har....html#comments >> >>> ================================================= >> >>> "Pegasus (MVP)" <I.can@fly.com> wrote in message >> >>> news:uzhZcuEEGHA.2436@TK2MSFTNGP15.phx.gbl... >> >>>>I beg to disagree. The OP's subject is "Remote Desktop" >> >>>> and Remote Desktop requires WinXP Pro at the office. >> >>>> >> >>>> >> >>>> "David Candy" <.> wrote in message >> >>>> news:%23lZPRgEEGHA.312@TK2MSFTNGP09.phx.gbl... >> >>>> You don't need WinXP Pro at the office. Any windows will do since 95. >> >>>> Netmeeting. >> >>>> >> >>>> -- >> >>>> ------------------------------------------------------------------------ >> > - >> >> - >> >>> -- >> >>>> ---------------------- >> >>>> Goodbye Web Diary >> >>>> >> >>> >> >> >> > http://margokingston.typepad.com/har....html#comments >> >>>> ================================================= >> >>>> "Pegasus (MVP)" <I.can@fly.com> wrote in message >> >>>> news:eOonkqDEGHA.3820@TK2MSFTNGP12.phx.gbl... >> >>>>> >> >>>>> "Candace Sparks" <rsparks24@comcast.net> wrote in message >> >>>>> news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... >> >>>>>> I will be working from home after surgery for about a week. I would >> >>> like >> >>>>> to >> >>>>>> be able to connect to my computer at work using remote desktop. I >> > have >> >>> a >> >>>>>> laptop at home with cable internet. Network at the office is is on a >> >>>>>> domain, Windows 2003 Server and xp client. Office has DSL for >> > Internet >> >>>>>> connection, with DSL modem between the Internet and the network. What >> >>> do >> >>>>> I >> >>>>>> need to to to get accomplish the connection from home to the office? >> >>>>>> >> >>>>>> Thank you for your help in advance! >> >>>>>> >> >>>>>> Candace >> >>>>>> >> >>>>>> >> >>>>> >> >>>>> Here is what you need: >> >>>>> - WinXP Professional on the office PC. >> >>>>> - Remote Desktop enabled on the office PC. >> >>>>> - Your account listed under the Remote Desktop users on >> >>>>> the office PC. >> >>>>> - A fixed internal IP address on your office PC. >> >>>>> - An known external IP address address for your office network. >> >>>>> - A tunnel through your office firewall that directs port 3389 >> >>>>> packets to your office PC. >> >>>>> - The Remote Desktop client on your home PC. If your home PC >> >>>>> does not run WinXP then can get it from here: >> >>>>> http://www.microsoft.com/windowsxp/p...rdclientdl.asp >> >>>>> >> >>>>> >> >>>> >> >>>> >> >>> >> >>> >> >> >> >> >> > >> > >> |
|
#18
|
|||
|
|||
|
Surely the firewall is part of that security protocol...?
"David Candy" wrote: > How are you opening up your network by disabling a firewall. Most networks have security protocols. > > -- > -------------------------------------------------------------------------------------------------- > Goodbye Web Diary > http://margokingston.typepad.com/har....html#comments > ================================================= > "Mort" <Mort@discussions.microsoft.com> wrote in message news:B1912CD6-E9F3-48FB-BDD8-34C330DDF663@microsoft.com... > > Wow > > > > David, could you give the unenlightened masses with their heads in the sand > > (and i count myself as one of these if trying to look after your network is > > an act of stupidity) a valid reason for opening up their networks by taking > > their firewalls out of the picture? A terrorist invention? Explain... > > > > "David Candy" wrote: > > > >> I'm not going to fu#k about with configuring firewalls when they shouldn't be even legal. A terrorist invention. Perhaps you could massage Peter Norton and his terrorist mates for screwing you over. > >> > >> You have to take the same steps with NM as any other remote access software. I did post a link for the frightened and foolish. > >> > >> Remember firewalls/AV/etc programs only protect fools or bugs. While I run XP's firewall most of the time it isn't needed in SP2 (the bugs being exploited in windows prior to XP2 were fixed). I don't run AV programs as one CANNOT be infected unless one is stupid (or bugs but I'm a better virus checker than any program). As I don't visit sites with stolen software or porn an adware protecting program is completely unnecessary (the dirty secret of adware - it affect thieves and perverts, and the odd stupid smily central person only). The only problems I have is with idiots like NVidia and Raxco installing shìt for no reason. Why would I want nvidia pathetic utilities? Are they available on every single XP machine -NO, NO, NO, just crap. > >> -- > >> -------------------------------------------------------------------------------------------------- > >> Goodbye Web Diary > >> http://margokingston.typepad.com/har....html#comments > >> ================================================= > >> "Pegasus (MVP)" <I.can@fly.com> wrote in message news:%23FshX5FEGHA.516@TK2MSFTNGP15.phx.gbl... > >> > You're talking about NetMeeting, not Remote Desktop. > >> > Furthermore your prerequisites are totally unrealistic: > >> > - Drop the fireawall: Really? In a corporate environment? > >> > - Disconnect routers: Open up my network to the outside world? > >> > You also did not specify a port number. > >> > > >> > Are you seriously proposing to the OP to implement a scheme > >> > that renders his company's network wide open to the outside world? > >> > If so then you should explain the risks to him in detail. > >> > > >> > > >> > "David Candy" <.> wrote in message > >> > news:%23TZ6qhFEGHA.3200@tk2msftngp13.phx.gbl... > >> > Drop your firewall , disconnect routers, and Type conf in Start Run, Tools - > >> > Enable Remote Desktop .... Send me the IP address. This will work from 95 > >> > onwards. Although I normally use it in Remote Assistance mode (Called Shared > >> > Applications but is same as RA if you choose Desktop to share). Either way > >> > send me the IP. > >> > > >> > AND unlike stupid messenger NM can give audio with a simplex card. > >> > > >> > If you must stuff about with silly things like firewalls > >> > http://66.102.7.104/search?q=cache:M...=en&lr=lang_en > >> > -- > >> > ---------------------------------------------------------------------------- > >> > ---------------------- > >> > Goodbye Web Diary > >> > http://margokingston.typepad.com/har....html#comments > >> > ================================================= > >> > "Pegasus (MVP)" <I.can@fly.com> wrote in message > >> > news:eGC7VTFEGHA.3904@TK2MSFTNGP10.phx.gbl... > >> >>I note that you beat about the bush instead of responding > >> >> to my challenge. Why? > >> >> ================================== > >> >> "David Candy" <.> wrote in message > >> >> news:emqOqNFEGHA.2424@TK2MSFTNGP10.phx.gbl... > >> >> Remote Desktop is part of Netmeeting. Start it and look. It requires > >> >> conf.exe on any windows version. Based on NM there is also Terminal > >> >> Services, which the NT specific Remote Desktop (meant for Administration > >> > of > >> >> servers OR for running apps on the server from a client). In XP this was > >> >> renamed Remote Desktop and given a stupid UI. I've only ever used the > >> >> multipurpose one on XP as it is stupid to use a delibrately crippled > >> >> version, esp as the good version is present (if hidden. > >> >> -------------------------------------------------------------------------- > >> > -- > >> >> --------------------- > >> >> Goodbye Web Diary > >> >> > >> > http://margokingston.typepad.com/har....html#comments > >> >> ================================================= > >> >> "Pegasus (MVP)" <I.can@fly.com> wrote in message > >> >> news:uNp1FHFEGHA.2040@TK2MSFTNGP14.phx.gbl... > >> >>> Either we're talking about two different things or else > >> >>> you are deliberately making misleading statements. > >> >>> To clarify: > >> >>> > >> >>> - This thread is about Remote Desktop. It is not about > >> >>> NetMeeting, WinVNC, pcAnywhere or any other product. > >> >>> > >> >>> - Remote Desktop requires a host machine, to host the > >> >>> the Remote Desktop session. This host must run the > >> >>> Terminal Server service. This service runs on Windows > >> >>> Server and it runs on WinXP Professional. It does not > >> >>> run on any other version of Windows. > >> >>> > >> >>> - Remote Desktop requires the remote machine to run > >> >>> mstsc.exe. This program is freely downloadable. It will > >> >>> run on any version of Windows. > >> >>> > >> >>> - There is no native Windows command called "conf" > >> >>> as you suggest in your latest reply. > >> >>> > >> >>> Now if you still think that Windows 98 will host a Remote > >> >>> Desktop session then I challenge you to post full details on > >> >>> how to configure this Win98 PC, including firewall tunnels > >> >>> etc. I will then rig up a test Win98 machine especially for > >> >>> you and I will give you its external IP address. If you can > >> >>> create a text file on my Windows 98 machine then I will > >> >>> believe you. If you can't then I suggest you stop confusing > >> >>> the OP. > >> >>> > >> >>> > >> >>> "David Candy" <.> wrote in message > >> >>> news:OxRZp6EEGHA.2320@TK2MSFTNGP11.phx.gbl... > >> >>> No it doesn't. Type conf in any windows version and turn on Remote > >> >> Desktop. > >> >>> Remote Desktop is installed on all Windows versions except the very first > >> >> 95 > >> >>> versions (you had to download it there). There is two remote desktops in > >> >> XP > >> >>> Pro. > >> >>> > >> >>> -- > >> >>> ------------------------------------------------------------------------- > >> > - > >> >> -- > >> >>> ---------------------- > >> >>> Goodbye Web Diary > >> >>> > >> >> > >> > http://margokingston.typepad.com/har....html#comments > >> >>> ================================================= > >> >>> "Pegasus (MVP)" <I.can@fly.com> wrote in message > >> >>> news:uzhZcuEEGHA.2436@TK2MSFTNGP15.phx.gbl... > >> >>>>I beg to disagree. The OP's subject is "Remote Desktop" > >> >>>> and Remote Desktop requires WinXP Pro at the office. > >> >>>> > >> >>>> > >> >>>> "David Candy" <.> wrote in message > >> >>>> news:%23lZPRgEEGHA.312@TK2MSFTNGP09.phx.gbl... > >> >>>> You don't need WinXP Pro at the office. Any windows will do since 95. > >> >>>> Netmeeting. > >> >>>> > >> >>>> -- > >> >>>> ------------------------------------------------------------------------ > >> > - > >> >> - > >> >>> -- > >> >>>> ---------------------- > >> >>>> Goodbye Web Diary > >> >>>> > >> >>> > >> >> > >> > http://margokingston.typepad.com/har....html#comments > >> >>>> ================================================= > >> >>>> "Pegasus (MVP)" <I.can@fly.com> wrote in message > >> >>>> news:eOonkqDEGHA.3820@TK2MSFTNGP12.phx.gbl... > >> >>>>> > >> >>>>> "Candace Sparks" <rsparks24@comcast.net> wrote in message > >> >>>>> news:-5ydnZp5edsahCfeRVn-hQ@comcast.com... > >> >>>>>> I will be working from home after surgery for about a week. I would > >> >>> like > >> >>>>> to > >> >>>>>> be able to connect to my computer at work using remote desktop. I > >> > have > >> >>> a > >> >>>>>> laptop at home with cable internet. Network at the office is is on a > >> >>>>>> domain, Windows 2003 Server and xp client. Office has DSL for > >> > Internet > >> >>>>>> connection, with DSL modem between the Internet and the network. What > >> >>> do > >> >>>>> I > >> >>>>>> need to to to get accomplish the connection from home to the office? > >> >>>>>> > >> >>>>>> Thank you for your help in advance! > >> >>>>>> > >> >>>>>> Candace > >> >>>>>> > >> >>>>>> > >> >>>>> > >> >>>>> Here is what you need: > >> >>>>> - WinXP Professional on the office PC. > >> >>>>> - Remote Desktop enabled on the office PC. > >> >>>>> - Your account listed under the Remote Desktop users on > >> >>>>> the office PC. > >> >>>>> - A fixed internal IP address on your office PC. > >> >>>>> - An known external IP address address for your office network. > >> >>>>> - A tunnel through your office firewall that directs port 3389 > >> >>>>> packets to your office PC. > >> >>>>> - The Remote Desktop client on your home PC. If your home PC > >> >>>>> does not run WinXP then can get it from here: > >> >>>>> http://www.microsoft.com/windowsxp/p...rdclientdl.asp > >> >>>>> > >> >>>>> > >> >>>> > >> >>>> > >> >>> > >> >>> > >> >> > >> >> > >> > > >> > > >> > |
|
#19
|
|||
|
|||
|
In article <OqfwKfFEGHA.272@TK2MSFTNGP10.phx.gbl>, I.can@fly.com says...
> Comments in-line. > > "Leythos" <void@nowhere.lan> wrote in message > news:T_suf.277185$tD4.88249@tornado.ohiordc.rr.com ... > > In article <-5ydnZp5edsahCfeRVn-hQ@comcast.com>, rsparks24@comcast.net > > says... > > > I will be working from home after surgery for about a week. I would > like to > > > be able to connect to my computer at work using remote desktop. I have > a > > > laptop at home with cable internet. Network at the office is is on a > > > domain, Windows 2003 Server and xp client. Office has DSL for Internet > > > connection, with DSL modem between the Internet and the network. What > do I > > > need to to to get accomplish the connection from home to the office? > > > > > > Thank you for your help in advance! > > > > Candace, the we we normally set this up is as follows: > > > > For a Office that has a Fixed IP Address and a firewall (not a NAT > > ROUTER), we would have you make a PPTP connection from your home > > computer to the Firewall, then the firewall would permit you to make a > > Remote Desktop Port connection to your desktop in the office - the > > office computer would be setup to accept your domain user account for > > Remote Desktop. > > > > If your office DSL is not a fixed IP address, well, since it can change > > on a daily basis, it would be impossible for you to GUESS the office > > network public IP address - you would have to get someone at the office > > to tell you the IP address and then you could do it using the other VPN > > or direct (port forwarding method). > > An easy solution to this problem is provided free of charge by > companies such as www.no-ip.com or www.dyndns.org. Yes, but you might still want a fixed IP so that everything works all the time and perfectly. Imagine the headache it causes when the lease expires and the new IP has not replicated to the public DNS servers yet. > > > What you need to do is ask the Administrator if they have VPN setup on > > the Windows 2003 server or if they have VPN Setup on the Firewall. If > > they run a Dual NIC setup and SBS 2003, then you will use one solution > > path, if a single NIC and a NAT Router, then it's another path. > > You do not need a VPN for Remote Desktop. It works just > as well without. Yes, but do you really want to expose your Windows connections directly to the Net, risking a weak password? -- spam999free@rrohio.com remove 999 in order to email me |
|
#20
|
|||
|
|||
|
<snip>
> > > If your office DSL is not a fixed IP address, well, since it can change > > > on a daily basis, it would be impossible for you to GUESS the office > > > network public IP address - you would have to get someone at the office > > > to tell you the IP address and then you could do it using the other VPN > > > or direct (port forwarding method). > > > > An easy solution to this problem is provided free of charge by > > companies such as www.no-ip.com or www.dyndns.org. > > Yes, but you might still want a fixed IP so that everything works all > the time and perfectly. Imagine the headache it causes when the lease > expires and the new IP has not replicated to the public DNS servers yet. I have several clients with dynamic addresses. Since the addresses are stable, they don't have a problem. They know that they get a new address after a power failure, and they know that they need to wait ten minutes until the new address is known. Nice'n'easy! > > > What you need to do is ask the Administrator if they have VPN setup on > > > the Windows 2003 server or if they have VPN Setup on the Firewall. If > > > they run a Dual NIC setup and SBS 2003, then you will use one solution > > > path, if a single NIC and a NAT Router, then it's another path. > > > > You do not need a VPN for Remote Desktop. It works just > > as well without. > > Yes, but do you really want to expose your Windows connections directly > to the Net, risking a weak password? Same with a VPN: You're exposed with a weak password too! |