new router - old dog
From: Wynne (impy2101_at_yahoo.com)
Date: 11/21/04
- Next message: Brian Sullivan MVP: "Re: new router - old dog"
- Previous message: Brian Sullivan MVP: "Re: Remote desktop sharing"
- Next in thread: Brian Sullivan MVP: "Re: new router - old dog"
- Reply: Brian Sullivan MVP: "Re: new router - old dog"
- Reply: Stefan Renzke: "Re: new router - old dog"
- Messages sorted by: [ date ] [ thread ]
Date: 21 Nov 2004 08:18:47 -0800
Sigh...I guess it's true that you can't teach an old dog new tricks. I
have a new DI-624 D-Link wireless router. And I can't quite figure out
if I've set it up right.
I've always used DSL in the past and I have a number of home clients
that I connect to via Netmeeting. I had a software firewall and a DSL
modem. So I had an IP address I could give to the client to 'call' me.
The primary purpose for netmeeting is to have them share their desktop
and then I can conduct examinations/repairs, whatever.
I've gone through the setups of the di-624 and there are a number of
settings to allow netmeeting to work through...I've got them
configured...but when I start netmeeting or when I run ipconfig I can
only see a local ip addy. Is there some obvious answer here that I'm
not seeing? Do other people use ip addy's to connect with netmeeting
or some other means?
I assigned my pc that I use for the clients with a static ip, I then
placed that address beyond the dmz. I enabled netmeeting under the
virtual serving settings. I also enabled netmeeting under the firewall
rules. Now how do I get my clients to call me if ipconfig and
netmeeting only show a local ip address?
Thanks,
Wynne
- Next message: Brian Sullivan MVP: "Re: new router - old dog"
- Previous message: Brian Sullivan MVP: "Re: Remote desktop sharing"
- Next in thread: Brian Sullivan MVP: "Re: new router - old dog"
- Reply: Brian Sullivan MVP: "Re: new router - old dog"
- Reply: Stefan Renzke: "Re: new router - old dog"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|