| Author |
Message |
Wynne
Guest
|
 Posted:
Sun Nov 21, 2004 9:18 pm Post subject:
new router - old dog |
|
|
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 |
|
| Back to top |
|
 |
Brian Sullivan MVP
Guest
|
| Posted:
Sun Nov 21, 2004 9:31 pm Post subject:
Re: new router - old dog |
|
|
Wynne wrote:
| Quote: |
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...
|
| Quote: | but when I start netmeeting or when I run ipconfig I can
only see a local ip addy.
|
That would be normal for any pc behind any router.
| Quote: | 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?
|
If your router is configured to forward tcp 1503 to your machine ( or you
are using the dmz feature) - you can be called by using the public/WAN IP
address of the router as the calling address. To accurately determine your
current WAN IP you would look in one of the router configuration panels
(generally accessible via http://192.168.x.x -- in internal IP address of
the router -- exactly where to look is router specific but is often on the
initial display page)
| Quote: | 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 am not sure what "enabling netmeeting under the virtual serving settings"
means in the context of your router.
| Quote: | 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?
|
You determine the address to call other than locally (unless they are
calling your from your internal network). Using the router configuration
information is the recommended strategy,
--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp |
|
| Back to top |
|
|
Stefan Renzke
Guest
|
| Posted:
Mon Nov 22, 2004 1:11 am Post subject:
Re: new router - old dog |
|
|
"Wynne" <impy2101@yahoo.com> wrote:
| Quote: | 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 do. There is a site where I can look up my public IP to give it to callers
http://www.uni-essen.de/cgi-bin/info
| Quote: | 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.
|
That's the same procedure that worked for me. My computer is behind a
DI-624, too.
Regards,
Stefan |
|
| Back to top |
|
|
Wynne
Guest
|
| Posted:
Sat Nov 27, 2004 4:03 am Post subject:
Re: new router - old dog |
|
|
"Stefan Renzke" <anonymous@positively.invalid> wrote in message news:<OaCUJZA0EHA.3028@TK2MSFTNGP10.phx.gbl>...
| Quote: | "Wynne" <impy2101@yahoo.com> wrote:
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 do. There is a site where I can look up my public IP to give it to callers
http://www.uni-essen.de/cgi-bin/info
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.
That's the same procedure that worked for me. My computer is behind a
DI-624, too.
Regards,
Stefan
|
Ok, cool. Thanks! That is the trick to know the addy. I got a chance
to check this out. But here's the other thing...I have them use
Tools/Share Desktop to get on their computer to look at issues. I
found that if I have them call me they (and I) cannot share the
desktop. Does this require an addtional enabling?
Thanks! |
|
| Back to top |
|
|
Brian Sullivan MVP
Guest
|
| Posted:
Sat Nov 27, 2004 5:19 am Post subject:
Re: new router - old dog |
|
|
On 26 Nov 2004 15:03:09 -0800, Wynne wrote:
| Quote: | I do. There is a site where I can look up my public IP to give it to callers
http://www.uni-essen.de/cgi-bin/info
Ok, cool. Thanks! That is the trick to know the addy. I got a chance
to check this out.
|
The only thing to be aware of though is the most of these http sites will
show the incorrect IP address if your browser is configured to use an http
proxy. If you are sure you are not behind a proxy (many ips do this by
default) this method should work.
The most reliable method is still to use the router configuration page (
usually accessible via the browser so it really isn't any more difficult).
| Quote: | But here's the other thing...I have them use
Tools/Share Desktop to get on their computer to look at issues. I
found that if I have them call me they (and I) cannot share the
desktop. Does this require an addtional enabling?
Thanks!
|
This is likely not be a router issue -- when this happens can you use other
data functions (whiteboard, text chat, file transfer)? If so then no router
or firewall is blocking tcp 1503 ( used for all these functions) -- your
problem will be elsewhere. You say you cann share the desktop -- what does
this mean -- do you get an error message, are functions disabled or ...? |
|
| Back to top |
|
|
Impy
Guest
|
| Posted:
Sun Dec 19, 2004 12:24 am Post subject:
Re: new router - old dog |
|
|
Hi Brian,
Thanks for your patience. It took me awhile to figure out what was
happening. I find...and it is random it seems...that we can connect and
then clicking on the Tools/Sharing the box will result in the Share
dialog box popping up but it says: Not in a Meeting and so the sharing
is not allowed. I believe this is true with the other functions. The
one time I had a friend helping me, when I could not share the desktop,
we also could not chat, whiteboard, etc. I didn't notice it at the time
but I think the display probably said the same thing: Not in a Meeting.
I hate asking my users to work with me while I experiement with this
but I think this is the case. I had tried experimenting with my router
settings and didn't get far. Why would we be able to connect but get a
"not in a meeting" error when trying one of the functions? And
furthermore...why does it happen sometimes and not others? |
|
| Back to top |
|
|
Impy
Guest
|
| Posted:
Sun Dec 19, 2004 12:39 am Post subject:
Re: new router - old dog |
|
|
I should have put this with my last posting.
Here are all the settings in my D-Link AirExtremeG 2.4GHZ Wireless
Router online configuration:
Advanced Tab:
Virtual Server
(Virtual Server is used to allow Internet users access to LAN services
)
NetMeeting 192.168.0.100 TCP 1720/1723 Always
Firewall Rules
(Firewall Rules can be used to allow or deny traffic from passing
through the DI-624. )
Allow NetMeeting WAN,* LAN,192.168.0.100 TCP,1720
Allow NetMeeting_ADV WAN,* LAN,192.168.0.100 TCP,
DMZ
(DMZ (Demilitarized Zone) is used to allow a single computer on the LAN
to be exposed to the Internet.
Enabled)
IP Address 192 .168 .0 .100
I am also running ZoneAlarm on the pc that I put in the DMZ
192.168.0.100. |
|
| Back to top |
|
|
Brian Sullivan MVP
Guest
|
| Posted:
Sun Dec 19, 2004 4:17 am Post subject:
Re: new router - old dog |
|
|
On 18 Dec 2004 11:24:05 -0800, Impy wrote:
| Quote: | Hi Brian,
Thanks for your patience. It took me awhile to figure out what was
happening. I find...and it is random it seems...that we can connect and
then clicking on the Tools/Sharing the box will result in the Share
dialog box popping up but it says: Not in a Meeting and so the sharing
is not allowed. I believe this is true with the other functions. The
one time I had a friend helping me, when I could not share the desktop,
we also could not chat, whiteboard, etc. I didn't notice it at the time
but I think the display probably said the same thing: Not in a Meeting.
I hate asking my users to work with me while I experiement with this
but I think this is the case. I had tried experimenting with my router
settings and didn't get far. Why would we be able to connect but get a
"not in a meeting" error when trying one of the functions? And
furthermore...why does it happen sometimes and not others?
|
It sounds like you are *not* facing a router issue.
NetMeeting calls are really two calls in parallel - an H.323 one for
audio/video and a T.120 one for data sharing functions. The calls connect
separately -- the H.323 first followed by the T.120 one (by design). It is
also possible to force calls to be just H.323 or T.120.
Because the H.323 part of the call connects first, there will always be a
time(usually short) after the call starts when you will try a data
function and get "Not in Call". The data portion of the call seems to take
longer to connect when one party is on a lower speed line and video starts
immediately on connection. Sometimes (probably becuase of some internal
timeout -- but I don't know for sure) the data portion of the call fails to
connect altogether. I have found the best way to avoid this issue (at least
it seems to work) is to avoid starting video on call connection ( a setting
in the video options tab), wait until the data part of the call connects (
10 or 15 seconds or so) and then start video.
Other than that I can't think of any remedy.
--
Brian Sullivan (MVP)
Meeting by Wire ( www.meetingbywire.com) |
|
| Back to top |
|
|
Impy
Guest
|
| Posted:
Mon Dec 20, 2004 8:01 am Post subject:
Re: new router - old dog |
|
|
Ah...that makes sense. In fact, I have some of my user's initially
disable the video view (View/Data Only) because I think it's
distracting. And maybe that is why it works "sometimes and not others".
The last time I had this problem, my user had dial-up...it's all
falling into place now...:-) Thanks, I'll give this a shot and report
back. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in