RE: Terminal Server Connecton Mystery

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


-- Thanks ,I think you got it. I had to get a new Internet account for this
network, and I Only got 1 public IP address for it. I disabled the second
nic, and forward the IP of the terminal server to the new public IP. It now
only has one gateway to look at, and thus far has eliminated my problem.

Thanks for your quick responses, and I applogize for my tardiness in getting
back.


stevie6


"Dragos CAMARA" wrote:

if i understood your router is forwarding 215 to 192.168.100.254 with a
gateway 192.168.100.1 , if so remove this gateway from 192.168.100.254.
or forward 215 to 192.168.1.5 and remove that network card with 100.254. I
don't see the reason of have 2 nic card's unless you plan a isa or another
firewall there.
if it was worked maybe is a problem with clients wich have broken connections.
--
Dragos CAMARA
MCSA Windows 2003 server


"stevie" wrote:

I messed up in my last thread, I meant the nic for the terminal was
192.168.100.254, with the gateway as 192.168.100.1. and is connected a switch
which is fed by the ISP's router.
--
stevie6


"stevie" wrote:

Dragos, Thanks for getting back.
I was wondering if that might be the problem.The Isp's router, obviously
feeds every thing. The internal numbers assigned to me from their router is
192.168.100. 2 through 5, with 192.168.100.1 for the gateway. I use
192.168.100.2 for the wan of the linksys router. 192.168.1.5 through 254, for
the local workgroup.
So one card in the server is set to 192.168.1.5, with a gateway of
192.168.1.1.and is connected to the linksy.
The card to the Terminal is set to 192.168.100.254, with a gateway of
192.168.100.254 and is connected to the ISP router.

I have 2 public Ip's assigned from the Isp, which is xxx.xxx.xxx 214 and one
that is xxx.xxx.xxx.215 . Now 215 points to 192.168.100.254 and is dedicated
to the terminal.

I hope you can understand me, cause I am confusing myself. lol
What should the proper gateway be for the terminal card, and why would it
work for 2 years, then all of a sudden start this problem?

--
stevie6


"Dragos CAMARA" wrote:

hi,
it could be a problem with default gateways , you must have only one default
gateway even you have multiple nic's.
--
Dragos CAMARA
MCSA Windows 2003 server


"stevie" wrote:

yeah, It's a windows 2003 server. I have 6 people that work off of it, in the
office, one card goes to a linksys router, that supports the Lan. I have the
terminal installed, and dedicated to the other Nic, which goes to a switch,
and a router provided by the ISP. I have 3 people from the outside that work
off of the terminal.
--
stevie6


"Dragos CAMARA" wrote:

hi,
theese two nic are on terminal server?
--
Dragos CAMARA
MCSA Windows 2003 server


"stevie" wrote:

I have had a W2k03 SP1 Terminal up for a couple of years. About 4 months ago,
I allowed it to perform a windows update run,our connection issue began.The
problem only involves my outside clients. They can no longer recieve a
consistant connection. It might work for 10 minutes or 10 hrs. It can be
brought back up, by login onto the server, and establishing a remote
connection using the public IP. After that its back to the same thing. I have
applied hotfix 898060, but this didn't help.
I do have 2 routers and 2 nics involved, with one nic assigned to the TS,
which is connected to 1 router. The other nic is for the lan, on the other
router. Each nic is assigned to the gateway of the router, to which it is
connected. Could this be part of my problem?
stevie6
.

Relevant Pages

  • Re: Physically Relocating An SBS box
    ... The VPN connection is a persistent link created by the Symantec Gateway ... Sytems 360 Router. ... > recommend letting the SBS server handle this and not the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: home lan setup suggestions
    ... for your router, set an administrative password, and disable UPnP ... Connection: Auto-dhcp ... Default gateway: xxx.xxx.xxx.N+1, being the IP assigned by ISP ... Router's gateway should be the modem, and modem's gateway should be the ISP's, so router dialog should tell me its gateway is 192.168.0.1. ...
    (comp.security.firewalls)
  • Re: Moden setup
    ... > earlier,to my router, is the best option. ... This is the "gateway" for all outbound IP routes from your dial-up ... connection and is dynamically assigned at connection time (i.e. it may NOT ... Try not to use them when assigning/allocating local IP addresses ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Ping timeouts - what do they mean?
    ... Machine 1: Laptop ... default gateway, DNS and WINS 192.168.0.1 ... This hard coded in this router. ... Lan connection static IP: 192.168.0.1 ...
    (microsoft.public.windowsxp.network_web)
  • Re: Urgent! New router and big disaster
    ... by CEICW for any type of connection other than full time broadband was ... exists - is completely transparent to the SBS. ... "local router with an IP address" is the setup that matches her network. ... between the server and my cable modem. ...
    (microsoft.public.windows.server.sbs)