Connecting IEEE1394 device kills internet ?

[Someone]

Hello all - was hoping you could shed some light on the following problem
for me please ....

I've got a dual processor computer with a Audigy2 soundcard (and inbuilt
IEE1394 port) installed. The sound card works fine as does IEEE1394.

However I find that when I connect my Canon camcorder (MVX2i) to my
computer, it detects the connection as a possible network connection and as
far as I can ascertain, seems to start routing all internet traffic via my
camera instead of my 56k modem (yes - some of us still use these !)

Although once I connect the camera, my internet is "broken" I can then
transfer information (video + pics) to and from my camcorder without
problems.

The only way I have found to solve this problem is to do a system restore to
a point before the camcorder <-> computer connection took place.

I have been reading a few of the posts on here, and compared the following
reg keys from before and after the connection and they are exactly the same
:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock

I have also tried disabling the IEEE1394 Network adapter device in Device
Manager also without success. There are no conflicts in Device Manager.

Whilst I have the problem, I have done a few TCP/IP connectivity tests and
found something interesting - I can ping IP addresses without problems, but
can not do so via their hostname - even though the settings for the DNS are
correct.

In addition, doing an IP config at the command line shows a very weird
problem :

---
Pinging picard [?] with 32 bytes of data:

Reply from 62.255.96.77: bytes=32 time<1ms TTL=128
Reply from 62.255.96.77: bytes=32 time<1ms TTL=128
Reply from 62.255.96.77: bytes=32 time<1ms TTL=128
Reply from 62.255.96.77: bytes=32 time<1ms TTL=128

Ping statistics for Ôù?:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms



Windows IP Configuration

Host Name . . . . . . . . . . . . : picard
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft TV/Video Connection
Physical Address. . . . . . . . . : 00-00-00-00-00-00
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 4.0.2.0
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

PPP adapter NTL World:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-51-45-03-34-12
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.255.96.77
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 62.255.96.77
DNS Servers . . . . . . . . . . . : 194.168.4.100
194.168.8.100
NetBIOS over Tcpip. . . . . . . . : Disabled
---

Notice the characters after picard and it in the statistics section ... (and
yes I do like Star Trek)

I have also tried a TCP/IP reset using the command "netsh int ip reset
c:\resetlog.txt" without success.

I don't know how else to proceed.

Anybody got any ideas ?

Thanks in advance

Regards

 

[Someone]

Hey - Thanks for this info - I will try it and let you know what happens -
I've previously attempted to contact Canon's UK technical support without
success.

Thanks again !

 

[Someone]

Hi Seaver - I still haven't had a chance to collate the information you
requested or try the procedure outlined below, but could the MS
Knowledgebase article number 298646 have anything to do with this
connectivity problem ?

 

[Seaver]

Dear Customer,

The symptom described in 298646 article has been confirmed a Windows bug.
Currently we are working closely with related vendors on the issue, please
be patient and keep accessing Windows Update website at least monthly to
get the patch's latest information.

In the meantime, feel free to contact Canon by calling 1800 816 001 for the
latest information.

Thanks for your patience and understanding.

Sincerely,

Seaver

 

[Someone]

Hi Seaver - I have now downloaded and installed the software located on the
webpage below WITHOUT success - i.e. the problem still happens.

Are there any further steps I can take to resolve this issue ? Is there any
information (e.g. registry entries) which you would like to examine the
problem in further detail ?

 

[Seaver]

Dear Customer,

This bug is supposed to be resolved in the next version of XP Service
Pack(SP2). Currently no seperate patch has been released, we are sorry for
any inconvenience brought.

Your understanding is appreciated. Thank you.

Regards,

Seaver

 

[Someone]

OK - that knowledgebase article SEEMS to address the problem I am having -
is there anyway you could confirm this ? Or is it a different problem to the
one I am experiencing ?

I am going to ask you a question now which you may not want to respond to
....

Is there an ETA for the XP SP2 release date ?

Thanks

 

[Seaver]

Dear Customer,

What's listed in our last threads are the latest information about the
298646 issue, which corresponds with your problem, it's confirmed that no
separate patch has been released so far. As for XP SP2, we may release it
in next summer. Please keep accessing http://windowsupdate.microsoft.com/
or http://www.microsoft.com/windowsxp for the latest information.

Regards,

Seaver

 

[Someone]

OK Thanks for letting me know.

 

[Someone]

Forgot to say - if there is any additional information you need to identify
the problem please feel free to let me know.

 

[Someone]

Seaver - sorry to keep bothering you about this question, but do you know
why this problem occurs ?

I have done an export of the registry before connecting the camcorder and
after and compared the 2 registries and there is no difference ?

 

[Seaver]

Dear Customer,

Based on our supporting policy, the only information I can distribute is
that this bug lies in the limitation of designing IEEE 1394's network
adapter's driver interface with Windows XP, which is more advanced than
Registry. Close cooperation between hardware vendors and Microsoft is
necessary in delivering the hotfix.

Your patience and understanding is appreciated, thanks.

- Seaver

 

[Someone]

OK - Once again - Many Thanks for the information you have given so far

 

[Seaver]

Dear Customer,

Thank you for your reply and continual patience with us.

As always, thank you for choosing Microsoft.

Sincerely,

Seaver

 

[Someone]

Seaver - sorry to keep messaging you, but I thought you might be interested
to find out I seem to have solved this problem ...

When I cleaned out the registry after having uninstalled the anti virus
program I was using, I connected my webcam whilst on the internet and it
worked fine !

So this is fixed ! - Only one problem to go

Thanks again

 

[Seaver]

Dear Customer,

Thank you for the update on your specific issue. I suggest that you keep
monitoring the status for at least one day to ensure that the removed
registry entry is the root cause. After that, whether the 298646 issue
corresponds with that of your problem will then be clarified.

Regards,

Seaver

 

[Someone]

Seaver - I have since installed another anti virus vendor solution and can
still connect to the internet and use my camcorder via the FireWire port
simultaneously without problems - so I'm pretty confident it was the anti
virus solution which was causing this problem.

I have re-read this thread and although I didn't want to specify any product
names, I have the feeling that people reading this may get the wrong end of
the stick as to what anti virus solution I was and now am using. I was
using McAfee VirusScan v7 (which I had problems with) and am now using
Norton AntiVirus which I have NO problems with.

Doing a search on McAfee's website actually returns a technical article
which does seem to relate to problems regarding internet connectivity in all
v7 of VirusScan.

Thanks again Seaver