Re: Help configuring AT with XP and Crossover Cable]

Tim Hill <[email protected]> Thu, 24 Feb 2005 11:39:41 -0800
Newsgroups gmane.comp.hardware.voyetra.audiotron
Message-ID <[email protected]>
Agreed -- at least in theory if he has full control of the router he can
pretty much open up anything -- even setting his PC as the DMZ.

--Tim

Chris Dickens wrote:

>Tim:
>
>He hasn't mentioned anything about a VPN yet, so I'm assuming he doesn't use
>one.  Also, if port forwarding is set up for some things on the corporate
>router, then this configuration would firewall those ports back off at the
>second router, but that's also unlikely.  Worst case scenerio, he could try
>it and if he has any trouble, just go back to the way it was before and keep
>troubleshooting.  If no trouble, then he just saved a lot of time - that's
>the way I look at it.
>
>--Chris
>
>-----Original Message-----
>Date:    Wed, 23 Feb 2005 10:35:36 -0800
>From:    Tim Hill <[email protected]>
>Subject: Re: [Fwd: Re: [AT] Help configuring AT with XP and Crossover Cable]
>
>My problem with that is that with the PC the wrong side of a private router,
>he may have trouble getting access to some corporate resources on his LAN.
>
>--Tim
>
>Chris Dickens wrote:
>
>
>
>>Tim:
>>
>>Skip the second NIC like Tim says.  Configure it like this:
>>
>>       [Internet] <--> [Company Router] <--> [Your Router]
>>                                            |      |
>>                                           [PC]   [AT]
>>
>>Set your PC and AT for DHCP and the router for the same and you should
>>be golden.
>>
>>--Chris
>>
>>-----Original Message-----
>>Date:    Tue, 22 Feb 2005 21:51:02 -0500
>>From:    Tim Carlson <[email protected]>
>>Subject: Re: [Fwd: Re: [AT] Help configuring AT with XP and Crossover
>>Cable]
>>
>>Yeah, the whole thing started because the router I'm on belongs to the
>>company, and I want to take the AT off of it. I thought this would be a
>>simple thing to do.
>>
>>Yes, everything works fine if I plug both the PC and the AT into the
>>router.
>>
>>Thanks for all the help.
>>
>>-Tim
>>
>>On Tue, 22 Feb 2005 13:22:21 -0800, Tim Hill <[email protected]>
>>wrote:
>>
>>
>>
>>
>>
>>>Unlikely to be a cable issue since you can access the internet and
>>>ping. I'm curious... if you connect the AT to NIC #1 can you access
>>>the shares?
>>>
>>>I'm also trying to recall the reason for not having the AT on the NIC1
>>>LAN segment? If you've prepared to get another cheap router (and that
>>>might be the best way) I would ditch the whole second NIC thing and
>>>place you PC and the AT the other side of the router.
>>>
>>>--Tim
>>>
>>>Tim Carlson wrote:
>>>
>>>
>>>
>>>
>>>
>>>>Yes, I'm trying to get the AT off of the router. So, I plug my NIC#1
>>>>into the router which is connected to the Internet, then the AT plugs
>>>>into NIC#2. In order for the AT to access Turtle Radio, I have to
>>>>share the connection that is established via NIC#1, at least that's
>>>>my understanding. If there's another way to do that, then let me
>>>>know.
>>>>
>>>>What I'm thinking about trying is:
>>>>
>>>>
>>>>     AT<----->new cheap router<------->XP(NIC2)
>>>>                                          |
>>>>                                          |
>>>>                                        XP(NIC1)<---->router<--
>>>>
>>>>
>>>>
>>>>
>>>Internet
>>>
>>>
>>>
>>>
>>>>I'll keep the "new cheap router" off of the Internet if I can and try
>>>>sharing the Internet connection established by NIC1. If I can't, then
>>>>
>>>>
>>>>
>>>>
>>I'll
>>
>>
>>
>>
>>>>get another IP address, and run two separate systems.
>>>>
>>>>Any suggestions for the "new cheap router"?
>>>>
>>>>Also, as a last ditch effort on the Xover cable method, I was
>>>>wondering
>>>>
>>>>
>>>>
>>>>
>>if
>>
>>
>>
>>
>>>>it was a duplex issue? It seems that I read somewhere that the AT
>>>>
>>>>
>>>>
>>>>
>>operates
>>
>>
>>
>>
>>>>at half duplex. I haven't checked the NIC2 card, but maybe it's set
>>>>at full and maybe that's the issue.
>>>>
>>>>-Tim
>>>>
>>>>
>
>------------------------------
>
>End of AUDIOTRON Digest - 22 Feb 2005 to 23 Feb 2005 (#2005-52)
>***************************************************************
>
>
>
>