|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
March 29th 10, 03:50 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
confused on ip log ons
Sometimes while my wife is on facebook and she chats with others there,
I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key) 
|
| Ads |
|
#2
March 29th 10, 07:48 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Hi
If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers. You probably should ignore it, IPv6 can not go on to the current Internet. If AES encryption is On the wireless is secured. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#3
March 29th 10, 07:48 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Hi
If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers. You probably should ignore it, IPv6 can not go on to the current Internet. If AES encryption is On the wireless is secured. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#4
March 30th 10, 02:13 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Well that is interesting to know that v6 is not needed yet. I don't recall
installing it, I am almost certain it installed by default when I first set up my LAN workgroup. I still get the normal 192.168.1.x of my local lan nodes also but from time to time I notice these other 64 bit hex numbers pop up. "Jack [MVP-Networking]" wrote in message ... Hi If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers. You probably should ignore it, IPv6 can not go on to the current Internet. If AES encryption is On the wireless is secured. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#5
March 30th 10, 02:13 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Well that is interesting to know that v6 is not needed yet. I don't recall installing it, I am almost certain it installed by default when I first set up my LAN workgroup. I still get the normal 192.168.1.x of my local lan nodes also but from time to time I notice these other 64 bit hex numbers pop up. "Jack [MVP-Networking]" wrote in message ... Hi If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers. You probably should ignore it, IPv6 can not go on to the current Internet. If AES encryption is On the wireless is secured. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#6
March 30th 10, 03:36 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Hi
Yeah it is installed by default on newer OS' and it can stay there and be ignored if not used for Local Traffic. Or you can uncheck it in the Connection Properties. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Well that is interesting to know that v6 is not needed yet. I don't recall installing it, I am almost certain it installed by default when I first set up my LAN workgroup. I still get the normal 192.168.1.x of my local lan nodes also but from time to time I notice these other 64 bit hex numbers pop up. "Jack [MVP-Networking]" wrote in message ... Hi If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers. You probably should ignore it, IPv6 can not go on to the current Internet. If AES encryption is On the wireless is secured. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#7
March 30th 10, 03:36 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Hi
Yeah it is installed by default on newer OS' and it can stay there and be ignored if not used for Local Traffic. Or you can uncheck it in the Connection Properties. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Well that is interesting to know that v6 is not needed yet. I don't recall installing it, I am almost certain it installed by default when I first set up my LAN workgroup. I still get the normal 192.168.1.x of my local lan nodes also but from time to time I notice these other 64 bit hex numbers pop up. "Jack [MVP-Networking]" wrote in message ... Hi If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers. You probably should ignore it, IPv6 can not go on to the current Internet. If AES encryption is On the wireless is secured. Jack (MS, MVP-Networking).. "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#8
April 7th 10, 12:41 AM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Probably local v6 traffic as suggested by Jack. Easiest way to check is to
open a command prompt and type ipconfig /all on each PC. Look at the result to see if your ethernet adapter has the address you have shown. Cheers, Jim "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
|
#9
April 7th 10, 12:41 AM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
confused on ip log ons
Probably local v6 traffic as suggested by Jack. Easiest way to check is to open a command prompt and type ipconfig /all on each PC. Look at the result to see if your ethernet adapter has the address you have shown. Cheers, Jim "RB" NoMail@NoSpam wrote in message ... Sometimes while my wife is on facebook and she chats with others there, I notice my BitDefender Lan log on notifications come up with ips that are not the normal 192.168.1.x local ip's of our NAT but rather these 64bit things like FE08:ED88:FC33:2314 which I surmise are ip address's coming from TCP v6 ? Appreciate any input on what these are. (By the way we are running AES encryption security on our wireless NAT router, with a very long key)
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
