Home Network w/ 2 SQLServers: 1-way problem

I have a WinXP Pro home network which is behind a firewall. Within
this network I have 2 computers running SQLServer 2000: my desktop and
my laptop. Both instances are configured identically and use Windows
authentication. I use Enterprise Manager.
- My laptop can "see" the desktop's instance; i.e., I'm able to create
a SQLServer Registration entry and browse the desktop's databases
- My desktop can NOT "see" the laptop's instance. When I try to create
a SQLServer Registration, I receive "SQL Server does not exist or
access denied..."
I've tried registering via the laptop's computer name, and I've tried
registering via the laptop's local IP address.
My firewall is not allowing access to port 1433 for either computer.
Both computers can see each other through file/printer sharing.
SQLServer seems to be the only case where there is a "blockage".
Any help is appreciated...
-JeffOne other note -- both machines can ping each other by IP and by name.
Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
and
> my laptop. Both instances are configured identically and use Windows
> authentication. I use Enterprise Manager.
> - My laptop can "see" the desktop's instance; i.e., I'm able to
create
> a SQLServer Registration entry and browse the desktop's databases
> - My desktop can NOT "see" the laptop's instance. When I try to
create
> a SQLServer Registration, I receive "SQL Server does not exist or
> access denied..."
> I've tried registering via the laptop's computer name, and I've tried
> registering via the laptop's local IP address.
> My firewall is not allowing access to port 1433 for either computer.
> Both computers can see each other through file/printer sharing.
> SQLServer seems to be the only case where there is a "blockage".
> Any help is appreciated...
> -Jeff|||Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
> and my laptop. Both instances are configured identically and use
> Windows authentication. I use Enterprise Manager.
>
If you're blocking 1433 on both PCs, how are you connecting to the
desktop from the laptop? Named Pipes? Try using the same network
protocol to connect the other way around.
--
David Gugick
Imceda Software
www.imceda.com|||Would the firewall blockage apply internally? I thought the firewall
would only prevent outside access? In other words, I didn't think that
my firewall would prevent internal machines from communicating?
Anyhow, both Named Pipes and TCP/IP are enabled.
The Server Network Utility and Client Network Utility settings are
identical on both machines.
> If you're blocking 1433 on both PCs, how are you connecting to the
> desktop from the laptop? Named Pipes? Try using the same network
> protocol to connect the other way around.
> --
> David Gugick
> Imceda Software
> www.imceda.com|||Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
--
David Gugick
Imceda Software
www.imceda.com|||Is your Firewall also acting as your LAN router? If so, it is probably
blocking your internal traffic as well. Consider putting your Firewall in
front of a real LAN router, that's how it is usually configured. If so,
then that configuration would behave as you suspect, blocking only traffic
onto/out of the router, but not packets routed between back end hosts.
Sincerely,
Anthony Thomas
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23mN$uleHFHA.3196@.TK2MSFTNGP15.phx.gbl...
Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
--
David Gugick
Imceda Software
www.imceda.com