I’ve had several setups where a static route was necessary.
Some VPN/WAN configurations.
-sc
From: Richard Stovall [mailto:rich...@gmail.com]
Sent: Wednesday, April 27, 2011 10:32 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
I also thought I
, then the ACLs and/or firewall settings others
have
suggested are the best candidates for the culprit.
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Saturday, April 23, 2011 7:43 PM
To: NT System Admin Issues
Subject: frustrating network issue on two servers
Two sites, R
?
If it is a new setup, then the ACLs and/or firewall settings others have
suggested are the best candidates for the culprit.
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Saturday, April 23, 2011 7:43 PM
*To:* NT System Admin Issues
*Subject:* frustrating network issue on two
...@gmail.com]
Sent: Wednesday, April 27, 2011 10:17 AM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
OK
Everybody prepare to laugh.
Removed the ROUTE on server R1.
Re-added the ROUTE on server R1.
Problem gone
for the culprit.
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Saturday, April 23, 2011 7:43 PM
*To:* NT System Admin Issues
*Subject:* frustrating network issue on two servers
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B
and Exchange MVP
http://TheEssentialExchange.com
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Wednesday, April 27, 2011 10:17 AM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
OK
Everybody prepare to laugh.
Removed the ROUTE on server R1.
Re-added the ROUTE
: frustrating network issue on two servers
Please be aware that the route command is no longer recommended for
route table manipulations for Server 2008 and above. It is known to fail
under a number of circumstances.
Instead, use the netsh command, e.g. netsh interface ipv4 set route
.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Steven M. Caesare [mailto:scaes...@caesare.com]
Sent: Wednesday, April 27, 2011 10:32 AM
To: NT System Admin Issues
Subject: RE: frustrating network issue on two servers
Why on earth don't they simply
: frustrating network issue on two servers
Preaching to the choir.
That being said, breaking route.exe was not intentional but rewriting it
apparently takes a fair bit of effort. The stated direction for admin tools
is not toward stand-alone executables likes route.exe so I think they should
just finish
setup, then the ACLs and/or firewall settings others have
suggested are the best candidates for the culprit.
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Saturday, April 23, 2011 7:43 PM
*To:* NT System Admin Issues
*Subject:* frustrating network issue on two servers
Two
mechanisms netsh does under the covers? Geesh.
IOW: fix the stupid thing.
-sc
*From:* Michael B. Smith [mailto:mich...@smithcons.com]
*Sent:* Wednesday, April 27, 2011 10:25 AM
*To:* NT System Admin Issues
*Subject:* RE: frustrating network issue on two servers
Please be aware
*To:* NT System Admin Issues
*Subject:* RE: frustrating network issue on two servers
Please be aware that the “route” command is no longer recommended for route
table manipulations for Server 2008 and above. It is known to fail under a
number of circumstances.
Instead, use the “netsh” command
3:19 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
Yet, it is all too easy to make ROUTE.EXE a stub file that call the
necessary NETSH command, Mr. Choir Director sir.
ASB (Professional Bio http://about.me/Andrew.S.Baker/bio )
Harnessing
, April 27, 2011 3:53 PM
To: NT System Admin Issues
Subject: RE: frustrating network issue on two servers
+1.
If you are going include it, fix known issues. Period.
How many bazillion scripts out there might depend on CLI functionality that's
been there SINCE THE ORIGIN OF THE OS, for goodness sake
, but not for explorer
with UAC.
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Wednesday, April 27, 2011 2:55 PM
To: NT System Admin Issues
Subject: RE: frustrating network issue on two servers
Open a call and complain. I've already expressed my opinion. The only other
possibility
Just maybe I will!
:-)
-sc
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Wednesday, April 27, 2011 3:55 PM
To: NT System Admin Issues
Subject: RE: frustrating network issue on two servers
Open a call and complain. I've already expressed my opinion. The only
other
i didn't see anyone else suggesting this, but i've experienced odd
networking issues when ipv6 was enabled. we're not an ipv6 shop, so we don't
need it and disabling it on the win2k8 servers resolved some issues for us.
On Sat, Apr 23, 2011 at 5:42 PM, G.Waleed Kavalec kava...@gmail.com wrote:
Disabling IP 6 on 2008 and higher has been know and documented to break
things. There was a thread on this within the last 2 months that you might
want to look at.
Jon
On Wed, Apr 27, 2011 at 4:23 PM, Jeff mrplay...@gmail.com wrote:
i didn't see anyone else suggesting this, but i've
Indeed. :)
*ASB *(Professional Bio http://about.me/Andrew.S.Baker/bio)
*Harnessing the Advantages of Technology for the SMB market...
*
On Wed, Apr 27, 2011 at 5:31 PM, Jon Harris jk.har...@gmail.com wrote:
Disabling IP 6 on 2008 and higher has been know and documented to break
things.
[mailto:kava...@gmail.com]
*Sent:* Saturday, April 23, 2011 7:43 PM
*To:* NT System Admin Issues
*Subject:* frustrating network issue on two servers
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B servers can see all R servers - EXCEPT TWO
i looked through the last couple months worth of list activity, but didn't
really find anything groundbreaking. the only viable link i found was
http://blogs.technet.com/b/netro/archive/2010/11/24/arguments-against-disabling-ipv6.aspx.
this was a little vague and basically said that, aside from
Webster
Consultant and Citrix Technology Professional
http://dabcc.com/Webster http://dabcc.com/Webster
From: Jeff [mailto:mrplay...@gmail.com]
Subject: Re: frustrating network issue on two servers
i looked through the last couple months worth of list activity, but didn't
really find
://dabcc.com/Webster
*From:* Jeff [mailto:mrplay...@gmail.com]
*Subject:* Re: frustrating network issue on two servers
i looked through the last couple months worth of list activity, but didn't
really find anything groundbreaking. the only viable link i found was
http://blogs.technet.com/b
of the right people.
IPv6 should just work.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Jeff [mailto:mrplay...@gmail.com]
Sent: Wednesday, April 27, 2011 6:07 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
i looked
Kavalec [mailto:kava...@gmail.com]
Sent: Saturday, April 23, 2011 7:43 PM
To: NT System Admin Issues
Subject: frustrating network issue on two servers
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B servers can see all R servers - EXCEPT TWO
Webster
Consultant and Citrix Technology Professional
http://dabcc.com/Webster
*From:* Jeff [mailto:mrplay...@gmail.com]
*Subject:* Re: frustrating network issue on two servers
i looked through the last couple months worth of list activity, but didn't
really find anything
?
If it is a new setup, then the ACLs and/or firewall settings others
have
suggested are the best candidates for the culprit.
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Saturday, April 23, 2011 7:43 PM
To: NT System Admin Issues
Subject: frustrating network issue on two servers
you said you are using 192.168.x.x range it seems
easily possible.
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Sunday, April 24, 2011 5:33 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
I'm not logging in again
are using 192.168.x.x range it seems easily possible.
--
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Sunday, April 24, 2011 5:33 PM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
I'm not logging in again tonight
cache, clean up DC's etc. Do things start working?
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Monday, April 25, 2011 7:59 AM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
I don't think so, because we can SQL
Issues
*Subject:* Re: frustrating network issue on two servers
The exact command I used was
Nmap –sS –P0 –p 137,138,139,445,1433 192.168.2.132
This gave back the error I posted.
On Sun, Apr 24, 2011 at 3:18 PM, Ziots, Edward ezi...@lifespan.org
wrote:
I also scanned systems
:* Monday, April 25, 2011 7:59 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
I don't think so, because we can SQL and browse to R1 R2 from the R
subnet, no problem.
The symptom only exists crossing over from the B subnet.
And other R servers can
Kavalec [mailto:kava...@gmail.com]
*Sent:* Sunday, April 24, 2011 4:06 PM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Ipsec policy agent is running, no policies defined.
On Sun, Apr 24, 2011 at 2:34 PM, Crawford, Scott crawfo...@evangel.edu
wrote
...@lifespan.org mailto:email%3aezi...@lifespan.org
Cell:401-639-3505
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Sunday, April 24, 2011 5:37 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
The exact command I used was
Nmap -sS -P0 -p
...@gmail.com]
Sent: Monday, April 25, 2011 9:31 AM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
OK, I've had my cup of coffee and realized that 'filtered' != 'open'
Now I have to figure out why these ports are filtered, but only across
the subnet
:31 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
OK, I've had my cup of coffee and realized that '*filtered*' != 'open'
Now I have to figure out why these ports are filtered, but only across the
subnet.
On Mon, Apr 25, 2011 at 8:21 AM
: frustrating network issue on two servers
OK, I've had my cup of coffee and realized that '*filtered*' != 'open'
Now I have to figure out why these ports are filtered, but only across the
subnet.
On Mon, Apr 25, 2011 at 8:21 AM, G.Waleed Kavalec kava...@gmail.com
wrote:
OK, success
Engineer
Lifespan Organization
Email:ezi...@lifespan.org
Cell:401-639-3505
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Monday, April 25, 2011 9:46 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Here is the nmap result from B1
:* Monday, April 25, 2011 9:46 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51 ( http://nmap.org ) at 2011-04-25 08:42 Central
Daylight Time
Nmap scan report
[mailto:kava...@gmail.com]
*Sent:* Monday, April 25, 2011 9:46 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51 ( http://nmap.org ) at 2011-04-25 08:42 Central
Daylight Time
...@lifespan.org
Cell:401-639-3505
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Monday, April 25, 2011 9:46 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51
:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Monday, April 25, 2011 9:46 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51 ( http://nmap.org ) at 2011-04-25 08:42 Central
: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51 ( http://nmap.org ) at 2011-04-25 08:42 Central
Daylight Time
Nmap scan report for 192.168.2.134
Host is up (0.0092s latency).
PORT STATE SERVICE
137/tcp closed
-3505
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Monday, April 25, 2011 9:46 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51 ( http://nmap.org ) at 2011
...@gmail.com]
Sent: Monday, April 25, 2011 11:55 AM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
Are you sure this is an OS issue and not something having to do with
routers or switches or firewalls in between the devices?
Have you considered running nMap
: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Saturday, April 23, 2011 7:43 PM
To: NT System Admin Issues
Subject: frustrating network issue on two servers
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B servers can see all R servers - EXCEPT TWO
R1
: Monday, April 25, 2011 9:46 AM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
Here is the nmap result from B1 to a different R server
Starting Nmap 5.51 ( http://nmap.org ) at 2011-04-25 08:42 Central
Daylight Time
Nmap scan report for 192.168.2.134
:43 PM
*To:* NT System Admin Issues
*Subject:* frustrating network issue on two servers
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B servers can see all R servers - EXCEPT TWO
R1 and R2 see all B servers, browse folders etc.
B
You might try running a network trace :)
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Monday, April 25, 2011 12:58 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
Servers R1 and R2 have been up for months, but until recently access from
subnet B
Organization
Email:ezi...@lifespan.org
Cell:401-639-3505
*From:* Andrew S. Baker [mailto:asbz...@gmail.com]
*Sent:* Monday, April 25, 2011 11:55 AM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Are you sure this is an OS issue and not something having
Kavalec [mailto:kava...@gmail.com]
*Sent:* Saturday, April 23, 2011 7:43 PM
*To:* NT System Admin Issues
*Subject:* frustrating network issue on two servers
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B servers can see all R servers - EXCEPT
Nope. R1 or R1.ourdomain.local same symptoms.
Ping yes - from either subnet.
Browse no, SQL no - but ONLY fails from subnet B.
On Sun, Apr 24, 2011 at 12:50 AM, Crawford, Scott crawfo...@evangel.eduwrote:
does it matter if you use the fqdn?
Sent from my Palm Pre on the Now Network
Any firewalls ? Either windwows or something else in between. Make sure
ports are open. Try telnet to port 445 to be sure.
On Apr 24, 2011 10:59 AM, G.Waleed Kavalec kava...@gmail.com wrote:
Nope. R1 or R1.ourdomain.local same symptoms.
Ping yes - from either subnet.
Browse no, SQL no - but
have a network trace?
Sent from my Palm Pre on the Now Network from Sprint
On Apr 24, 2011 1:08 PM, Ben N bennordlan...@gmail.com wrote:
Any firewalls ? Either windwows or something else in between. Make sure ports
are open. Try telnet to port 445 to be
All firewalls off.
Once again, browse and SQL work fine from the same subnet/site.
And ping from both, both directions.
On Sun, Apr 24, 2011 at 1:08 PM, Ben N bennordlan...@gmail.com wrote:
Any firewalls ? Either windwows or something else in between. Make sure
ports are open. Try telnet to
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
All firewalls off.
Once again, browse and SQL work fine from the same subnet/site.
And ping from both, both directions.
On Sun, Apr 24, 2011 at 1:08 PM, Ben N bennordlan...@gmail.com wrote:
Any
ipsec service running? any policies defined?
Sent from my Palm Pre on the Now Network from Sprint
On Apr 24, 2011 2:02 PM, G.Waleed Kavalec kava...@gmail.com wrote:
All firewalls off.
Once again, browse and SQL work fine from the same subnet/site.
And ping
...@lifespan.org
Cell:401-639-3505
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Sunday, April 24, 2011 3:02 PM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
All firewalls off.
Once again, browse and SQL work fine from the same
Ipsec policy agent is running, no policies defined.
On Sun, Apr 24, 2011 at 2:34 PM, Crawford, Scott crawfo...@evangel.eduwrote:
ipsec service running? any policies defined?
Sent from my Palm Pre on the Now Network from Sprint
--
On Apr 24, 2011 2:02 PM,
Issues
Subject: Re: frustrating network issue on two servers
I'm not familiar with nmap. The command format you provide just says
Starting Nmap 5.51 ( http://nmap.org ) at 2011-04-24 14:57 Central Daylight Time
Failed to resolve given hostname/IP: ûsS. Note that you can't use
Email:ezi...@lifespan.org
Cell:401-639-3505
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Sunday, April 24, 2011 4:06 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
Ipsec policy agent is running, no policies defined.
On Sun, Apr 24, 2011
...@gmail.com]
*Sent:* Sunday, April 24, 2011 4:06 PM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
Ipsec policy agent is running, no policies defined.
On Sun, Apr 24, 2011 at 2:34 PM, Crawford, Scott crawfo...@evangel.edu
wrote:
ipsec service running? any
E. Ziots
CISSP, Network +, Security +
Network Engineer
Lifespan Organization
Email:ezi...@lifespan.org
Cell:401-639-3505
From: G.Waleed Kavalec [mailto:kava...@gmail.com]
Sent: Sunday, April 24, 2011 5:37 PM
To: NT System Admin Issues
Subject: Re: frustrating network issue on two servers
+
Network Engineer
Lifespan Organization
Email:ezi...@lifespan.org
Cell:401-639-3505
*From:* G.Waleed Kavalec [mailto:kava...@gmail.com]
*Sent:* Sunday, April 24, 2011 5:37 PM
*To:* NT System Admin Issues
*Subject:* Re: frustrating network issue on two servers
The exact command I used
Two sites, R and B. Same domain, different subnets.
All R servers can see all B servers
All B servers can see all R servers - EXCEPT TWO
R1 and R2 see all B servers, browse folders etc.
B servers can PING R1 and R2 just fine; R1 and R2 can PING B servers just
fine.
But B cannot browse R1 or
Check the IP properties of the servers in question. I had an issue with week
where one of my 2008 R2 servers couldn't ping, get to anything. I went into
the properties of IPv4, everthing looked good, then checked the box to verify
upon exit. Then all was well. Weird. May not apply, just a
Thanks Tom, I'll give that a shot in the morning.
On Sat, Apr 23, 2011 at 9:39 PM, Tom Miller tmil...@hnncsb.org wrote:
Check the IP properties of the servers in question. I had an issue with
week where one of my 2008 R2 servers couldn't ping, get to anything. I went
into the properties of
67 matches
Mail list logo
