Re: Help configuring AT with XP and Crossover Cable

Duh! I think John has it. I was busy looking for something far more subtle!

To add some detail... Basically all the computers on the same LAN need
to be in the same IP network, while computers on different LANs need to
be in different networks (yes, I'm simplifying...). Being on the "same
network" isn't a *physical* thing (i.e. same cable), its to do with the
IP address. Each IP address is split into two parts -- the first is the
"network number", the second is the "host number" (also called lots of
other things). Being "on the same network" in IP terms means sharing the
same network number, i.e. all computers on a LAN should have the same
network number. At the same time, all computers on the same network must
have a different host number.

To make things more "fun", the split of the IP address into network
number and host number can vary. That's where the subnet mask comes in
(again, I'm going to simplify here a lot). Essentially, a subnet mask of
255.255.255.0 means the first 3 parts of the IP address are the network
number, while the last part is the host number. Or a subnet mask of
255.0.0.0 means the first part of the IP address is the network number,
while the last 3 parts are the host number. It actually makes sense in
binary, but we can ignore this for now.

So your problem is that the AT is in one network (10.0.0.0) while the PC
is in another network (192.168.0.0). To get everything correct, as John
says, move the AT to the 192.168.0.0 network. It should be able to "see"
your PC correctly.

--Tim



john wrote:

>Hmmm, if I'm understanding your post correctly, you've got the WinXp box
>on 192.168.0.1 with a subnet of 255.255.255.0.  Is your Atron still at
>10.0.0.1?  If so, give the Atron 192.168.0.10 (or whatever), with the
>same subnet and see what you get.  I take it the xover cable is
>connected to NIC3, correct?  (It should be for this to work.)
>
>The Atron should be fine seeing NIC3 and the XP's Local Area Connection
>(NIC1 or whatever) should still see the internet.  Don't give a default
>gateway to either the NIC3 or the Atron, as they're not needed.
>
>I think you just about there!  Keep at it... You'll be up and running
>this weekend...
>
>John
>
>-----Original Message-----
>From: Turtle Beach Audiotron User Forum
>[mailto:[email protected]] On Behalf Of Tim Carlson
>Sent: Friday, February 18, 2005 10:40 PM
>To: [email protected]
>Subject: Re: [AT] Help configuring AT with XP and Crossover Cable
>
>Ok, I'm getting close. I now can get to the Internet with the AT, but it
>can't find the shares. Here's the dump from ipconfig /all:
>
>
>Windows IP Configuration
>
>
>
>        Host Name . . . . . . . . . . . . : tc-xp-hm
>
>        Primary Dns Suffix  . . . . . . . :
>
>        Node Type . . . . . . . . . . . . : Peer-Peer
>
>        IP Routing Enabled. . . . . . . . : Yes
>
>        WINS Proxy Enabled. . . . . . . . : No
>
>        DNS Suffix Search List. . . . . . : ad.dvd.com
>
>
>
>Ethernet adapter Local Area Connection 3:
>
>
>
>        Connection-specific DNS Suffix  . :
>
>        Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
>Fast Ethernet NIC
>
>        Physical Address. . . . . . . . . : 00-30-BD-71-86-85
>
>        Dhcp Enabled. . . . . . . . . . . : No
>
>        IP Address. . . . . . . . . . . . : 192.168.0.1
>
>        Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
>        Default Gateway . . . . . . . . . :
>
>
>
>Ethernet adapter Local Area Connection:
>
>
>
>        Connection-specific DNS Suffix  . : ad.dvd.com
>
>        Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
>For Complete PC Management NIC (3C905C-TX)
>
>        Physical Address. . . . . . . . . : 00-01-03-D4-56-F2
>
>        Dhcp Enabled. . . . . . . . . . . : Yes
>
>        Autoconfiguration Enabled . . . . : Yes
>
>        IP Address. . . . . . . . . . . . : 155.132.147.58
>
>        Subnet Mask . . . . . . . . . . . : 255.255.255.248
>
>        Default Gateway . . . . . . . . . : 155.132.147.57
>
>        DHCP Server . . . . . . . . . . . : 155.132.147.57
>
>        DNS Servers . . . . . . . . . . . : 155.132.138.22
>
>                                            66.7.169.1
>
>        Primary WINS Server . . . . . . . : 155.132.167.26
>
>        Lease Obtained. . . . . . . . . . : Friday, February 18, 2005
>5:55:13 PM
>
>        Lease Expires . . . . . . . . . . : Saturday, February 19, 2005
>5:55:13 PM
>
>**********************************************
>
>The NIC that talks to the AT is the Realtek. If I set the DNS to the
>same
>value as the gateway, 192.168.0.1, then the AT finds the Internet, but
>cannot find the shares. If I set the DNS to either 155.132.138.22 or
>66.7.169.1, then the AT can't even see the Internet, let alone the
>shares.
>
>So, I need to figure out how to get the AT to resolve the name :
>TC-XP-HM
>where the share is located.
>
>You guys have been a big help getting me this far, and I appreciate your
>help.
>
>Thanks,
>
>-Tom
>
>On Fri, 18 Feb 2005 12:18:15 -0800, Tim Hill <[email protected]>
>wrote:
>
>
>
>>Error 53 is "The network path was not found" so you still have some
>>address problems.
>>
>>You have two DNS problems to solve with this setup:
>>
>>1. DNS servers are routable. That is, you can set a DNS server that is
>>on a different subnet. So you can simply configure the AT with the same
>>DNS server address as your PC is using. To find this address, open a
>>command prompt and enter the command "ipconfig /all". You'll see a LOT
>>of stuff (and, in fact, if you could post the whole lot here it would
>>help). Look for the "DNS Servers" line on the ethernet card that
>>connects to your ISP (you have two cards now, so make sure to choose
>>
>>
>the
>
>
>>right one).
>>
>>2. Now the next problem is getting your AT to see the internet. This
>>requires that you setup a router between the two NICs so that your PC
>>will forward AT requests appropriately. You can do this in Control
>>Panel::Network.
>>
>>--Tim
>>
>>
>>Tim Carlson wrote:
>>
>>
>>
>>>The name of my PC is TC-XP. It's IP is 10.0.0.10, while the AT is
>>>10.0.0.20. Both can ping each other.
>>>
>>>I think the problem is that I don't have anything configured as the
>>>
>>>
>DNS
>
>
>>>server, because I don't know what that would be. On the Share Search
>>>options page, I've tried entering both \\TC-XP\Audiotron and
>>>
>>>
>\\10.0.0.10
>
>
>>>\Audiotron.
>>>
>>>When I use \\10.0.0.10\Audiotron, I get :
>>>
>>>Host TC-XP found at IP 10.0.0.10
>>>\\TC-XP - Error accessing host, Error = 53
>>>
>>>
>>>When I use \\TC-XP\Audiotron I get :
>>>
>>>Can't get IP address for host TC-XP-HM
>>>Completed Operation
>>>
>>>
>>>
>>>When the AT pings TC-XP it reports : Ping Failed: No DNS Server
>>>
>>>
>configured.
>
>
>>>I think I'm close, but I'm getting wrapped around the axle on the DNS
>>>server and/or gateway entries when running in this direct connect
>>>
>>>
>mode.
>
>
>>>Yes, I am running XP SP2 with Firewall. Are there any settings to make
>>>with that?
>>>
>>>Thanks,
>>>
>>>-Tim
>>>
>>>
>>>
>>>
>>>On Fri, 18 Feb 2005 04:49:16 -0500, john <[email protected]>
>>>
>>>
>wrote:
>
>
>>>
>>>
>>>
>>>>How have you configured the shares that the Atron is using?  Do you
>>>>refer to the "server" by name or the IP address?  If it can ping, but
>>>>not see the shares, it could be a name resolution, in which case
>>>>referring to the "server" (the one with the music shares) by IP
>>>>
>>>>
>should
>
>
>>>>help.  If you look for shares from the Atron interface, are there any
>>>>errors listed ("Host not found" or otherwise)?
>>>>
>>>>Any chance you're running WindowsXP with the firewall enabled?
>>>>
>>>>-----Original Message-----
>>>>From: Turtle Beach Audiotron User Forum
>>>>[mailto:[email protected]] On Behalf Of Tim Carlson
>>>>Sent: Thursday, February 17, 2005 11:59 PM
>>>>To: [email protected]
>>>>Subject: Re: [AT] Help configuring AT with XP and Crossover Cable
>>>>
>>>>I seem to be getting closer. After changing the binding order, I can
>>>>
>>>>
>now
>
>
>>>>see the Internet just fine using my #1 NIC.
>>>>
>>>>The #2NIC is connected to the AT and I can get to the web config
>>>>
>>>>
>pages
>
>
>>>>of
>>>>the AT, but I can't seem to get the AT to find my shares. The AT can
>>>>ping
>>>>NIC#2.
>>>>
>>>>On the AT, what does it want for Gateway and DNS Server values? I've
>>>>tried
>>>>using the IP of NIC#2 for the Gateway (10.0.0.2) but that doesn't
>>>>
>>>>
>seem
>
>
>>>>to
>>>>work.
>>>>
>>>>Again, the values I have entered for the AT are:
>>>>
>>>>IP 10.0.0.4
>>>>SN 255.255.255.0
>>>>Gateway 10.0.0.2 - The IP of the NIC at the end of the crossover
>>>>DNS - I have no idea what to enter here.
>>>>
>>>>
>>>>The NIC#2 in my PC:
>>>>IP 10.0.0.2
>>>>SN 255.255.255.0
>>>>Gateway - nothing, If I enter the IP of the router here, I lose the
>>>>Internet on my primary (NIC#1) connection.
>>>>
>>>>Any ideas?
>>>>
>>>>Thanks,
>>>>
>>>>-Tim
>>>>
>>>>
>>>>
>>>>We have a similar situation in our lab:  Frontend (network-facing)
>>>>
>>>>
>NIC
>
>
>>>>with gateway and Backend (private-subgroup-facing) NIC with no
>>>>
>>>>
>gateway.
>
>
>>>>Works fine.  The PC is going to need a gateway to get to the
>>>>
>>>>
>Internet,
>
>
>>>>so
>>>>the NIC connecting to the router needs the gateway, which should be
>>>>
>>>>
>the
>
>
>>>>IP
>>>>of the router.
>>>>
>>>>When we've had problems in the past, it's because the binding order
>>>>
>>>>
>had
>
>
>>>>the Backend NIC listed first, so it never saw the internet.  If you
>>>>
>>>>
>go
>
>
>>>>to
>>>>Network Settings in Control Panel, the Advanced Menu (up top),
>>>>
>>>>
>there's a
>
>
>>>>tab with the binding order listed.  Make sure your PC-to-Gateway NIC
>>>>
>>>>
>is
>
>
>>>>listed first.
>>>>
>>>>I hope I didn't confuse the hell out of you!  Sorry if I did...
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>
>
>
>