Users cannot access HTTPs - [WP] WildPacket 10/24/2008 5:42:15 PM The users in one of our remote site cannot logon to any https:// sites on the internet - it just times out on them but weird is they can logon to the OWA site. They have Windows 2003 DC/GC there ...if I by pass the entire network using a notebook and plug directly in the router all works fine. What could be wrong ... DNS - DNS forwarders are pointing to a DC in the HeadOffice and BELLs IP???? Flushed the Local Cache/DNS on the client no sucess???? It is definetly some thing in our site ...all was working. One day accidently BELL disconnected their connection and when they put it back this issue surfaced. Advise Please. Thank you

Re: Users cannot access HTTPs - [WP] "A, Deji" <deji[ at ]akomolafe.com> 10/25/2008 6:39:05 AM DNS does not factor into the equation here. I'd look at your firewall/router/proxy and anything else in-between the client and the web server, but don't focus on DNS. Deji "WildPacket" <WildPacket[ at ]discussions.microsoft.com> wrote in message news:37E26A87-A216-4692-8A08-F23BFCED30E5[ at ]microsoft.com... [Quoted Text] > The users in one of our remote site cannot logon to any https:// sites on > the > internet - it just times out on them but weird is they can logon to the > OWA > site. > > They have Windows 2003 DC/GC there ...if I by pass the entire network > using > a notebook and plug directly in the router all works fine. > > What could be wrong ... DNS - DNS forwarders are pointing to a DC in the > HeadOffice and BELLs IP???? Flushed the Local Cache/DNS on the client no > sucess???? > > It is definetly some thing in our site ...all was working. One day > accidently BELL disconnected their connection and when they put it back > this > issue surfaced. > > Advise Please. > > Thank you

Re: Users cannot access HTTPs - [WP] Paul Bergson [MVP-DS] <pbbergs[ at ]nospam_msn.com> 10/29/2008 12:27:44 PM Hello WildPacket, What happens when you do some troubleshooting? ping the dns server ping the workstations gateway ping your firewall on the internal side nslookup www.live.com tracert -d www.live.com This will help you quickly learn if things are internally setup correctly. My guess is there are problems with the gateway or the workstation configuration. -- Paul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. [Quoted Text] > The users in one of our remote site cannot logon to any https:// sites > on the internet - it just times out on them but weird is they can > logon to the OWA site. > > They have Windows 2003 DC/GC there ...if I by pass the entire network > using a notebook and plug directly in the router all works fine. > > What could be wrong ... DNS - DNS forwarders are pointing to a DC in > the HeadOffice and BELLs IP???? Flushed the Local Cache/DNS on the > client no sucess???? > > It is definetly some thing in our site ...all was working. One day > accidently BELL disconnected their connection and when they put it > back this issue surfaced. > > Advise Please. > > Thank you >