is the SBS a standard or premium...basically are you using ISA???
What version?
MLF
Printable View
is the SBS a standard or premium...basically are you using ISA???
What version?
MLF
This was already covered and mentioned, tried and done.Quote:
First thring I would try, is remove the Enhanced security crap on IE....Try that...if that doesn't work, install firefox or something and see and if we can browse the web via something other than IE.
I cant seem to find anything to indicate premium version however it does not say standard anywhere either. No there is no proxy or ISA server running, as i have already mentioned.Quote:
is the SBS a standard or premium...basically are you using ISA???
Results from the terminal server (The problematic server)Quote:
------------------------------------------------------------------------
Tracing route to www.l.google.com [72.14.253.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [exchange server name].[domain name].com.au.local [192.168.0.2]
2 1 ms 1 ms 1 ms 202-61-227-5.static.dft.net.au [202.61.x.x]
3 10 ms 10 ms 9 ms bdr0.per.dft.net.au [202.61.225.65]
4 9 ms 10 ms 9 ms ge0-1.core.dft.net.au [202.61.224.178]
5 8 ms 9 ms 10 ms VLAN214.o6ssc76fe.optus.net.au [61.88.166.113]
6 234 ms 226 ms * 203.208.148.73
7 228 ms 246 ms 271 ms ge-0-0-0-0.laxow-dr2.ix.singtel.com [203.208.171
.66]
8 288 ms 226 ms 267 ms 203.208.169.154
9 261 ms 242 ms 245 ms 216.239.43.126
10 254 ms 243 ms 244 ms 216.239.46.203
11 273 ms 297 ms 253 ms 209.85.250.67
12 249 ms 287 ms 242 ms 72.14.233.14
13 244 ms 247 ms 263 ms po-in-f99.google.com [72.14.253.99]
Trace complete.
------------------------------------------------------------------------
Correct. The Exchange server is the DHCP/DNS/Domain Controller as well as exchange. It is the "go to" server for all the workstations. It also hosts the company data. The Terminal Server is specifically for Terminal Services and is not running anything additional to this. I dont think it should be configured differently to any other working client, but could be wrong here.Quote:
Where Terminal Server is using Exchange Server as DNS server and default gateway ?
:) Cheers guys. Thanks for all your input.
CTO
Try one more thing for me?
On the Terminal Services Server, try using telnet:
telnet mail1.eircom.net 25
See if you can connect.
This will give us basic internet activity.
Have you any software firewall running on the Terminal Services Server?
Not that I can help, but just a few more things to clarify:
So, It is set up in what Microsoft calls a server environment. Because of this, and the fact you are not running ISA, you will be running and doing the NAT through Routing And Remote Access (RRAS) and the Basic Firewall on the Exchange Server.
1) What was working and what was changed when you noticed the problem?
2) You mentioned other clients. They have access to the Internet using web browsers with no problems?
3) What policy for the Basic Firewall are you using ( Domain? )
4) What do the logs for RRAS and the Exchange Server Basic Firewall show?
I think you just hit on the problem!!Quote:
Originally Posted by IKnowNot
If the Exchange Server is your main Domain Controller then each client logs on to the domain provided by exchange server and is registered. Each user is provided with Internet Access privlidges.
So if the Terminal Server is not part of the domain but using the correct gateways etc, then a logged on user will not have the correct privlidges within the domain of the Exchange Server.
Connected immediately "220 mail07.svc.cra.dublin.eircom.net ESMTP" response.Quote:
On the Terminal Services Server, try using telnet:
telnet mail1.eircom.net 25
The terminal server IS part of the domain. I also dont believe it to be a permissions level problem, but i will believe anything at this stage.Quote:
So if the Terminal Server is not part of the domain but using the correct gateways etc, then a logged on user will not have the correct privlidges within the domain of the Exchange Server.
NAT/Firewall on exchange server has absolutely nothing fancy and nothing that would cause this problem.
As you can see the Terminal Server does have internet connectivity. When using Internet Explorer the status bar displays "website found, waiting for page to load" and with www.google.com in particular (fast loading) the status bar displays "done" - as it finishes loading the page it looks like something was loaded but just a blank page.
----
Just noticed something interesting. Keep in mind what i said about the microsoft page loading forever and the google page loads but displays nothing. When i browse to www.antionline.com i get the IE This page cannot be displayed page;
Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.
I cannot ping www.antionline.com but can ping www.google.com and mail.bigpond.com (Biggest ISP Here)
I can open this FTP site: ftp://isr.serveftp.net/
I can download files from this FTP server. However, cannot upload files. It just hangs with the file copy/upload dialog box going nowhere. (Yes i have authenticated on the FTP server fine as i can upload files from any other workstation/server in the entire network. )
So with all of that in mind..... go figure? YES i have internet on the terminal server because i CAN download files from the ftp server. The FTP server is in no way logically or phycically local to this network.
I say again... go figure :p
Thanks for all your input with this again guys - most appreciated.
Frustrated CTO
Ok, well we can say that without a doubt the Terminal Services Server does have internet connectivity.
So I'm guessing that it is either a browser or a DNS problem.
Can you add 159.134.237.6 as your primary DNS Server - just for test purposes. Try connecting to a website now, something you haven't visited before so it won't be cached, try www.iol.ie
Another option would be to set IE up to go through an anon proxy server on the net - again for test purposes only.
http://www.publicproxyservers.com/page1.html
This has me stumped! But we'll keep trying.
THANKYOU! :)Quote:
This has me stumped! But we'll keep trying.
OMG! I actually opened a webpage with IE after using a public Proxy Server namely 165.228.131.10:3128 - It took at least 4 minutes for the page to appear which was www.ebroadcast.com.au .
Note:I have also fiddled with the TCP/IP Settings on the adapter to include the DNS Suffix and also the WINS Server address which again, is exchange. I dont think this has assisted in anything.
I have also started a new line of investigation. Instead of internet connectivity I am now looking at extremely slow internet on terminal services. Maybe that would be the next step?
[edit]That doesnt explain why some pages load with nothing, add www.hotmail.com to that list. [/edit]
CTO
Well that can be quiet common for public proxies to take that long.
I think it is a problem with your DNS Server?
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.
Another thing to consider and I should have said earlier is a faulty network card - can you replace - even as a test?
I Have also created a new account so it was a fresh profile with no cached pages etc but still same problems. So not a profile or caching issue.
I wont list sites that are working or not working because that wont help. It seems to be ....... random/sparodic on which pages load and which dont. For exmaple, the microsoft.com page usually appears to be loading and never does, but just recently it loaded and displayed nothing like the google page.
Anyway, will soldier on.