Hi, all. I'm working in the healthcare industry now but still check
up on you guys from time to time.
I have a nurse user who connects RDP from a local hospital through
their wireless network, using their static settings, gateway, and dns
servers. I created a simple batch file on her desktop that she uses
to set the ip addresses to make that happen. Then when she comes
into the office another desktop batch file sets her ip address on the
same wireless adapter to DHCP-connect to my network, sets the gateway
and dns so she can RDP here. That way all she has to know is to
click 'hospital' there and 'VNA' here. Everything else works exactly
the same either place.
The real reason I came here today is to ask advice on thin-clients.
WYSE has several models and configs and I'm in a quandry. Anybody
got any pros/cons?
tlw
up on you guys from time to time.
I have a nurse user who connects RDP from a local hospital through
their wireless network, using their static settings, gateway, and dns
servers. I created a simple batch file on her desktop that she uses
to set the ip addresses to make that happen. Then when she comes
into the office another desktop batch file sets her ip address on the
same wireless adapter to DHCP-connect to my network, sets the gateway
and dns so she can RDP here. That way all she has to know is to
click 'hospital' there and 'VNA' here. Everything else works exactly
the same either place.
The real reason I came here today is to ask advice on thin-clients.
WYSE has several models and configs and I'm in a quandry. Anybody
got any pros/cons?
tlw
--- In vantage@yahoogroups.com, "Todd Hofert" <todd@s...> wrote:
> I have a similar set-up on several laptops. I add the laptop to the
domain and log them into the domain in the office. Then I tell the
office wireless connection NOT to connect automatically. That way it
will never get DHCP settings from the office wireless network. I set
static IP info for the wired network connection. Then when the user
goes home, the log on to their PC exactly as if at the office
(including domain). Set the wirelss home connection to DHCP or obtain
automatically. The first time the user, when logged in at home may
have to do ipconfig /release and ipconfig /renew from the command
prompt to reload home network settings. After that they should not
have any problems anymore.
>
> Otherwise, doing ipconfig /release and ipconfig /renew will work
from home.
>
> ________________________________
>
> From: meco_inc_paris [mailto:admin@m...]
> Sent: Mon 1/31/2005 1:45 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: OT: LAPtops
>
>
>
>
>
> I did nothing with his settings
> He was able to connect to our network (With his domain uername &
> password) but could not connect at home
>
>
> --- In vantage@yahoogroups.com, "Jasper Recto" <jrecto@l...> wrote:
> > Did you change his IP address, Defaulte gateway and DNS to match
his
> home scheme?
> > Are you going through a proxy server? If so, did you change the
> setting for his IE?
> > Did you change the security setting on his wireless card? WEP?
> >
> > Just a few suggestions.
> > Jasperps Links
>
>
>
>
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You
must have already linked your email address to a yahoo id to enable
access. )
> (1) To access the Files Section of our Yahoo!Group for Report
Builder and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
>
> This e-mail and any attachments may contain confidential and
privileged
> information. If you are not the intended recipient, please notify
the
> sender immediately by return e-mail, delete this e-mail and destroy
any
> copies. Any dissemination or use of this information by a person
other
> than the intended recipient is unauthorized and may be illegal.
>
> [Non-text portions of this message have been removed]