N. Miller
Guest
|
 Posted:
Mon Apr 18, 2005 1:11 am Post subject:
Re: Netmeeting access via LAN |
|
|
In article <d3bg3h$ihu$1@sparta.btinternet.com>, Alanf says...
| Quote: | Since setting up a router with integral firewall it seems that I cannot
access other users, or any Netmeeting directories and so on. I used to be
able to send my IP address to another user and they could then connect to
me directly and easily. Now that seems impossible.
Netmeeting defines my IP as *** *** *** ***
When I look at the definitions as revealed by the router I get
LAN IP *** *** *** ***
Default *** *** *** ***
Primary DNS *** *** *** ***
Sec DNS *** *** *** ***
In each case the details are different. Which is the correct IP to notify
another user so that they can connect to me?
Any help would be appreciated as this seems an insoluble problem at the
moment.
|
It should be pretty obvious; just use IP address *** *** *** *** to contact
the other party.
Seriously, in my case, I have:
LAN IP: 192.168.102.100
Default (Gateway?): 192.168.102.1
Primary DNS (Not WINS Server?: Not listed as.
Secondary DNS (Not WINS Server: Not listed as.
The question marks relate to what I see under "Winipcfg", a Windows ME GUI
tool which is equivalent to the Windows XP "ipconfig /all" command.
For NetMeeting on my LAN, it is enough to enter the IP address of any other
computer running NM. If I use 192.168.102.101, I will get the only other
computer currently running on my LAN.
Or, I could use the NetBIOS computer names, instead. I don't recall if NM
can find them from the network properties, or if it needed to check the
hosts file; but I have entries in the hosts file because some piece of
software I use need it to tell that 192.168.102.100 is "Megumi".
--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in