Re: [Fwd: Re: [AT] Help configuring AT with XP and Crossover Cable]

I vaguely remember that there is an XP security setting that is real deep
that someone found.  It bit them after they upgraded.

Hopefully this jogs someone else's memory.

--Stephen

At 11:11 AM 2/20/2005 -0500, you wrote:
>So, how many folks does it take to get an Audiotron to...
>
>Here's some more tips from the horse's mouth (i.e., Turtle Beach) that
>may help:
>
>Error 53 is a Networking error message.  It means:
>
>     C:\>net helpmsg 53
>
>     The network path was not found.
>                   --------------------------
>
>*  Try pinging the AT and then your server.  If you get a response, then
>check to make sure the share is visible to the network by using the "net
>share" command.  If that is OK, then temporarily disable the Norton
>Personal FW and try the connection again.  Moving the share to another
>disk shouldn't    matter unless in the move the share was deleted and
>didn't get set back up.   The only other culprit is the FW.  Check the
>rules if all else fails.
>
>*  Norton Internet security can quietly hide stuff from the AT. If you
>quickly disable Norton (assuming you even run it) and it works, then you
>know that was it. You can fine-tune Norton to like your AT.
>
>*  If Internet Connection Firewall is enabled, it could cause the
>AudioTron    query for name resolution to fail. Most (large?)
>corporations are requiring    their employees accessing the corporation
>network through VPN to enable    ICF.
>
>*  If you're using XP, do not forget to turn off the built in firewall:
>Right click on Network Places > Properties > Local Area Connections >
>Properties > Click the Advanced tab...
>
>*  If you continue to receive this error please go through the steps
>below:    Download the latest AudioTron Setup Utility. Unshare you music
>directory    and start the Setup Utility. Check Audiotron Network
>Connection. Then do   the Search Local PC for Music Files test. When it
>finds the directory with    your music click on the FIX IT button (even
>if it says the folder is    accessible to the Atron).
>
>*  Disable the IPSec Service (Win2000/XP only):  Open your control panel
>on the server and then double-click on ADMINISTRATIVE TOOLS. Then
>double-click on SERVICES. Scroll down and look for IPSec. Double-click
>on it and stop it.
>
>                   --------------------------
>
>*  Windows XP only:
>    *  Move your folder containing the music to another directory and
>then       move it back.
>
>*  Windows 2000/XP only: *  Reset the TCP/IP protocol. Right click on My
>Network Places and choose Properties. Now right click on the Local Area
>Connection and choose Properties. Scroll down and remove the check mark
>for "Internet Protocol TCP/IP" and hit the OK button. Reboot the
>computer. Follow the steps above again but this time put a check mark
>back in "Internet Protocol TCP/IP" and hit the OK button.
>
>
>-----Original Message-----
>From: Turtle Beach Audiotron User Forum
>[mailto:[email protected]] On Behalf Of Tim Carlson
>Sent: Sunday, February 20, 2005 9:54 AM
>To: [email protected]
>Subject: Re: [AT] [Fwd: Re: [AT] Help configuring AT with XP and
>Crossover Cable]
>
>Ok, the AT can ping outside and inside names e.g. TURTLEBEACH.COM,
>TC-XP-
>HM.
>
>I verified that File Sharing is checked for the connection.
>
>I've tried using the AT Setup Utility.
>When I do "Check AudioTron music file playback", it creates it's little
>test share - C_AUDIOTRON and the music file, but the test fails. It says
>
>"Host PC: \\TC-XP-HM
>Host error code 53 error string: The network path was not found."
>
>So, I wonder if it's an XP Firewall issue or something like that. I've
>tried disabling the firewall, but I get the same results. This is just
>weird.
>
>Thanks,
>
>Tim
>
>
>
>
>
> >
> >-------- Original Message --------
> >Subject:        Re: [AT] Help configuring AT with XP and Crossover
>Cable
> >Date:   Sat, 19 Feb 2005 21:42:57 -0800
> >From:   Tim Hill <[email protected]>
> >To:     [email protected]
> >References:     <LISTSERV%[email protected]>
> >
> >
> >
> >OK, you've got the PC NIC#2 and AT on the same subnet now, which is
>correct.
> >
> >The gateway comes in when accessing the internet. Basically, the
>gateway
> >is the address that packets need to be sent to that are now destined
>for
> >the local subnet. it goes something like this...
> >
> >1. Device or PC wishes to send data to a computer at another IP
>address.
> >2. Q: Is the destination on the same subnet (i.e. is the "network
> >number" of the destination the same as the sender network number)?
> >3. A: Yes: Just send the packet directly, since the computer is on my
> >subnet.
> >4. A: No. Send the packet to the gateway instead, and let it figure out
> >how to forward it to my desired destination.
> >
> >So, in your case the AT can connect to your PC directly, but needs the
> >gateway to talk to the internet. Also note that, implied in the above,
> >is that the AT can talk to the gateway directly, which by definition
> >means the AT and the gateway must be in the same subnet.
> >
> >So the gateway setting for the AT must be the same as the IP address of
> >NIC #2 on your PC. So far so good. You can ping the PC from the AT,
> >which is also good. Now you have three problems to solve...
> >
> >1. Can the AT access the internet? This tests if the PC is correctly
> >acting as a gateway and forwarding packets for the AT. You can test
>this
> >by getting the AT to ping an internet address (you MUST do this by IP
> >address, not by name -- names come later). Find a webs ite you can ping
> >from your PC, note the IP address, and try it from the AT.
> >
> >2. Can the AT resolve names? This is the DNS stuff. Once #1 is working,
> >you really should be able to simply use the same IP address as your PC
> >is using, since DNS requests are routable. But this won't work until
> >you've got the ping working in step #1.
> >
> >3. Can you access shares on the PC? I'm assuming you can ping the PC
> >from the AT. If you cannot access shares, you should start checking the
> >network bindings on your PC. First, in Control Panel Networks, look at
> >the Properties for the NIC (#2) connected to the PC. You should see
> >"File and Print Sharing for Microsoft Networks" listed and checked. If
> >its not there, add it, since this is the component that listens for
> >share-level access over the network.
> >
> >--Tim
> >
> >