Terminal Server & Broken Internet

Quote:

---

(1)Well that can be quiet common for public proxies to take that long.

(2)I think it is a problem with your DNS Server?

(3)Also, my next option would be to install ethereal and see what packets are going out from your Terminal Services Server - I've seen before where an awful lot of traffic from malfunctioning apps can cause this.

(4)Another thing to consider and I should have said earlier is a faulty network card - can you replace - even as a test?

---

1) I thought that might be the case
2) How can it be? It is using the same DNS Server as the rest of the network.
3) Great Idea!!!
4) Truely possible, but connection to the terminal server via RDP and using the applications installed (usualy at least 5 users) would imply the NIC is running smoothly.

Will it help to post the ethereal captures? Anyone who can understand and identify a problem?

[edit]I am getting huge amounts of Errors - Bad Checksum. This is when i am attempting to browse and AFAI can tell it seems that the packets are coming back corrupt or the whatever is doing the checksum is not right. And from what i can see this IS my problem right here..... the bad checksums[/edit]

Troubleshooting DNS issues is one of those things I just hate doing.

Now before I give advice, typically its good practice NOT to access the internet from a server. I know a lot of companies restrict this as to keep the risk of malware and virus to a minimum on servers. /Disclaimer

Have you tried a new network card? Have you tried IPCONFIG /flushdns

Have you tried entering a manual entry for another name server other than your Exchange box?

You know this sounds familar...

I had a problem with a site and web pages loading...some not

This was happening on all workstations...after working with the ISP we lowered our MTU setting on the router and all was well.

so...I did a search MTU Terminal Server

and found lots of stuff

http://www.google.com/search?q=MTU+t...e=utf8&oe=utf8

May wanna look at it and see if any relates to your situation...

Ms has some stuff too....

http://support.microsoft.com/search/...query=MTU&adv=

Hope this helps

MLF

Yeah post the ethereal outputs - one complete and the other filtered with only the bad checksums.

I think replacing the NIC nightn't be a bad idea - for test purposes.

Also, it's not harm adding a DNS Server for test purposes either.

Thanks MLF :) Will sus it out.

Quote:

---

(1)Now before I give advice, typically its good practice NOT to access the internet from a server. I know a lot of companies restrict this as to keep the risk of malware and virus to a minimum on servers. /Disclaimer

(2)Have you tried a new network card? Have you tried IPCONFIG /flushdns

(3)Have you tried entering a manual entry for another name server other than your Exchange box?

---

1)My aim is not to give internet access to users from the terminal server. It is simply to access the FTP website and upload files from the application that is installed on the terminal server. I can access the FTP site and download files but they will not upload.

2) Have not swapped the NIC yet, and yes DNS has been flushed.

3) Yes, i have used various other DNS servers, ones i know to work and use often. This does not help. Please note that all hostnames resolve completely so i dont think it is DNS related.

This Bad Checksum thing could explain alot and my first instinct as to why it is happening is a faulty NIC.... im sure others would agree. Anyways, i will post the ethereal logs tomorrow as its 1AM now and my bed beckons.

Thanks guys!!!


CTO

http://groups.google.com/groups?q=MT...=1&sa=N&tab=wg

Somemore reading ...same search in google groups

MLF

Whats the best way to post the ethereal logs? Plain text or text file attachment? It just seems exuberant.

Hi, pls.. solved a problem one at a time first check check your router configuration static or dynamic if its can connected to internet the terminal server is different story


here is a simple diagram

provider-router -------- your router/firewall---------hubs------> terminal, web-server and others



all this things could do via port forwarding

i hope this will help u

We've been over the basics pvclink, thanks anyways.

And CTO - post in an attachment if you can.